IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
FAAD2 bug, (fixed already)
rufu
post Feb 4 2004, 20:26
Post #1





Group: Members
Posts: 75
Joined: 28-July 03
Member No.: 8044



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

This post has been edited by rufu: Feb 4 2004, 21:36
Go to the top of the page
 
+Quote Post
indybrett
post Feb 4 2004, 20:33
Post #2





Group: Members (Donating)
Posts: 1302
Joined: 4-March 02
From: Indianapolis, IN
Member No.: 1440



foobar .5 beta 5?


--------------------
Wait Master, it might be dangerous... you go first.
Go to the top of the page
 
+Quote Post
Garf
post Feb 4 2004, 20:33
Post #3


Server Admin


Group: Admin
Posts: 4408
Joined: 24-September 01
Member No.: 13



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


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? huh.gif
Go to the top of the page
 
+Quote Post
sony666
post Feb 4 2004, 20:40
Post #4





Group: Members
Posts: 573
Joined: 22-February 02
Member No.: 1375



QUOTE (rufu @ Feb 4 2004, 08:26 PM)
Get the following error in foobar 0.5 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.

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 sad.gif
Go to the top of the page
 
+Quote Post
Garf
post Feb 4 2004, 20:53
Post #5


Server Admin


Group: Admin
Posts: 4408
Joined: 24-September 01
Member No.: 13



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) smile.gif
Go to the top of the page
 
+Quote Post
menno
post Feb 4 2004, 21:01
Post #6


Nero MPEG4 developer


Group: Developer (Donating)
Posts: 1187
Joined: 11-October 01
From: LA
Member No.: 267



Fixed already. Sorry for the inconvenience blush.gif

Menno
Go to the top of the page
 
+Quote Post
eagleray
post Feb 4 2004, 21:06
Post #7





Group: Members
Posts: 265
Joined: 15-December 03
Member No.: 10452



@menno

Fixed exactly what? What file am I supposed to download?
Go to the top of the page
 
+Quote Post
JohnV
post Feb 4 2004, 21:13
Post #8





Group: Developer
Posts: 2797
Joined: 22-September 01
Member No.: 6



QUOTE (sony666 @ Feb 4 2004, 09:40 PM)
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 sad.gif

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


--------------------
Juha Laaksonheimo
Go to the top of the page
 
+Quote Post
Garf
post Feb 4 2004, 21:19
Post #9


Server Admin


Group: Admin
Posts: 4408
Joined: 24-September 01
Member No.: 13



QUOTE (eagleray @ Feb 4 2004, 10:06 PM)
@menno

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

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.
Go to the top of the page
 
+Quote Post
eagleray
post Feb 4 2004, 21:21
Post #10





Group: Members
Posts: 265
Joined: 15-December 03
Member No.: 10452



A whole hour? wink.gif
Go to the top of the page
 
+Quote Post
rufu
post Feb 4 2004, 21:40
Post #11





Group: Members
Posts: 75
Joined: 28-July 03
Member No.: 8044



QUOTE (Garf @ Feb 4 2004, 12:19 PM)
You will want to download an updated foobar in an hour or so.

Gee that's like forever tongue.gif

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 crying.gif, guess it's time to trim the fat from my music collection
Go to the top of the page
 
+Quote Post
JohnV
post Feb 4 2004, 21:44
Post #12





Group: Developer
Posts: 2797
Joined: 22-September 01
Member No.: 6



QUOTE (rufu @ Feb 4 2004, 10:40 PM)
QUOTE (Garf @ Feb 4 2004, 12:19 PM)
You will want to download an updated foobar in an hour or so.

Gee that's like forever tongue.gif

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 crying.gif, 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.


--------------------
Juha Laaksonheimo
Go to the top of the page
 
+Quote Post
Case
post Feb 4 2004, 21:55
Post #13





Group: Developer (Donating)
Posts: 1605
Joined: 19-October 01
From: Finland
Member No.: 322



Fixed FAAD2 decoders: foobar2000 0.8beta, Winamp 2.x/5.x, faad.exe.
Go to the top of the page
 
+Quote Post
JohnV
post Feb 4 2004, 22:02
Post #14





Group: Developer
Posts: 2797
Joined: 22-September 01
Member No.: 6



QUOTE (Case @ Feb 4 2004, 10:55 PM)
Fixed FAAD2 decoders: foobar2000 0.8beta,

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


--------------------
Juha Laaksonheimo
Go to the top of the page
 
+Quote Post
JohnV
post Feb 4 2004, 22:09
Post #15





Group: Developer
Posts: 2797
Joined: 22-September 01
Member No.: 6



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).


--------------------
Juha Laaksonheimo
Go to the top of the page
 
+Quote Post
Ivan Dimkovic
post Feb 4 2004, 22:12
Post #16


Nero MPEG4 developer


Group: Developer
Posts: 1465
Joined: 22-September 01
Member No.: 8



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


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.
Go to the top of the page
 
+Quote Post
calinb
post Feb 4 2004, 22:57
Post #17





Group: Members
Posts: 8
Joined: 27-October 03
Member No.: 9486



QUOTE (Garf @ Feb 4 2004, 11:53 AM)
you may have to wait a day before you can play em back with foobar (or anything using FAAD decoder) smile.gif

I guess that includes CoreAAC DSF too? rjamorim, can you help us out? Thanks!
Go to the top of the page
 
+Quote Post
JohnV
post Feb 4 2004, 23:10
Post #18





Group: Developer
Posts: 2797
Joined: 22-September 01
Member No.: 6



QUOTE (calinb @ Feb 4 2004, 11:57 PM)
QUOTE (Garf @ Feb 4 2004, 11:53 AM)
you may have to wait a day before you can play em back with foobar (or anything using FAAD decoder) smile.gif

I guess that includes CoreAAC DSF too?

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.


--------------------
Juha Laaksonheimo
Go to the top of the page
 
+Quote Post
calinb
post Feb 5 2004, 00:05
Post #19





Group: Members
Posts: 8
Joined: 27-October 03
Member No.: 9486



QUOTE (JohnV @ Feb 4 2004, 02:10 PM)
QUOTE

I don't think so, unless there was a new CoreAAC released just some days ago.

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.

This post has been edited by calinb: Feb 5 2004, 01:08
Go to the top of the page
 
+Quote Post
JohnV
post Feb 5 2004, 01:21
Post #20





Group: Developer
Posts: 2797
Joined: 22-September 01
Member No.: 6



QUOTE (calinb @ Feb 5 2004, 01:05 AM)
QUOTE (JohnV @ Feb 4 2004, 02:10 PM)
QUOTE

I don't think so, unless there was a new CoreAAC released just some days ago.

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..


--------------------
Juha Laaksonheimo
Go to the top of the page
 
+Quote Post
john33
post Feb 5 2004, 12:28
Post #21


xcLame and OggDropXPd Developer


Group: Developer
Posts: 3419
Joined: 30-September 01
From: Bracknell, UK
Member No.: 111



All new compiles at Rarewares now. wink.gif


--------------------
John
----------------------------------------------------------------
My compiles and utilities are at http://www.rarewares.org/
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st November 2009 - 08:26