Cdparanoia Lives!

khead · Post by **khead** » Wed Aug 30, 2006 9:05 pm

Great news for everyone here:

http://www.hydrogenaudio.org/forums/ind ... opic=47850

khead · Post by **khead** » Wed Aug 30, 2006 11:33 pm

http://lists.xiph.org/pipermail/paranoi ... 6.html[url]

[/url]

krmathis · Post by **krmathis** » Thu Aug 31, 2006 2:46 pm

Great news, I guess!
No new features yet, but at least it is now have a active development again. Five years after the previous official release.

http://lists.xiph.org/pipermail/paranoi ... 00006.html

khead · Post by **khead** » Thu Aug 31, 2006 4:12 pm

Less wordy, and more importantly:

http://www.xiph.org/paranoia/news.htm

There is a completely new version (IV) being started soon.

Might it be best to let this be the secure ripper and focus on implementing a complete port, rather than spending a lot of time trying develop an “in house” secure ripper?

Post by **sbooth** » Thu Aug 31, 2006 4:24 pm

khead wrote:Less wordy, and more importantly:

http://www.xiph.org/paranoia/news.htm

There is a completely new version (IV) being started soon.

Might it be best to let this be the secure ripper and focus on implementing a complete port, rather than spending a lot of time trying develop an “in house” secure ripper?

I guess it depends on the direction that IV takes. If it relies on SG_IO or FUA bits, then it won't be much more effective on a Mac than the current version. If it attempts to perform some sort of cache-defeating algorithm (test & copy or whatever you wish to call it) then it could be an improvement.

I read an interesting article on HA (part 2 is http://www.hydrogenaudio.org/forums/ind ... opic=47415) indicating that the approach used by the comparison ripper in Max- large reads with C2 error reporting- seems to be very reliable. I am still not convinced that with offset correction added the comparison ripper will not be up to par.

khead · Post by **khead** » Sat Sep 02, 2006 4:09 pm

OK - That does make things sound more promising for the comparison ripper. I thought it was still stuck on trying to disable or flush the cache, which seemed to have dead ended.

I do hope that paranoia continues to be supported in Max. It’s quite a bit faster than the comparison ripper, and I think that paired with just about any decent drive - caching or not - is all that I, and probably most people just looking to reliably transfer their CD collection to their computer without any audible defects, really need.

It think all the talk on the forums about MAX really needing a “secure” ripper might be confusing to some people.
Perhaps a FAQ section would be helpful on this site.

Again, thanks for this program. It’s my most valuable program... and free!!!

krmathis · Post by **krmathis** » Sun Sep 03, 2006 5:44 am

Seems like Monty plan to update cdparanoia's cache management code:
http://slashdot.org/comments.pl?sid=108647&cid=9242997

Fuga · Post by **Fuga** » Sun Sep 03, 2006 3:16 pm

From that link does no one else find the following comment intriguing?

"Or you can increase the cache thrashing constant and rebuild."

I would guess I am wrong in my assumption because if it were true I'd have to ask why no one tried earlier, but ...

Does that comment mean there is merely a paranoia setting to be changed (i.e. "cache thrashing constant")?

Do please forgive my ignorance.

Post by **sbooth** » Sun Sep 03, 2006 4:17 pm

Fuga wrote:From that link does no one else find the following comment intriguing?

"Or you can increase the cache thrashing constant and rebuild."

I would guess I am wrong in my assumption because if it were true I'd have to ask why no one tried earlier, but ...

Does that comment mean there is merely a paranoia setting to be changed (i.e. "cache thrashing constant")?

Do please forgive my ignorance.

I'm not too familiar with the paranoia source, but that is what the comment implies to me. I don't remember seeing anything like that in the paranoia version I'm using for Max, though, but I will go back and check!

krmathis · Post by **krmathis** » Sun Sep 03, 2006 5:56 pm

I seached the source code for 1024 bytes (1MB), and got these hits:

Code: Select all

$ grep -r 1024 *
buffering_write.c:#define OUTBUFSZ 32*1024
interface/common_interface.c:  float *a=calloc(1024,sizeof(float));
interface/common_interface.c:  float *b=calloc(1024,sizeof(float));
paranoia/p_block.h:#define MIN_SILENCE_BOUNDARY 1024   /* 16 bit words */

Perhaps one of them should be changed to 8096, or something?

khead · Post by **khead** » Tue Sep 19, 2006 11:55 am

Just to add a couple of quotes taken from the current Paranoia FAQ page:

“Paranoia IV is an upcoming generation that intends to improve the library API as well as take advantage of new CDROM features that existed on only a few specialist drives five years ago, but are now ubiquitous even in inexpensive models. Where Paranoia III concentrated on bulletproof extraction from good media and reliable extraction from damaged media, Paranoia IV will concentrate on the best possible extraction and correction from even heavily damaged media-- so long as the drive can still recognize the disc.“

“Since Paranoia III was originally declared 'finished' in 1999 (subsequent releases have mostly just been to fix bugs and keep up with kernel changes), a number of features that once existed only on very expensive CDROM drives have become more widespread. In particular, drives today are much more capable of fine-grained reporting of media damage. Thus Paranoia IV is now intended to be an update of Paranoia III that improves error handling and reconstruction ability.“

sbooth.org

Cdparanoia Lives!

Cdparanoia Lives!

Or ...