| Summary: | KAudioCreator canoot encode tracks that have a question-mark in the title | ||
|---|---|---|---|
| Product: | [Applications] kaudiocreator | Reporter: | Mike Kinghan <imk> |
| Component: | general | Assignee: | Gerd Fleischer <gerdfleischer> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | adam |
| Priority: | NOR | ||
| Version: | 1.12 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Are you using a fat filesystem? On Friday 02 December 2005 10:13, Benjamin Meyer wrote:
>
> ------- Additional Comments From ben meyerhome net 2005-12-02 11:13
> ------- Are you using a fat filesystem?
The music collection is stored on a fat32 partition to share it between Linux and Windows XP on a dual boot system.
(Damn! It's just happened again as I'm writing. Van Morrison, "Have I Told You Lately That I Love You?")
So if this problem only arises on fat/fat32 filesystems then I could work round it having KAudioCreater encode an album to a linux partition, then have a look through for question-marks in filenames and edit them before moving to the music collection?
Not a major nuisance. I could automate it. Would be nice though if I could configure "strip question-marks from encoded filenames" when I run into this problem. Anybody with a dual boot system is only going to put their music on it once, and that means a common Linux/Windows partition or no music in one OS.
Thanks!
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:10pt;font-family:Sans Serif">
<p>On Friday 02 December 2005 10:13, Benjamin Meyer wrote:</p>
<p></p>
<p>></p>
<p>> ------- Additional Comments From ben meyerhome net 2005-12-02 11:13</p>
<p>> ------- Are you using a fat filesystem?</p>
<p></p>
<p>The music collection is stored on a fat32 partition to share it between Linux and Windows XP on a dual boot system.</p>
<p></p>
<p>(Damn! It's just happened again as I'm writing. Van Morrison, "Have I Told You Lately That I Love You?")</p>
<p></p>
<p>So if this problem only arises on fat/fat32 filesystems then I could work round it having KAudioCreater encode an album to a linux partition, then have a look through for question-marks in filenames and edit them before moving to the music collection?</p>
<p></p>
<p>Not a major nuisance. I could automate it. Would be nice though if I could configure "strip question-marks from encoded filenames" when I run into this problem. Anybody with a dual boot system is only going to put their music on it once, and that means a common Linux/Windows partition or no music in one OS.</p>
<p></p>
<p>Thanks! </p>
<p></p>
<p>-- </p>
<p>Mike Kinghan</p>
<p>20 Don Bosco Close</p>
<p>Temple Cowley</p>
<p>Oxford OX4 2LD</p>
<p>Tel. +44 (0)1865 438231</p>
<p>Mob. 0776 5222 793</p>
</body></html>
I recently ran in a similar problem (but I'm NOT using a FAT fs). My CD *title* had an exclamation mark in it, and the ogg-encoder didn't accept that (apparently the shell tried to expand the '!' even though it the shell-command issued by kaudiocreator had it in single quotes). Anyway: No FAT, but problems with '!' in the title. Removing the '!'s, and everything worked fine. I have the same problem with '?' and '"' characters in the track name; I'm trying to rip CDs with lame to an external fat32 harddisk. Why is this bug still unconfirmed? The solution should be quite simple - the program should simply remove all special characters from the generated file name (such is '*', '?', '!', ''', '"' etc.). I would try to write a patch myself if I had the time... I think the problem is not FAT-specific anyway, because '?' and '*' characters can lead to problems on typical *ix filesystems as well (perhaps not when creating the file, but having wildcards in filenames is always a bad idea). I just tried to encode a CD whose album name is "Cruisin'", and the encoder failed because KAudioCreator did not escape the single-quotes in "Cruisin'" in the command line. The solution to this is not to remove all special characters; the solution is to properly escape them. This should be simple to fix. Please fix it. It seems silly for a KDE app to fail because of something simple like unescaped quotes. This bug seems to be not only about question marks but general unescaped-character issues, thus I add this here. In https://launchpad.net/bugs/71647 a Kubuntu user reported that there are also problems with unescaped tilde characters ("~"). Evidently cddb can return titles which can contain a tilde (~). When encoding this the tilde gets translated into the home dir, which is not expected in this case. Same problem here with reiserfs and an exclamation point : The "output" shows that the "!" was interpreted by some shell as an 'event'...... |
Version: 1.12 (using KDE 3.4.2 Level "b" , SUSE 10.0) Compiler: Target: i586-suse-linux OS: Linux (i686) release 2.6.13-15-smp KAudioCreator fails to create the encoded file from a track that has a question-mark ("?") in the title, if the output location template includes "%{title}", e.g. ~%{extension}/%{albumartist}/%{albumtitle}/%{artist} - %{number} - %{title}.%{extension} It complains that the encoded file was not created. The reason is apparently that the question-mark is interpreted as a wildcard. Two tracks by David Bowie, "Life on Mars?" from "Hunky Dory" and "What's Really Happening?" from "Hours" have so far given me this problem.