Thread: [Mpg123-users] writing to stdout cuts short
Brought to you by:
sobukus
From: poncenby <sm...@po...> - 2007-06-02 09:34:18
|
Hi list, i'm using mpg123 in conjunction with JustePort in order to stream to airtunes boxen. i use mpg123 -s tune.mp3 | JustePort.exe - 192.168.1.33 0 this works fine however the last few seconds of the stream are cut off and a message is displayed saying [3:55] Decoding of tune.mp3 finished i'm really not sure why this would happen as mpg123 is (as far as I can tell) decoding the whole file, perhaps JustePort is finishing when mpg123 is finishing, but it shouldn't as there should still be stuff being piped to it. any ideas? thanks for your time poncenby |
From: Thomas O. <tho...@or...> - 2007-06-03 10:12:22
Attachments:
signature.asc
|
Am Sat, 02 Jun 2007 10:34:07 +0100 schrieb poncenby <sm...@po...>:=20 > Hi list, >=20 > i'm using mpg123 in conjunction with JustePort in order to stream to=20 > airtunes boxen. >=20 > i use mpg123 -s tune.mp3 | JustePort.exe - 192.168.1.33 0 On what system is this? Is this cygwin (wondering about the .exe)? >=20 > this works fine however the last few seconds of the stream are cut off=20 > and a message is displayed saying >=20 > [3:55] Decoding of tune.mp3 finished Well that message is normal. Is the reported length correct (3:55)? =20 > i'm really not sure why this would happen as mpg123 is (as far as I can=20 > tell) decoding the whole file, perhaps JustePort is finishing when=20 > mpg123 is finishing, but it shouldn't as there should still be stuff=20 > being piped to it. JusePort should finish when the pipe finishes. That should be when everythi= ng written by mpg123 has been read -- even after mpg123 ended. There should be nothing missing. First, please share the info what system / software environment (including = mpg123 version) your are working with, then we can start wondering what spe= cial property is the problem. What you also can try is to check the file size created by mpg123 -s tune.mp3 > tune.raw The size in bytes, divided by channel count, sample rate and 2 (for 16 bit = samples) should give you the length in seconds... If that is correct, you problem may lie within your shell or OS... hm, but = I don't want to speculate too much now. Thomas. |
From: poncenby <sm...@po...> - 2007-06-03 21:44:53
|
Thomas Orgis wrote: > Am Sat, 02 Jun 2007 10:34:07 +0100 > schrieb poncenby <sm...@po...>: > >> Hi list, >> >> i'm using mpg123 in conjunction with JustePort in order to stream to >> airtunes boxen. >> >> i use mpg123 -s tune.mp3 | JustePort.exe - 192.168.1.33 0 > > On what system is this? Is this cygwin (wondering about the .exe)? >> this works fine however the last few seconds of the stream are cut off >> and a message is displayed saying sorry, completely forgot any useful information. Linux ziggy 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux mpg123 version is: High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3 version 0.61; this is a macbook. in the command above JustePort.exe is run by mono. >> [3:55] Decoding of tune.mp3 finished > > Well that message is normal. Is the reported length correct (3:55)? the lengths are always correct. > >> i'm really not sure why this would happen as mpg123 is (as far as I can >> tell) decoding the whole file, perhaps JustePort is finishing when >> mpg123 is finishing, but it shouldn't as there should still be stuff >> being piped to it. > > JusePort should finish when the pipe finishes. That should be when everything written by mpg123 has been read -- even after mpg123 ended. > There should be nothing missing. > First, please share the info what system / software environment (including mpg123 version) your are working with, then we can start wondering what special property is the problem. > What you also can try is to check the file size created by > > mpg123 -s tune.mp3 > tune.raw > > The size in bytes, divided by channel count, sample rate and 2 (for 16 bit samples) should give you the length in seconds... this value is correct. > If that is correct, you problem may lie within your shell or OS... hm, but I don't want to speculate too much now. > > > Thomas. > > > -- > This email has been verified as Virus free > Virus Protection and more available at http://www.plus.net > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Mpg123-users mailing list > Mpg...@li... > https://lists.sourceforge.net/lists/listinfo/mpg123-users |
From: Thomas O. <tho...@or...> - 2007-06-04 01:03:30
Attachments:
signature.asc
|
Am Sun, 03 Jun 2007 22:44:41 +0100 schrieb poncenby <sm...@po...>:=20 =20 > this is a macbook. Ah, Nicholas area;-) You may especially be interested in the new 0.66 release, since it includes= SSE optimizations for your machine... > in the command above JustePort.exe is run by mono. > > mpg123 -s tune.mp3 > tune.raw > >=20 > > The size in bytes, divided by channel count, sample rate and 2 (for 16 = bit samples) should give you the length in seconds... >=20 > this value is correct. I'm tempted to blame mono, then. Another test would be mpg123 -s tune.mp3 | cat > tune.raw You should have the same situation then like when using JustePort -- mpg123= ends, but cat gets the rest fed via stdin and the created tune.raw should = be exactly the same as before. Perhaps you should consult the mono folks, then? When it works with the pipe to cat, It can hardly be mpg123's fault... Alrighty then, Thomas. |