Opened 20 months ago
Last modified 20 months ago
#10147 open defect
Failed to process corrupted aac audio in ffmpeg 5.1
Reported by: | ivyabc | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | undetermined |
Version: | 5.1.2 | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description (last modified by )
Summary of the bug:
ffmpeg 5.1.2 fails to skip corrupted aac audio and continue to process good data. git bisect points to this commit:
https://github.com/FFmpeg/FFmpeg/commit/494760f971a41851630d7940abe914cd1115737e
The corrupted file is uploaded to streams.videolan.org
How to reproduce:
ffmpeg -i d04f47da-4a09-4a47-a56a-2d458b9a2c1b.m4a -f null /dev/null ffmpeg 5.0: The input file 17:51-23:46 is corrupted. ffmpeg prints error but can continue to process good data. ffmpeg 5.1: [auto_aresample_0 @ 0x56039de0dd40] [SWR @ 0x56039cb4a340] Rematrix is needed between 30 channels and stereo but there is not enough information to do it [auto_aresample_0 @ 0x56039de0dd40] Failed to configure output pad on auto_aresample_0 Error reinitializing filters! Failed to inject frame into filter network: Invalid argument Error while processing the decoded data for stream #0:0 Conversion failed!
ffmpeg -i d04f47da-4a09-4a47-a56a-2d458b9a2c1b.m4a -vn -c:a aac -b:a 128k -ac 2 audio.m4a
Expected: 17:51-23:46 has no sound. Sound continues after 23:46.
Actual: Fails at 17:51
Change History (3)
comment:1 by , 20 months ago
Description: | modified (diff) |
---|
comment:2 by , 20 months ago
Summary: | Failed to process corrupted aac audio in 5.1 → Failed to process corrupted aac audio in ffmpeg 5.1 |
---|
Note:
See TracTickets
for help on using tickets.
https://streams.videolan.org/ffmpeg/incoming/10147/
17:51 indeed.
aac: SBR was found before the first channel element.
ffplay.exe -acodec libfdk_aac
allows to play at 1406 seconds, i.e. 23:26, while -ss 23:25 already gives some warnings.
It appears after some time it fails (see no "stereo" word, another bug)
Maybe the reason is that fix that allowed 48 channel decoding ced6a5affb0ab1a24278b9bade76c36b8636e267