Version: 1.12 (using KDE 3.3.2, Gentoo) Compiler: gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6) OS: Linux (i686) release 2.6.10-gentoo-r4 If I attempt to RIP a track that has a question mark in its name then the Lame encoder fails. It does however appear that the file was actually ripped to a wav from the CD.
If you click on the extended info box what does the encoder output? Are you trying to move it to a fat32 partion?
Encoder output is as follows: lame --preset standard --tt 'Who Cares?' --ta 'Extreme' --tl 'Extreme III Sides to Every Story' --ty '1992' --tn '14' --tg 'Rock' '/tmp/3lApFb.wav' '/mnt/data/mp3-download/to-tag/Extreme III Sides to Every Story - Extreme - 14 - Who Cares?.mp3' Can't init outfile '/mnt/data/mp3-download/to-tag/Extreme III Sides to Every Story - Extreme - 14 - Who Cares?.mp3' And yes, I am trying to save it to a FAT32 fs (which of course doesn't allow ? as a piece of a filename), but I thought that the software would take care of it.
As a temporary work around, I figured out that you can go to the Configuration Dialog and Under General place "\?" (sans quotes of course) in "Selection" box and "" or "_" in the "Replace With" box. If this is the actual solution, then perhaps it would be advisable to allow more than one regex find/replace pairing. Then you could also have KAudioCreator ship with some of these pairings already enabled to fix issues on different filesystems.
You can do more then one find/replace. It is a full regexp. Maybe I should show more examples? As for the Fat32 issue... I wont disable those on by default sense they work fine everywhere else, but fat32 (and many songs have ?). Maybe add some sort of filesystem check, but that has to be given more thought sense KAudioCreator runs on BSD, linux, etc
TODO: add "[ ] Fat32 compatible names." checkbox option to the configure dialog.
You can add more characters by doing this *not in quotation marks*: [\?\'\"]
*** Bug 119236 has been marked as a duplicate of this bug. ***
*** Bug 117462 has been marked as a duplicate of this bug. ***
*** Bug 155477 has been marked as a duplicate of this bug. ***
There is now a "Make FAT32 compatible filenames" option (1.2.80).