FAAD 2.8.8 crashes with some MP4 files (e.g. Youtube) where 2.7 did not about faad2 HOT 5 CLOSED

Update:

Problem is caused by the following line returning NULL and memset'ing the frameInfo to all zero:

sample_buffer = NeAACDecDecode(hDecoder, &frameInfo, mp4config.bitbuf.data, mp4config.bitbuf.size);

We get division by zero, because frameInfo.channels is zero, but frameInfo.samples is zero too.

But I guess the "real" problem here is that the returned sample_buffer ends up being NULL.

The first couple of calls to NeAACDecDecode() do not return NULL though!

I tried to insert a continue statement in case that sample_buffer is NULL, but it results in infinite loop.

(So, once NULL was returned, all subsequent calls return NULL as well)

from faad2.

I guess the decoder should simply abort if there is an AAC frame that it cannot parse.

I tried to insert a continue statement in case that sample_buffer is NULL, but it results in infinite loop.

What if you add break there?

from faad2.

If I add a break, then it will stop decoding very quickly and leave an (almost) empty WAV file.

My guess: The new MP4 parsing code introduced in FAAD v2.8 does not support MP4 files containing a video stream – or, more generally, MP4 files with more than a single stream – yet.

If we have more than one stream, the "MDAT" atom of the MP4 file will contain chunks of the various streams, in an interleaved fashion. For this reason, it is necessary to parse the chunk offsets and lengths from the tables in the "MOOV" atom, and then jump to the chunks belonging to the desired stream.

Simply assuming that the "MDAT" atom contains a sequence of AAC frames (all belonging to the same stream) is not going work for files with more than one stream! ...and thus for most MP4 files out there.

I hope this can be fixed, because otherwise we will be stuck with FAAD 2.7 😟

from faad2.

Just wondering, any chance for a fix? ❓

from faad2.

Bump ✨

from faad2.