Version: (using KDE KDE 3.4.3) Installed from: SuSE RPMs I have kaudiocreator's "Automatically rip all tracks upon a successful CDDB retrieval" option selected. However, this feature has an annoying bug (or misfeature?) in that data tracks from enhanced CDs are ripped. Ripping and encoding data tracks doesn't make any sense because there's nothing to hear. Please make kaudiocreater automatically detect and skip data tracks when "Automatically rip all tracks upon a successful CDDB retrieval" is enabled. A naive way of doing this would be to simply skip any tracks called "Data" which appear at the end of the CD. (I believe that the standard CDDB naming convention is to call all data tracks "Data", and in my experience all data tracks are placed at the end of the CD rather than at the beginning or interspersed with audio tracks.) A more sophisticated way would be to actually examine the track to determine whether it is an audio track or a data track, though I don't know how easy this is.
I too had a problem with data tracks. They show up in the track list and I made the (l)user error off adding it to the rip job list. When Kaudiocreator hit the data track kioslave just hung eating up my CPU. The CD was 'A Livingroom Hush' by 'Jaga Jazzist' (ZEN CD76), if this helps replicating the issue (kaudiocreator-1.13).
I have had the same problem on the CD "Venezuela Zinga Son" by Los Amigos Invisibles. There's a video.flv file on the disk, and I did the same luser misteak of selecting all tracks without observing that one of them was a video. The application hangs. In general, I have found kaudiocreator does not handle bad audio tracks well at all. I have also found that on some marginal disks (read: Disks purchased at the outdoor bazaar's in Caracas, Venezuela), kaudiocreator will hang on tracks that Kaffeine is able to decode. kaudiocreator has a general hanging problem, I'd say. It does not handle bad audio tracks well...
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.