hi! i've experienced the same problem, but have read dir2ogg source code a 
little. after understanding a bit, i've created ~/.bin/mpg123, which overrides 
/usr/bin/mpg123 and does only the following:
#!/bin/bash
echo "$0 $@" > /tmp/mpg123
and here is what i get when i run smth like "dir2ogg -t filename.mp3":
/home/dimas/.bin/mpg123 -q -w /dev/stdout /home/<...>/01 - F.T.W..mp3
well, i thought that it's mpg123 bug and dug around. with "-w filename.wav" it 
works fine. well, i've updated mpg123 package and after nothing changed, i 
noticed this in changelog:
> mpg123 (1.14.2-1) unstable; urgency=low
> 
>   * New upstream release.
>     - Fix writing of WAV to stdout.
> 
>  -- Miguel A. Colón Vélez <[email protected]>  Sat, 12 May 2012 
> 13:30:02 -0400
fixed? hm... yes, almost! so, THE PROBLEM IS:
if you specify stdout using dash (like "-w -") it works, damn! but with "-w 
/dev/stdout" (exactly what dir2ogg does) it fails.
so i ask maintainer or upstream dev to fix that behaviour, since i'm not 
familiar enough with python.
and now i'll also fire up the bug for mpg123.

and here is workaround utill things get fixed: create a function named "mpg123" 
in your .bashrc or ~/.bin/mpg123 (make sure it's set up in .profile, and this 
path preceds /usr/bin in $PATH) containg the following:
eval /usr/bin/mpg123 `echo "$@" | sed 
's|/dev/stdout|-|;s|\(/.*\.mp3\)|\"\1\"|g'`

haven't tested with .bashrc function, but script in ~/.bin works fine. don't 
forget to add "#!/bin/bash" in case of script))



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to