Robert Hegemann wrote:
[snip]
OK, here is the statement out of
"MPEG Layer3 / Bitstream Syntax and Decoding"
quote
If the words (CRC checksum and transmitted values) are not
identical, a transmission error has occured in the protected
field of the bitstream. To avoid annoying
David Bridson wrote:
That seems to be the world upside down. Adapting an encoder in order
to fit a non-mp3-compliant player is no good move I think. Best is to
contact the mpg123 author?
I don't think it's just mpg123 - I have problems playing same file in
CL-Amp under BeOS with VBR MP3s
David Bridson wrote:
That seems to be the world upside down. Adapting an encoder in
order
to fit a non-mp3-compliant player is no good move I think. Best is
to
contact the mpg123 author?
I don't think it's just mpg123 - I have problems playing same file
in
CL-Amp under BeOS with VBR
If mpg123 needs all frames to have CRC, can the VBR header contain a CRC?
Or would the CRC cause problems if it were to be embedded in a VBR header?
Shawn
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Hello Shawn,
Monday, July 03, 2000, 6:44:12 PM, you wrote:
SR If mpg123 needs all frames to have CRC, can the VBR header contain a CRC?
SR Or would the CRC cause problems if it were to be embedded in a VBR header?
That seems to be the world upside down. Adapting an encoder in order
to fit a
Mark Taylor schrieb am Mon, 03 Jul 2000:
Thanks Mathew, I just changed VbrTag.c to set
the CRC bit for the Xing-VBR tagging frame
like the first frame.
Now mpg123 works with protected VBR files.
Robert
This is probabaly the right thing to do, but:
Now, the Xing
Robert wrote-
Now mpg123 works with protected VBR files.
Mark wrote-
This is probabaly the right thing to do, but:
Now, the Xing VBR header is actually a corrupt mp3 frame. Before this
fix, the Xing header was a valid mp3frame which would decode to silence.
So mpg123 now works, but there
It appears that CRC checking in lame produces something that can't be played
back using mpg123.
while bladeenc seems to work okay. just thought this might be a bug in lame.
I am using "lame -p -v -h -b 128"
and the output when i try to play it back is.
