Main Menu

Truncated Data

Started by velezericn, April 15, 2023, 03:30:58 PM

Previous topic - Next topic

velezericn

So i have a python script where i'm writing metadata to mp4s

cmd = [exiftool_path, "-overwrite_original","-CreateDate={}".format(date_and_time_no_dashes), file]

So i'm able to write to mp4s and apply meta data perfectly fine but sometimes i get

Warning: Truncated 'moov' data (missing 5721 bytes)
or
Warning: Truncated 'mdat' data

Truncated moov data doesn't display metadata when i check it in exiftool but truncated mdat data will sometimes be fine and no problem or it'll not show in exiftool

why is it that it sometimes truncates? is it due to file corruption of mp4? i'm not really sure whats going on

Phil Harvey

The truncated media data is indicative of a corrupted file.  This can happen if a transfer (eg. download) is aborted before the full file is received.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

penginex

I have the same problem, I think the video file is fine and the command I use is:

exiftool -api LargeFileSupport -m -p C:\Windows\gpx.fmt -ee3 D:/Photo/Insta360/VID_20230618_184959_00_041.insv > C:\Desktop\aa.txt

Results:

Warning: Truncated '?\x00\x00\x00' data - D:/Photo/Insta360/VID_20230618_184959_00_041.insv

But.. Now insta360 studio 4.8.0 You can now export gpx  :o

Phil Harvey

That warning isn't indicative of a problem in an Insta360 video.  It is because there is some sort of unrecognized trailer appended to the file that doesn't conform to the container format.  The video data itself is OK.  Truncated 'mdat' data as earlier in this thread is bad, and does indicate video data corruption.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).