![]() ![]() I also don't see how this would relate to the Apple QuickTime maker notes. ![]() This is an undocumented maker note and nothing I would base an implementation on. Is there any spec from Apple that requires the MP4/MOV QuickTime timestamps to be in UTC? Link? If the timestamp would be "2018:02:03 09:57:04 Z", things would be clear and well-defined. IMatch assumes local time, Windows Explorer may be hard-coded to add the current time-zone? Not sure. When IMatch looks at a create time QuickTime timestamp of "2018:02:03 09:57:04", how can it tell that this was recorded in UTC and not in local time? I checked two Z6 samples in my test library. If neither is specified, the time must/may be in local time?Īpple uses "T17:56Z" for a date of February 24, 2012, time of 17:56, UTC. ![]() This date format may contain a time-zone identifier like +01:00 or a Z for UTC. This is true for the QuickTime Create/Modify timestamps and also for the separate TRrack and Media Created/Modified timestamps. I have checked the QuickTime spec and I could not find anything about the dates being in UTC always.Īpple just refers to ISO 8601, which is also the date format used by ExifTool and IMatch. ![]()
0 Comments
Leave a Reply. |