[FFmpeg-trac] #11005(avformat:closed): Damaged MP4 rejected by ffmpeg, mkvtoolnix can read it fine
FFmpeg
trac at avcodec.org
Mon Jun 10 04:41:45 EEST 2024
#11005: Damaged MP4 rejected by ffmpeg, mkvtoolnix can read it fine
------------------------------------+------------------------------------
Reporter: PumaD | Owner: (none)
Type: defect | Status: closed
Priority: normal | Component: avformat
Version: git-master | Resolution: fixed
Keywords: mp4 | Blocked By:
Blocking: | Reproduced by developer: 1
Analyzed by developer: 1 |
------------------------------------+------------------------------------
Comment (by PumaD):
Remuxing with mkvtoolnix fixes the freeze, otherwise I wouldn't have
reported it. Not just similar-looking frames. There's even a bit of
movement making it easy to see.
I noticed that ffplay shows these messages with the original file at the
time of the freeze:
{{{
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x712350000c80] Packet corrupt (stream = 1, dts
= 113707010).
[aac @ 0x712350008240] channel element 2.0 is not allocated
[aac @ 0x712350008240] channel element 2.0 is not allocated
[aac @ 0x712350008240] Sample rate index in program config element does
not match the sample rate index configured by the container.
[aac @ 0x712350008240] channel element 3.1 is not allocated
[h264 @ 0x7123505c8e00] concealing 1127 DC, 1127 AC, 1127 MV errors in P
frame
}}}
Playing the file remuxed by mkvtoolnix only shows these messages:
{{{
[aac @ 0x74e870005480] channel element 2.0 is not allocated
[aac @ 0x74e870005480] channel element 2.0 is not allocated
[h264 @ 0x74e870324100] concealing 1127 DC, 1127 AC, 1127 MV errors in P
frame
}}}
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11005#comment:24>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list