#2 Problem with parsing input and output dirs

[Hameed]

When you feed audenc a directory with a comma in the name, it fails and doesn't continue or crash.

Example:
$ audenc vorbis Music/MP3/Charlie\ Mars/Like\ a\ Bird\,\ Like\ a\ Plane/ Music/OGG/Charlie\ Mars/Like\ a\ Bird\,\ Like\ a\ Plane/

Produces this:
mplayer: could not connect to socket
mplayer: No such file or directory

and stops. You need to interrupt (Ctrl+C) to get back to the prompt. If you manually look at the output directory (Music/OGG/Charlie\ Mars/), you see a file 'Like a Bird' and a folder 'Like a Bird, Like a Plane'.

This is kind of annoying when used in conjunction with find, which is what I'm doing:
$ find Input\ Music -type d -exec audenc vorbis {} convert/{} \;
That works just fine for me (yes I know it's not the prettiest, but it does exactly what it should), and it just stops dead. You have to manually go through and move all the songs with any comma in their name elsewhere and deal with them some other way. Yes I have a automate process for that too, but that's not the point.

[microchip]

I don't have a problem with directories that contain a comma and nor do I have a problem with files that do so to. In fact, I just tested it by running:

audenc vorbis "test, 1" "foobar"

Notice that I place the input and output dirs inside quotes. Inside the "test, 1" directory, there's a file named "sample, 01.mp3". audenc is successfully able to encode that sample which contains a comma and it did not have any problems with the input directory which also contains a comma.

[Hameed]

Re: microbooster
Tried that. Still the same problem.