Version: 1.13 (using KDE 3.5.2, Debian Package 4:3.5.2-2+b1 (testing/unstable)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.16-1-686 Currently kaudiocreator uses system("") type execution to run the ripper which means that it has to prepare the ripped files as actual FILES on the hard drive. This is very inefficient. Each CD takes about 700 megs and it wears my hard drive down (imagine ripping 100 cds and rewriting the same 700 megs of drive space a 100 times over). The ripper can work DIRECTLY from the cd. This means that the ripper will read from the cd and will ripp and write the results directly to the hard drive. This could be achieved via a pipe but most rippers have support for that even today. The most efficient use of resources would be not to use the ripper via a system("") type execution but rather use its API directly and link with its library. The ripper would then not be a different process but rather a different thread in the system. The communication with ripper in this case would be much more efficient (good error reporting, real time control like - pause, resume etc and many many more goodies).
This is what audiocd:/ is there for.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
This project is unfortunately no longer maintained. If a new maintainer wants to step up and take care, the project is archived here: https://invent.kde.org/unmaintained/kaudiocreator You can just clone it in your private namespace on invent.kde.org and if you have started to work on it and fixed/implemented something get it reviewed and the project unarchived. Sorry for the inconveniences.