Am Wed, 4 Jul 2012 14:25:56 +0400
schrieb dimas :
> well, in my case:
>
> >14:19:03 186 ~/downloads/music/Sword/1986 Metalized$ /usr/bin/mpg123 -q -w
> >/dev/stdout 01.mp3 | file -
Ah, everyday I learn something new. I did not know that there is a
difference for a program between
$ prog > out
well, in my case:
>14:19:03 186 ~/downloads/music/Sword/1986 Metalized$ /usr/bin/mpg123 -q -w
>/dev/stdout 01.mp3 | file -
[wav.c:143] error: cannot even write a single byte: Illegal seek
[audio.c:630] error: failed to open audio device
[mpg123.c:902] error: Failed to initialize output, goodbye.
What exactly fails? With 1.14.3 (also 1.14.2, actually) I do this:
$ mpg123 -w - bla.mp3 > bla.wav
$ mpg123 -w /dev/stdout bla.mp3 > bla2.wav
$ md5sum bla*.wav
ebcdd5f3136e11265c99c578815c4b9b bla2.wav
ebcdd5f3136e11265c99c578815c4b9b bla.wav
Same for trunk ... at least for a single file, I don
0. because, imho, good program should correctly handle as much aliases as
possible, not limiting to "-" only, but also "/dev/stdout", "/dev/fd/1" or
whatever it can be.
1. it was working for a long time until got broken in some of recent versions
2. not only dir2ogg may rely on that behaviour.
o
On Tue, Jul 3, 2012 at 5:16 PM, dimas wrote:
> Package: mpg123
> Version: 1.14.2+svn20120622-1
> Severity: normal
>
> hello.
> after recent upgrade on Debian testing i've found that dir2ogg (that uses
> mpg123 directly) fails to do the job. pleasee see #679813 for details.
> after digging around
Package: mpg123
Version: 1.14.2+svn20120622-1
Severity: normal
hello.
after recent upgrade on Debian testing i've found that dir2ogg (that uses
mpg123 directly) fails to do the job. pleasee see #679813 for details.
after digging around i've also read this in mpg123's changelog:
> mpg123 (1.14.2-1
