[FFmpeg-user] Error with mp4 files moov atom (\moov\trak\mdia\minf\stbl\sgpd)
barsnick at gmx.net
Thu Dec 13 22:39:58 EET 2018
On Thu, Dec 13, 2018 at 15:04:15 -0500, Karen Norton wrote:
> I only see the error when opening the output files with MP4 Inspector
> otherwise the files play fine (ex: in VLC) and show no issues in
So basically, it's not an issue at all, *except* for MP4 Inspector?
> I wouldn't have even know this was an issue because everything appears fine
> with V90893. I only discovered this because I just downloaded MP4 Inspector
> to try.
See what I mean. ;-)
> The exact error in MP4 Inspector is:
> Failed on reading box header, parent box path
> "\moov\trak\mdia\minf\stbl\sgpd", stream position "0x1C7362678B6399",
> reason "The box size 0 exceeds the remaining file length
> -8,008,165,506,864,740." (I have attached a screenshot of the error).
I don't want to seem rude - but why would you trust a tool which
reports negative file sizes?
In other words: Why should MP4 Inspector be more correct than ffmpeg?
Perhaps they have a bugfix release? ;-)
> ffmpeg 90893 (not working in MP4 Inspector):
> Command: ffmpeg -i inputs01e01.mp4 -metadata media_type="10" -metadata
> title="Law & Order" -metadata show="Prescription For Death" -metadata
> season_number="1" -metadata genre="Crime, Drama, Mystery" -metadata
> episode_id="66209" -metadata episode_sort="1" -metadata:s:a:0 language=eng
> -c:v libx264 -vf hflip -c:a copy outputs01e01.mp4
Can you create such files ("broken" for MP4 Inspector) with arbitrary
input? I.e. with
$ ffmpeg -f lavfi -i testsrc -t 1 -c:v libx264 output.mp4
Or does it depend on your particular input?
Too bad MP4 Inspector doesn't run under Wine, otherwise I'd try to
More information about the ffmpeg-user