-Z by default?

[GoogleCodeExporter]

Why is -Z included in the cdparanoia config by default?  Doesn't that
disable the paranoia?

Original issue reported on code.google.com by emailgr...@gmail.com on 26 Jun 2008 at 5:57

[GoogleCodeExporter]

I don't know. I removed that option myself, I think it should indeed be removed 
from
the default options.
I'm not removing it now, maybe there was a good reason for putting it there.

Original comment by jwca...@gmail.com on 2 Jul 2008 at 9:49

• Changed state: Accepted

[GoogleCodeExporter]

The correction cdparanoia does isn't always that good with drives that have a 
cache. In 
combination with a better speed I've disabled the cdparanoia correction by 
default. 

If you don't like it, you can simply remove it. But I don't see any benefits. 
Please come with 
some proof that removing -Z leads to better rips.

Original comment by rubyripp...@gmail.com on 4 Jul 2008 at 3:09

• Changed state: WontFix

[GoogleCodeExporter]

since rubyripper aims to be a _secure_ ripper for the unix world, i think this 
should
definitely be removed from the default options

anyway, flac default flags should also be modified. -V should definitely be 
added so
that the generated flac files can be verified later

Original comment by asdfasdf...@freemail.hu on 27 Sep 2008 at 11:30

[GoogleCodeExporter]

Please start up a new issue. I think cdparanoia recently improved the handling 
of
drives that caches data. The internal cdparanoia correction is therefore much 
better
and more reliable. Since this wasn't the case it was not improving the quality 
before
(IMHO).

Original comment by rubyripp...@gmail.com on 28 Sep 2008 at 8:40

[GoogleCodeExporter]

okay, i filed it up:
http://code.google.com/p/rubyripper/issues/detail?id=243
thanks

Original comment by asdfasdf...@freemail.hu on 28 Sep 2008 at 2:40