Opened 16 months ago

Last modified 12 months ago

#11452 new defect

AAC audio track does not play in ffplay

Reported by: v0lt Owned by:
Priority: normal Component: avcodec
Version: 7.1 Keywords: aac
Cc: MasterQuestionable Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description (last modified by v0lt)

Summary of the bug:
The video starts playing with sound, but after 1-2 seconds the sound disappears and there are many errors in the console.
https://www.mediafire.com/file/rpj4e32o1l205vt/River.mp4/file

How to reproduce:

ffplay -hwaccel vulkan -y 720 River.mp4

fplay version 2025-02-02-git-957eb2323a-full_build-www.gyan.dev Copyright (c) 2003-2025 the FFmpeg developers

There is also a problem with ffmpeg.

ffmpeg -i River.mp4 test.mp4

More information in ffplay_output.txt and ffmpeg_output.txt (see attachments).

The file plays correctly in MPC-BE x64 1.8.2 and VLC 3.0.21.

Attachments (2)

ffplay_output.txt (23.2 KB ) - added by v0lt 16 months ago.
ffmpeg_output.txt (45.0 KB ) - added by v0lt 16 months ago.

Download all attachments as: .zip

Change History (5)

by v0lt, 16 months ago

Attachment: ffplay_output.txt added

by v0lt, 16 months ago

Attachment: ffmpeg_output.txt added

comment:1 by v0lt, 16 months ago

Description: modified (diff)

comment:2 by MasterQuestionable, 16 months ago

Cc: MasterQuestionable added
Component: undeterminedavcodec
Keywords: aac added

͏    Related? (“"Reserved bit set" errors”)
͏    https://trac.ffmpeg.org/ticket/10008

comment:3 by Nicolas Gaullier, 12 months ago

I don't know if there are more significant issues, but the first errors are pretty serious:
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f0fb0000c80] STSC entry 4 is invalid (first=4 count=19 id=1)
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f0fb0000c80] STSC entry 3 is invalid (first=3 count=18 id=1)
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f0fb0000c80] STSC entry 2 is invalid (first=2 count=19 id=1)

A dump makes it clear the stsc is broken:
<SampleToChunkBox Size="2164" Type="stsc" Version="0" Flags="0" Specification="p12" Container="stbl" EntryCount="179">
<SampleToChunkEntry FirstChunk="1" SamplesPerChunk="27" SampleDescriptionIndex="1"/>
<SampleToChunkEntry FirstChunk="2" SamplesPerChunk="19" SampleDescriptionIndex="1"/>
<SampleToChunkEntry FirstChunk="2" SamplesPerChunk="19" SampleDescriptionIndex="1"/>
<SampleToChunkEntry FirstChunk="3" SamplesPerChunk="18" SampleDescriptionIndex="1"/>

The second entry is repeated twice.
Never seen that before, very specific... Here it seems clear that the entry is doubled and the second one can be ignored, of course, but really this is not a clean patch nor a safe hack to support that kind of corrupted files in a general manner.
BTW, be careful with corrupted files 'supported' by some systems one day; they may not be supported another day.

Note: See TracTickets for help on using tickets.