Version: (using KDE KDE 3.1.1a) Installed from: Mandrake RPMs People need powerful grabber. Particulary, I want: 1. encoding on the fly, I mean ability to change general command line ( for example, i use cdda2wav -I cooked_ioctl -D /dev/cdrom -w -t <TRACK NUMBER> - | lame - "<NAME OF TRACK>.mp3" --alt-preset standard -c -p -tt "<SONG TITLE>" ) This will provide freedom of choosing encoder (lame, oggenc, flac) and ripper (cdda2wav, cdparanoia) 2. Remote CDDB support (and not only freedb) 3. CD-TEXT support 4. Local CDDB - for saving info obtained from remote CDDB, CD-TEXT, user input 5. When inputting album info (names of songs): User entered name of track 1, pressed <Enter> and after that track 2 must be activated and it must be ready for typing The same vs other trax. This will help people to enter album info faster 6. Support for cp1251 encoding cause it is used (de-facto) in all russian mp3's
Have you already taken a look at KAudioCreator? The only things in your list that I don't know if it supports are: 3) CD-TEXT 4) Local CDDB (I'm almost certain) 6) correct encoding selection for MP3 ID3v2 tags 1 is implemented, though it always uses kio_audiocd as a source, which in turn uses cdparanoia (or libparanoia?) 2 is implemented and you can change the server in the global configuration 5 is implemented Ogg always uses UTF-8 for comments, so 6 is Ok for Ogg, whereas ID3v1 is ISO-8859-1 *only*.
CD-TEXT saving (in local CDDB) is important for me I have an old BTC (without cdtext support) and new Teac CD-RW (with) What I do if Windows is loaded (using CDex, cdexos.sourceforge.net): 1. Load Aidio CD in Teac, CD-Text is saved in local CDDB 2 Eject CD from Teac and load it in BTC, CD-Text is read from local CDDB 3. Rip track using BTC, avoiding torturing my new CDRW (I keep it only for copying new ALTLinux releases :-)
KAudioCreator uses several backends. I recomend that you seperate the issues and put them as wishlists in the respected backends. audiocd:// right now only uses cdparinoia so add as a wishlist against audiocd:// to also use cd2wav as a configure option. The CDDB (and cd-TEXT) wishlist items should be assigned to libkcddb. Once assigned to those backends then their authors can work on them (I don't really work on them).
ok, but what about encoding on the fly? Do you know what the main difference between DOW and Unix? Or is it too hard for you to implement this: system("cdparanoia \"" + track + "\" - | lame - \"" + filename + ".mp3\" --alt-preset standard"); ? Why i must damage my harddisk saving on it .wav files?
Encoding on the fly is a desired feature and work is being done to that end, but the woks is in audiocd and not kaudiocreator. A major step was made and it shoudl be on target for the next release.
i hate audiocd:/ couse its developers don't understand that --r3mix is outdated and --alt-preset standard (or extreme, insane, cbr or abr) are the only options needed. Only alt-preset (and only in lame 3.90.3) options have good quality. see hydrogenaudio.org
ok, i'll study qt and make fork of your app
>> i hate audiocd:/ >> couse its developers don't understand that --r3mix is outdated and >> --alt-preset standard (or extreme, insane, cbr or abr) are the only options >> needed. >> >> >> Only alt-preset (and only in lame 3.90.3) options have good quality. >> see hydrogenaudio.org Good thing you have KAudioCreator which lets you specify whatever option you want. As for piping (so you don't have to to save to disk first) I have a patch waiting for approval which will permit that very option.
> I have a patch waiting for approval which will permit that very option. Oh, really? But, I guess, it'll be implemented only on CVS HEAD, i.e. only in kde33... As for libkcddb (CD-Text), i'll open for this soon
Well lucky for you (and everyone) 3.3 is not going to be next January, but July. We are going to try a 6 month release this time. I can also make a private release if there is interest.