also mpg123 seems to not like catching a stream from stdin.  The only way
this works is if mpg123 gets a frame on stdin with nothing else before it,
like a partial frame.  If the encoding changes, like say if it wanted to
change from 128k to 256k, mpg123 simply ignores the frames. so if mpg123
decides that it is receiving some kind of frame that it really isn't, it
is necessary to restart mpg123 and hope it will sync up with the stream
properly.

_J

In the new year, Felix von Leitner wrote:
> Thus spake Robert Hegemann ([EMAIL PROTECTED]):
> > > By the way: has anyone of you noticed that mpg123 can't play lame
> > > encoded mp3s if they contain 320 kbps bitrates?  Seems to be mpg123's
> > > fault, I'm going to complain to the author about it now ;)
> > No, I haven't seen such faults. No problems with latest mpg123 (0.59r?)
> > or xmms for me.
> 
> Doesn't xmms use a different engine?  I don't use xmms.
> I use mpg123 0.59r, too, and it repeatedly bombs on "-v -V 0" encoded
> songs.  A friend of mine apparently likes -V 0 and he has had the same
> problems with mpg123, so it is not an isolated issue.
> 
> Felix
> --
> MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
> 

--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )

Reply via email to