#11005: Damaged MP4 rejected by ffmpeg, mkvtoolnix can read it fine
-------------------------------------+-------------------------------------
Reporter: PumaD | Type: defect
Status: new | Priority: normal
Component: | Version: git-
undetermined | master
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Got a multi GiB file which is unfortunately damaged and all players I
tested refuse to play. I almost deleted it but then had the idea to run it
though mkvtoolnix. It managed to salvage it almost completely with just
minor visual artifacts during playback.
Would be great if ffmpeg could do the same.
How to reproduce:
{{{
$ ffmpeg -i slightly-damaged.mp4 out.mp4
ffmpeg version N-115112-g39ce8a9695 Copyright (c) 2000-2024 the FFmpeg
developers
built with gcc 13.2.1 (GCC) 20240417
configuration:
libavutil 59. 17.100 / 59. 17.100
libavcodec 61. 5.103 / 61. 5.103
libavformat 61. 3.103 / 61. 3.103
libavdevice 61. 2.100 / 61. 2.100
libavfilter 10. 2.101 / 10. 2.101
libswscale 8. 2.100 / 8. 2.100
libswresample 5. 2.100 / 5. 2.100
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x609423feb840] Invalid sample size -1251017134
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x609423feb840] error reading header
[in#0 @ 0x609423feb580] Error opening input: Invalid data found when
processing input
Error opening input file slightly-damaged.mp4.
Error opening input files: Invalid data found when processing input
}}}
Tested with ffmpeg 6.1.1 as well as git master from yesterday.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11005>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
