Hi
This is my first post at this site, i'v been meaning to join for a while now just never got around to it. Anway my question is.

I have been using cdex for about 2 years now and its done me well.
But a friend of mine uses EAC and he always says its better for getting a more "Secure" rip. I never really liked the Eac interface and found it very confusing but one feature that i thought was an excellent idea was the "AccurateRip" feature in it. Is there a way to actually include this in cdex without changing the program or doing something to the source code.

Thanks in advance.

In CDex it's just called cdparanoia. Options -> Settings -> CD Drive -> Ripping Method.

No i'm not talking about the error correction in cdex im talking about accurate rip
(www.accuraterip.com) when a cd is ripped and compared to other peoples to see if the rip is without error.

AccurateRip can't be added to CDex. CDex is GPLd, and AccurateRip is not released under a GPL-compatible license.

May i ask how it was included in EAC.

Erm.. EAC is not GPLd :B

Ok stupid question thanks for the reply

>AccurateRip can't be added to CDex. CDex is GPLd, and AccurateRip is not released under a GPL-compatible license

Not perhaps the main thing stopping it (look at CDex's WMA encoder, it is dbpoweramp's and that is without GPL).

The main thing stopping it is that CDex would first have to have CD drive offset capacity, then a developer would need about 2-3 months to implement AccurateRip (of part time work) that is the perhaps the main reason.

That's right, CDex should not encode to WMA. Or, at least, not link to Microsoft's SDK code for WMA encoding, as it is not GPL-compatible.

Then again, we arrive at the problem that Albert Faber seems to have no idea of what really means for a code to be GPLd. Otherwise he wouldn't be distributing Winamp plugins in the installation package.

CDex was originally GPLd so that it could feature CDparanoia (that is GPLd). So, even if Faber wanted, he wouldn't be able to create exceptions in his licensing to accomodate AcurateRip's closedsourceness. It would then conflict with CDparanoia.

Solution? Either remove CDparanoia from CDex (and other eventual code under the GPL), or release AccurateRip in a GPL-compatible license (won't happen)

Regards;

Roberto.

What a pity... A good example that opensource-licenses also can be contraproductive...

Isn't there any alternative to AccurateRip? I can't imagine that it is too difficult code. Does it more than hashing the raw audio data and compare it with a database?

I'm sure there's a way for CDex to use AccurateRip without having to cause license conflicts by linking directly to it. E.g. via scripting, or writing a scriptable non-GPL wrapper around AR if it's currently not scriptable.

Granted that's kludgy and a pain.

-brendan

Unfortunatly I don't believe their is. This is the drawback to using applications like EAC. You need to use them exclusively for those features, as they aren't GPLed or open-source, so they can't be ported to other applications. Now we are starting to see applications that have their own secure algorithms and use cdparanoia in conjunction for error correcting.



This happens quite often. There is a big difference between GPL and LPGL for example. Most open-source developers release their code under the GPL license when it should be LPGLed etc.

As Spoon already said, until CDex supports read sample offset correction it will not be able to the AccurateRip database. I doubt that a workaround through scripting will be able to address this fundamental problem.

Er, what I meant was: if the Author of CDex wanted to incorporate AccurateRip, the author could, even if prevent via license from compiling into the application. Just write a compatible-with-accuraterip-license (i.e. GPL) translater app that runs in a separate process and talk to CDex via scripting or other non-code-jump method.

That's how non-GPL software calls into Linux libraries, for example.

-brendan