![]() This can be almost *anything* and is defined by the sample descriptions in the track. The mdat atom is used to store RAW essence. I fear that the mdat video data may fall into this category. ![]() Many of the video format specifications are imprisoned by the ISO, and far too expensive for small, independent software developers like me. I should point out that this is a systemic problem with video formats. I haven't given up, but right now it isn't looking good for having this feature in the next release. This is frustrating because I can decode both ends (the high-level QuickTime container, and the low-level H264 compressed video stream which should contain the GPS), but I haven't yet managed to figure out how this is packed (along with the other streams) in the MOV mdat atom. For lack of appropriate documentation, I have also tried to reverse engineer the ffmpeg code, but haven't had much success with this either. ![]() ![]() The QuickTime file format specification is good for most metadata, but I can't find where it describes the structure of the mdat atom contents, which is where the streamed GPS will be found. But I have worked on this over the last two days from my office. I couldn't get much done on this over the holidays because most of the work so far has been in searching for a format specification for the contents of the MOV mdat atom, which is hard to do from home over dialup. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |