k3b --audiocd "$FILES" problem

bendeco13 · 03-21-2005, 05:02 PM

Say I have this script:

Code:

FILES='"/dir/to/1.mp3" "/dir/to/2.mp3"'
k3b --audiocd "$FILES" &
exit 1

Everytime I try this, k3b returns with a dialog that would say:
Could not find the following files:
/home/bendeco/"/dir/to/1.mp3" "/dir/to/2.mp3"

with "/home/bendeco/" being the directory in which I ran the script.

Why does it include the current directory and does anyone know of a way around this?
Its driving me insane....

It works fine from the command:
k3b --audiocd "/dir/to/1.mp3" "/dir/to/2.mp3"

Thanks in advance!!!
Bendeco

bendeco13 · 03-22-2005, 03:19 PM

Well I got it working... well not exactly this code...
I ended up communicating with k3b through the dcop interface...

If anyone does indeed go through the trouble of figuring this out...
I'd still be very curious of how this works.

I think that the problem is that the quotations ("") get cancelled out when the files are being added to k3b.

Thanks Anyways
Bendeco

TheLinuxDuck · 03-22-2005, 03:44 PM

I'd say that the problem has to do with the fact that the variable FILES in a ' enclosed string, which contains ". Then, the call to k3b wraps it in "", so in effect, the code is trying:

Code:

k3b --audiocd ""/dir/to/1.mp3" "/dir/to/2.mp3"" &

I'd suggest just removing the "" around the variable in the call to k3b, and I bet it will work fine.

bendeco13 · 03-29-2005, 09:45 PM

I already tried removing the quotes from the call to k3b and it doesn't work, all it does is reads each part of the files as seperate files. Say I have an mp3 like: /home/joe/new song.mp3
the call:
k3b --audiocd $FILES &

causes k3b to read /home/joe/new as a file and song.mp3 as a file.

Thanks anyways....

AM1SHFURN1TURE · 03-29-2005, 11:11 PM

I'll give this a shot taking my best guess.

you see this:

""/dir/to/1.mp3" "/dir/to/2.mp3""

i think it should be like this:

""dir/to/1.mp3" "dir/to/2.mp3""

What I'm thinking is that those two forward slashes are making k3b start the path to the mp3 from the root of your hd.

This is only a wild guess, and it may be completely wrong, but it could be worth a try if you are still stuck.