I was thinking of writing my own ripper/encoder frontend (mostly as a research project to improve my programming skills) and I was wondering if there is any way to re-use the Windows port of cdparanoia that
is the basis of the latest versions of CDEX.
I.e. anyone familiar with CDEX code can maybe tell me whether this is a stand-alone DLL or maybe a set of classes that could be re-used in a different project?
thanks in advance...
Answered my own question: CDRip.dll
...sorry for wasting bandwidth here...
Answered my own question: CDRip.dll
...sorry for wasting bandwidth here...
Checking through the CDex source should help too.
Just a note, if you are using a port of cdparanoia for windows, if a cd drive caches, it will be of no more use than any other burst mode ripper and so there may be others that are easier to use.
This is due to the fact that cdparanoia doesn't account for a drive cache, so it reads, re-reads from the cache and reports no error!!! I have personally tested this and have found that even on a terrrible cd, EAC struggled for ages in secure (2 hours and then failed), but cdex and cdparanoia reported no error! the result was unusable!!
Of course, if your drive does not cache, then it's great. If it does, you can still use no paranoia because it's not worth anything anyway!
These are just a few suggestions and opinions of mine, please nobody slate me! I would really love to use cdparanoia, especially when i am under Linux. I would then have no need for EAC.
Cheers,
Kristian
Has anyone ever done some comparison CDex vs. cdparanoia in linux? If you use cdparanoia from bash, you get quite thorough report of errors, IMHO much better than with CDex. I'd say that CDex just counts the bigger and very obvious errors cdparanoia reports. According to http://xiph.org/paranoia/faq.html#progbar (http://xiph.org/paranoia/faq.html#progbar) the report could contain much more info than CDex displays.
However, if you're right about that cache stuff, cdparanoia undoubtly has a major weakness, although it is much better than any other ripper I tried except EAC. But I don't like EAC because it stresses the drive (and my patience ) too much.
Does cdparanoia in linux encode to mpc, log? I may be using it soon with my xbox.
Does cdparanoia in linux encode to mpc
Uhh,
you encode to mpc, not a ripper. A ripper rips CD->wav. An encoder encodes wav->xx, and you can use whatever encoder you wish, and whatever method to do so you wish. Under Linux you may wish to use grip, a front-end to cdparanoia, which supports encoding to whatever command line you choose to type in (of which mppenc can certainly be one).
Does cdparanoia in linux encode to mpc
Uhh, you encode to mpc, not a ripper. A ripper rips CD->wav. An encoder encodes wav->xx, and you can use whatever encoder you wish, and whatever method to do so you wish. Under Linux you may wish to use grip, a front-end to cdparanoia, which supports encoding to whatever command line you choose to type in (of which mppenc can certainly be one).
abcde is a console based 'frontend' to cdparanoia and I found it fantastic. Take a look - it may be more suitable for the xbox.
Uhh, you encode to mpc, not a ripper. A ripper rips CD->wav. An encoder encodes wav->xx
What I was saying was, are there any frontends for it that support rip, encode & log like EAC does.
abcde is a console based 'frontend' to cdparanoia and I found it fantastic. Take a look - it may be more suitable for the xbox.
Thanx, I'll try it.
Is this possible to build a CDparanoia.exe binary ?