![]() ![]() Unless I'm missing something, MediaInfo consumes more or less the entire file before giving an answer. When finished, I have feed a total of 7827313 bytes into MediaInfo. Then, it seeks to offset 36, where the mdat atom data begins. I don't think its a problem with ffmpeg because I tried converting it directly (although it was with another version of ffmpeg probably) and it converted just fine. Moov atom or movie atom is a part of file data that contains information about duration, timescale, display characteristics, and sub atoms of each track in a video. After reading the first buffer, MediaInfo seeks to offset 7818735, where the moov atom is. ![]() Format profile : settings : CABAC / 1 Ref Frames ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |