Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Lame 3.98.4 and bug 2973877 (Read 6570 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Lame 3.98.4 and bug 2973877

I've just encoded a few hundred CDs with XLD based on Lame 3.98.3 using VBR.

In the release announcement for the new XLD based on Lame 3.98.4, everyone was encouraged to re-encode *any* files that were encoded with Lame 3.98.3.  In looking at the Lame bug report however, the only specific problem mentioned is CBR 320.  Can anyone tell me if bug 2973877 is indeed restricted to CBRs?  Are VBRs are always OK?  If not, is there a simple way I can detect if a given MP3 has the problem?  Will it fail to play?

Many thanks.

Denny

Lame 3.98.4 and bug 2973877

Reply #1
I've seen this bug only on some high bitrate CBR files, so far. To test your files, decode them (some batch or maybe with foobar) and look out for messages like the following
Code: [Select]
$ lame --decode --silent <song.mp3> nul:
hip: error audio data exceeds framesize by 146 bytes
hip: Can't rewind stream by 828 bits!

$ madplay -v -q --output=null: <song.mp3>
error: frame 2: Huffman data overrun

Lame 3.98.4 and bug 2973877

Reply #2
I found that mp3packer can also report about errors:

Quote
WARNING: Buffer over/underflow on frame 2 at ~0.05s

or even

Quote
Fatal error: exception Invalid_argument("index out of bounds")


btw Lame doesn't show any errors in the latter case but decoded file is slightly shorter than it should be.

Lame 3.98.4 and bug 2973877

Reply #3
Robert,

Many thanks!  Using lame decode I was able to check my files... all 4400+ of them.

Fortunately, none of the files seems to have had a problem.

Denny

Lame 3.98.4 and bug 2973877

Reply #4
I'm just going to run all of my 3.98.3 files through MP3packer and see if there are any errors. They're all V3, so I'm not too worried here, and this is easier way for me to check than re-encoding with 3.98.4.
God kills a kitten every time you encode with CBR 320

 

Lame 3.98.4 and bug 2973877

Reply #5
In my usage so far, I haven't come across any differences between 3.98.3 and 3.98.4 produced VBR files (comparison run in foobar2000).