Get the following error in foobar 0.8 beta 5 on playback of file made using 2.1.6.9 profile transparent.

ERROR (foo_input_std) : Maximum number of scalefactor bands exceeded
ERROR (foo_input_std) : MP4: decode error.

Edit 0.8 not 0.5

foobar .5 beta 5?

I can (unfortunately) verify this problem. QuickTime plays the files fine, so it seems the decoder (FAAD) is at fault.

I remember seeing it before with a very low bitrate HE-AAC file from the old encoder.

Menno?

I had this sort of problems with Nero aac files for months.. foobar console popping up and giving this or other decode errors, repeatable.
Can't remember which errors exactly (I made a thread in foobar - bug reports some day), I already ditched Nero und the codec and will never go back anyway

Menno just confirmed it's a bug in the decoder. So it's safe to update except that you may have to wait a day before you can play em back with foobar (or anything using FAAD decoder)

Fixed already. Sorry for the inconvenience

Menno

@menno

Fixed exactly what? What file am I supposed to download?

Very logical comment considering the bug rufu meantioned is in foobar 0.8beta faad2 plugin....

The FAAD2 decoder that is used in foobar and several other audio players.

You will want to download an updated foobar in an hour or so.

A whole hour?

Gee that's like forever

Just glad that it's safe to update. Though I've noiticed that files are larger with this encoder,and my 20GB iPod is nearly full , guess it's time to trim the fat from my music collection

In 2.6.1.9 I think the "internet"-profile should be near 128kbps average. Streaming is somewhat higher.

Fixed FAAD2 decoders: foobar2000 0.8beta, Winamp 2.x/5.x, faad.exe.

That foobar plugin is compiled with the latest 0.8 SDK, so you need a new Foobar2000 0.8b6 from here also:
http://www.foobar2000.org/beta.html

Btw. the FAAD2 decoding problem seems to be only in Foobar 0.8betas, not earlier Foobars. The official foobar2000 0.7.7b doesn't give me this error, but 0.8beta gives (before this fix).

That was a different issue - old problem was, indeed, in the encoder (lookup table overflow) which produced invalid frames. It was fixed long time ago.

I guess that includes CoreAAC DSF too? rjamorim, can you help us out? Thanks!

I don't think so, unless there was a new CoreAAC released just some days ago. The bug in FAAD2 was in very recent version.
The CoreAAC version I have works ok, and it's pretty new.

Hmmm, the Rarewares rjamorim link is for v 1.0b9, dated 2004-02-03. I don't know if that's the source date or the build date. Sounds like the source might be new enough to have the bug. It's definitely a day early for the fix!

Update: I installed the 02-03 and it says based on AAC Decoder v1.1 and FAAD2 2.0 RC3. I went to audiocoding.com to see if RC3 is affected but didn't have time to find release notes. I'm sure someone here can tell me.

Hmm.. yeah, that is too new indeed. Only 2 days old.
It seems to be affected. For me there's a blip-artifact with this CoreAAC in the position where foobar 0.8beta (before fixing) stopped playing.

But yeah, CoreAAC needs updating. Bad luck that it was updated just after the faad decoding bug appeared..

All new compiles at Rarewares now.