Collaborative ripping

Discuss the current and future development of Max.
Post Reply
Posts: 2
Joined: Thu Feb 15, 2007 2:49 pm

Collaborative ripping

Post by sporksmith »

First, thanks a lot for all your work- after poking around for several days, Max is the best ripper I've been able to find for OS X.

Unfortunately, I didn't know much about cd ripping, and after ripping my cd collection using the basic ripper, I started noticing some pops, which led me to reading about secure ripping and the difficulties thereof on your forums and elsewhere.

My first suggestion would be to not make the basic ripper the default so noobs like me don't shoot themselves in the foot :)

On to the interesting part, semi-cross posted from my blog:

From what I understand, secure rippers such as cdparanoia and the comparison ripper basically read each sector multiple times until it gets the same data from a particular sector n times. This does a decent job of getting rid of non-deterministic read errors. Unfortunately, cd's can be damaged in such a way that they consistently return the same incorrect data, so it's not foolproof. And of course if a sector is horribly damaged you may not be able to read anything at all.

That led me to wonder if there would be value in a collaborative ripping database. If, after ripping a cd, people submitted hashes for each track, and/or each sector, we could compare the hashes across multiple discs, and have a much higher confidence of whether the correct data was read. This would at least let you know whether you successfully ripped a sector/track/disc, but if the disc is damaged such that you can never read the correct data, you're still screwed.

Even better would be if the database could *correct* bad sectors. A naive solution would be to store the actual audio data, and provide requested sectors to people. Of course, this would be heavy weight, highly abused, and slapped with a cease-and-desist before you could say fair-use.

One way that might work is for people to generate and submit error-correcting codes per sector (e.g., reed-solomon). These codes could be used to correct a sector with a relatively small number of bit errors, but wouldn't give much useful information to someone who didn't have the original (maybe slightly damaged) sector.

Any thoughts on this? My usual expectation when I think of something like this is that either it's been done, or there's a good reason why it hasn't been done. If nothing else, it would require a server with pretty decent storage and bandwidth.

EDIT: btw, sorry if this is off-topic. Feel free to move it to the 'general discussion' forum if it belongs there. I posted here because, while I forgot to explicitly ask, part of what I want to know is if such a service existed, would you be interested in integrating it into max?
Posts: 117
Joined: Sun Jan 29, 2006 1:36 pm
Location: London, Europe

Post by Maurits »

You might want to have a look at AccurateRip.
Posts: 2
Joined: Thu Feb 15, 2007 2:49 pm

Post by sporksmith »

Maurits wrote:You might want to have a look at AccurateRip.
Ah ha! Yup, pretty much what I was thinking of, though they only provide verification, not correction. Then again, I'm not sure if correction is really feasible.

Any chance of seeting accuraterip integrated into Max?

User avatar
Site Admin
Posts: 2458
Joined: Fri Dec 23, 2005 7:45 am
Location: USA

Post by sbooth »

sporksmith wrote:Any chance of seeting accuraterip integrated into Max?
Not really, because it is Windows only and they solely provide a binary (dll) interface. I looked into it pretty heavily about 6 months ago and there is no chance (at this time) of getting the source code, because they are afraid that with the source code people could submit bogus information and lower the quality of their database. I'm not sure the argumemt holds water, but in any case, there is no OS X SDK and no way to get one. You might want to check out ... 37945.html,,,, and
Post Reply