I have just tried to encode a 3h38m00s wav file with Lame 3.97b2 from rarewares and the encoding output that is displayed on screen goes nuts.

Lame 3.97b2 output


Lame 3.96.1 output


This is how 3.97b2 looked at the end when encoding the whole wav

Could it be a memory thing? I get something similar with FLAC when I'm multitasking.

this bug is already fixed in CVS (HEAD and 3.97 branch)

Is HEAD the 3.98 alpha line? If so, why don't the changes for 3.98 just get added to the next 3.97 beta/final release?

they are incorporating fixes back to 3.97 as robert just pointed out...

Yes, sorry. It's just I don't very well understand CVS. Anyway, wrong thread... apologies.

So, does this mean we need john33 to update the compiled binaries at RareWares?

Quick CVS primer:

Typically there is HEAD (the trunk), which is where main development happens, and branches (such as 3.97) where patches from HEAD get selectively applied, usually only to fix bugs.

When a release happens, you're getting a snapshot of either a branch, or HEAD. Snapshots of HEAD tend to be fairly unstable since that's where all the newfangled features go.

Robert indicated that this was fixed in HEAD, backported to the 3.97 branch, and thus it will show up in the next 3.97 snapshot (3.97 beta 3, or final, or whatever). Make sense?

the bug was still there when i tried lame 3.98a2 off rarewares

Thanks, Jebus; that does help.


That'll be why the fix hasn't showed up.

ok thats one bug fixed, here is another 2.



Check out the Red boxes, this screenie was taken at the end of the encode, notice that the frame count it stopped on and what the total frames are different.

Also that progress bar at the bottom doesn't end up in the correct place. Maybe this should be changed in to a percent value (e.g %100.00) instead of a time value?

well, maybe your wav file is corrupted, as it indicates a song of over 20 hours missing at end of file?

The base bundles of 3.97beta2 and 3.98alpha2 have both now been updated at Rarewares to reflect these fixes.

Thanks a bunch!

Foobar, Wavpack, Flac, oggdropxp and wavgain have no problems with this wave file

does anybody know of a piece of software i can use to check it?

Any plans to update the bundles with INI setup?

I just opened the same WAV file in Audacity and saved it under another name and tried that with lame, it still reports it as being over 20hours long.

I tried to use Foobar diskwriter to convert it from WAV to WAV, it ended up making the convert WAV 1 hour sorter than the original one, but it worked fine in lame when encoding it.

so the big question is does lame have problems with WAV files over 3h30m in length?

Is there a limit to how big a WAV file can be?

How big is it? Most programs have problems with WAVs bigger than 2GB.

With approx. 1 min. is 10 MB, then 210 mins. (3 hours 30 mins.) is around 2.1 GB...

The Wave file in question is 2.70gigs (4h12m) but i have had the same problem with a 3h30m Wave aswell.

I wonder why Wavpack, Flac, oggdropxp and wavgain have no problems then?

Handling wav files between 2 and 4 gb is a little tricky because the size can appear negative if you're not careful. WavPack had trouble with these also before I fixed it in version 4.2, and many programs still had trouble last time I tried. Fortunately, it's usually pretty easy to fix.

Thanks. And here's a little more strange info on the problem.

I've tried encoding such a >2GB WAV file with LAME (3.90.3 and 3.97b1) and had even more interesting results on top of LAME's misinterpretation of the filesize:

An MP3 made at 320kbps (size well under even 1GB) made from the WAV would freeze some players and tools (including foobar2000) when attempting to import, play or seek.

An MP3 made at 128kbps from the WAV would have absolutely no problems.

I've had no problems with the LAME encoded files using 2.70gig+ wave files in foobar 9b13.

what version of foobar?

0.8.3

I forgot to mention something: I have a similar display problem to that originally described here, but with FLAC.

it looks like the track name is too long for the window...