Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
In June 2006 a beta-version was released. Usually, on beta-versions a few weeks later follow a RC or the final; now nearly 1,5 years are over.
Has the developement stopped?
It looks as if they left a prefectly good product to die.
Who cares. The beta was outdated. CDex WAS a good program 5 years ago...
With CDEx apparently "dead"-- What's everyone using now? I love CDEx for simple ripping...but i'm now also using mp3gain to adjust volume... Would entertain something that's simple, but can convert 320 to 192kb etc, grab info off cddb, and possibly do mp3 gain as well... any recommendations?
Oh, that's very pity, this program is/was the perfect tool for audio cd ripping and it was free/open source and that was very cool :-)
This program doesn't never die, never.
This formum contents very lots of spam in new post, the poster name's anonymous.
I have started to look around,
especially when I started to see problems with VNC playing my ripped mp3s,
where it looks like CDex may be generating some invalid data (see the VNC error messages).
After some searching I have found that both
are more than adequate replacements,
and are both under active development.
I just saw this thread, having already posted the same question on the 'Help' forum. It would appear to be well and truly dead, as the OP started this thread a year and a half ago and none of the dev team (if there even is one anymore) could be bothered to respond. What a shame!
I have used CDex now for years. It was, in my opinion at least, THE most user friendly CD ripper around. I could do almost anything I wanted to with it and it was dead easy to set up. I mean, I know EAC is the current "darling" of freeware rippers. But it's WAY too arcane for my liking...a true PITA to set up and use.
You wanna know the saddest part of this? CDex is open source. Which means that ANY capable developer could grab the code and start working on his/her own fork of the app. Too bad I'm not a programmer or I'd probably take it on myself. Ah well. Now the search begins for a suitable replacement.
It still works and doesn't appear to be broken in any way.
If you see a place where you can improve it, go for it.