General > Metadata

iOS 9 new [Keys] CreationDate tag

(1/5) > >>

wywh:
Hello,

I noticed that iOS (8.4)-9 or greater movies seem to have a new datetime tag:

[Keys] CreationDate: 2020:01:01 12:00:00+02:00

It can be inserted to old iOS movies and other movies with:

exiftool -m -P -overwrite_original_in_place -Keys:CreationDate="2020:01:01 12:00:00+02:00" movie.mov

(Final Cut Pro 10.4.8 m4v movies fail without the -m switch).

Is there an option to set the DST timezone according to the date for that tag in a similar way like "exiftool -api QuickTimeUTC=1" seems to do automatically?

It seems macOS 10.15 Catalina's Photos.app 5.0 readily grabs the datetime from that tag. On the other hand macOS 10.14 Mojave's Photos.app 4.0 behaves differently.

Does anyone outside Apple know which algorithm each Photos.app version uses when setting the datetime to the imported movies? Which datetime metadata does it use and in which order??

Would it be a good idea to insert that tag to all movies and modify all other datetime tags (QuickTime, XMP etc) the same in case some application besides Photos.app gets the datetime from some other field? Or would that only muddy current movie datetime mess even more?

regards,

- Matti

StarGeek:

--- Quote from: wywh on May 14, 2020, 01:40:20 PM ---I noticed that iOS (8.4)-9 or greater movies seem to have a new datetime tag:
--- End quote ---

The fact that it's being set may be new, but that tag has been around for quite a while.


--- Quote ---Does anyone outside Apple know which algorithm each Photos.app version uses when setting the datetime to the imported movies? Which datetime metadata does it use and in which order??
--- End quote ---

This is probably something that you'll have to figure out yourself.  I've tested some Windows stuff, but I don't use a Mac.


--- Quote ---Would it be a good idea to insert that tag to all movies and modify all other datetime tags (QuickTime, XMP etc) the same in case some application besides Photos.app gets the datetime from some other field? Or would that only muddy current movie datetime mess even more?
--- End quote ---

It's pretty much up to you depending upon what programs you use and what the intended purpose of your files is.  If the files are intended to be shared with people who might care about the metadata, for example, on some stock image/footage site, then more metadata would probably be better.  If you plan on using Adobe programs, then you would want to add the XMP tags.  But the more data you add the more you'll have to work to keep it in sync.

Myself, I don't do much video, though I do capture some live steams occasionally.  In those cases I make sure I set the Quicktime:CreateDate and that's about it. My DAM reads that and that's good enough for me.

Phil Harvey:
Hi Matti,


--- Quote from: wywh on May 14, 2020, 01:40:20 PM ---Is there an option to set the DST timezone according to the date for [CreationDate] in a similar way like "exiftool -api QuickTimeUTC=1" seems to do automatically?
--- End quote ---

No.  This tag is stored as text with time zone, so that time zone is what you get.


--- Quote ---It seems macOS 10.15 Catalina's Photos.app 5.0 readily grabs the datetime from that tag. On the other hand macOS 10.14 Mojave's Photos.app 4.0 behaves differently.
--- End quote ---

Not surprising.  Apple isn't known for their consistency.


--- Quote ---Does anyone outside Apple know which algorithm each Photos.app version uses when setting the datetime to the imported movies? Which datetime metadata does it use and in which order??
--- End quote ---

Not me for sure.


--- Quote ---Would it be a good idea to insert that tag to all movies and modify all other datetime tags (QuickTime, XMP etc) the same in case some application besides Photos.app gets the datetime from some other field? Or would that only muddy current movie datetime mess even more?
--- End quote ---

I can't answer that.

- Phil

wywh:
Filename YYYY-MMDD-hhmm-ss.* has been my golden standard for image and movie datetimes and I'd like all other metadata including file creation & modification datetimes to be the same. Images and movies should sort together everywhere regardless of DST or location. Images are OK but movie datetimes are giving me lots of headache and confusion.

I am trying to build a command that sets (H.264 m4v, mp4, mov) movie times so that all my applications including Photos.app 5.0 read them correctly. Photos.app seems to prioritize that "Keys > CreationDate" so also it must be modified. Standards should be used for future proofing.

My current plan to insert filenames to metadata is:

exiftool -m -P -overwrite_original_in_place -wm w -api QuickTimeUTC=1 "-AllDates<filename" "-Track*Date<filename" "-Media*Date<filename" movie.mov

Is there a better way to modify the QuickTime Tracks or does any application pay attention to their datetimes?

What option should be used to set the "Keys > CreationDate" with a timezone like +02:00? That tag needs a timezone because I noticed that Photos 5.0 datetime is scrambled and the year set to something like "177294" in mp4 and m4v if "Keys > CreationDate" or "UserData > DateTimeOriginal" is without timezone.

Some commands like "-AllDates<filename" create "UserData > DateTimeOriginal" without timezone. Is it best to use "-wm w" so no such unexpected tags are created? Or is it possible to force adding a timezone there?

BTW, why deleting "Keys > CreationDate" tag also deletes Composite > GPS* locations?

A related question: In Canon 6D movies some apps seem to stubbornly get some datetimes from either "IFD0 > ModifyDate" or "ExifIFD > DateTimeOriginal". I have unsuccessfully tried to modify them the same as other datetimes or wipe them out. Any advice for that?

How can I combine following two commands so that also Keys get the datetime from the filename with timezone and DST info?

exiftool -m -P -overwrite_original_in_place -wm w -api QuickTimeUTC=1 "-AllDates<filename" "-Track*Date<filename" "-Media*Date<filename" 2020-0101-1200-00_iphone4s_ios9.3.2.mov

exiftool -m -P -overwrite_original_in_place -Keys:CreationDate="2020:01:01 12:00:00+02:00" 2020-0101-1200-00_iphone4s_ios9.3.2.mov

iOS 9 or greater seem to have the Keys tag:

exiftool -a -G1 -s -time:all 2020-0101-1200-00_iphone4s_ios9.3.2.mov
[System]        FileModifyDate                  : 2020:01:01 12:00:00+02:00
[System]        FileAccessDate                  : 2020:05:16 17:00:27+03:00
[System]        FileInodeChangeDate             : 2020:05:16 20:49:41+03:00
[QuickTime]     CreateDate                      : 2020:01:01 10:00:00
[QuickTime]     ModifyDate                      : 2020:01:01 10:00:00
[Track1]        TrackCreateDate                 : 2020:01:01 10:00:00
[Track1]        TrackModifyDate                 : 2020:01:01 10:00:00
[Track1]        MediaCreateDate                 : 2020:01:01 10:00:00
[Track1]        MediaModifyDate                 : 2020:01:01 10:00:00
[Track2]        TrackCreateDate                 : 2020:01:01 10:00:00
[Track2]        TrackModifyDate                 : 2020:01:01 10:00:00
[Track2]        MediaCreateDate                 : 2020:01:01 10:00:00
[Track2]        MediaModifyDate                 : 2020:01:01 10:00:00
[Track3]        TrackCreateDate                 : 2020:01:01 10:00:00
[Track3]        TrackModifyDate                 : 2020:01:01 10:00:00
[Track3]        MediaCreateDate                 : 2020:01:01 10:00:00
[Track3]        MediaModifyDate                 : 2020:01:01 10:00:00
[Track4]        TrackCreateDate                 : 2020:01:01 10:00:00
[Track4]        TrackModifyDate                 : 2020:01:01 10:00:00
[Track4]        MediaCreateDate                 : 2020:01:01 10:00:00
[Track4]        MediaModifyDate                 : 2020:01:01 10:00:00
[Keys]          CreationDate                    : 2020:01:01 12:00:00+02:00

Those stubborn Canon "IFD0 > ModifyDate" or "ExifIFD > DateTimeOriginal" tags:

exiftool -a -G1 -s -time:all 2020-0101-1200-00_canon6d.mov
[System]        FileModifyDate                  : 2020:01:01 12:00:00+02:00
[System]        FileAccessDate                  : 2020:05:16 17:00:32+03:00
[System]        FileInodeChangeDate             : 2020:05:16 20:55:40+03:00
[QuickTime]     CreateDate                      : 2020:01:01 10:00:00
[QuickTime]     ModifyDate                      : 2020:01:01 10:00:00
[Track1]        TrackCreateDate                 : 2020:01:01 10:00:00
[Track1]        TrackModifyDate                 : 2020:01:01 10:00:00
[Track1]        MediaCreateDate                 : 2020:01:01 10:00:00
[Track1]        MediaModifyDate                 : 2020:01:01 10:00:00
[Track2]        TrackCreateDate                 : 2020:01:01 10:00:00
[Track2]        TrackModifyDate                 : 2020:01:01 10:00:00
[Track2]        MediaCreateDate                 : 2020:01:01 10:00:00
[Track2]        MediaModifyDate                 : 2020:01:01 10:00:00
[Track3]        TrackCreateDate                 : 2020:01:01 10:00:00
[Track3]        TrackModifyDate                 : 2020:01:01 10:00:00
[Track3]        MediaCreateDate                 : 2020:01:01 10:00:00
[Track3]        MediaModifyDate                 : 2020:01:01 10:00:00
[Keys]          LocationDate                    : 2015:08:08 13:03:06+03:00
[IFD0]          ModifyDate                      : 2015:08:08 13:02:57
[ExifIFD]       DateTimeOriginal                : 2015:08:08 13:02:57
[ExifIFD]       CreateDate                      : 2015:08:08 13:02:57
[Canon]         TimeZone                        : +03:00
[Canon]         TimeZoneCity                    : Cairo
[Canon]         DaylightSavings                 : On
[ExifIFD]       SubSecTime                      : 55
[ExifIFD]       SubSecTimeOriginal              : 55
[ExifIFD]       SubSecTimeDigitized             : 55
[Composite]     SubSecCreateDate                : 2015:08:08 13:02:57.55
[Composite]     SubSecDateTimeOriginal          : 2015:08:08 13:02:57.55
[Composite]     SubSecModifyDate                : 2015:08:08 13:02:57.55

- Matti

StarGeek:

--- Quote from: wywh on May 16, 2020, 02:51:07 PM ---That tag needs a timezone because I noticed that Photos 5.0 datetime is scrambled and the year set to something like "177294" in mp4 and m4v if "Keys > CreationDate" or "UserData > DateTimeOriginal" is without timezone.
--- End quote ---

This is actually good news.  We've had a few previous cases where the Quicktime:DateTimeOriginal tag was causing problems with Photos.  If adding the time zone fixes the problem, it will help if it comes up again.


--- Quote ---Some commands like "-AllDates<filename" create "UserData > DateTimeOriginal" without timezone. Is it best to use "-wm w" so no such unexpected tags are created? Or is it possible to force adding a timezone there?
--- End quote ---

You could tack the time zone on the end e.g. '-AllDates<$Filename -05:00', but that may too much manual work.  Either the -wm option as you suggest or just directly write the CreateDate/ModifyDate instead of AllDates.


--- Quote ---BTW, why deleting "Keys > CreationDate" tag also deletes Composite > GPS* locations?
--- End quote ---

More info needed, like the exact command and tags.  Because my quick test here didn't change the GPS data.


--- Quote ---A related question: In Canon 6D movies some apps seem to stubbornly get some datetimes from either "IFD0 > ModifyDate" or "ExifIFD > DateTimeOriginal". I have unsuccessfully tried to modify them the same as other datetimes or wipe them out. Any advice for that?
--- End quote ---

An EXIF block in a video file is non-standard, not that it doesn't stop camera companies from forcing it in.  Exiftool can't change this data.  I'm not sure if there is anything that can. 

Navigation

[0] Message Index

[#] Next page

Go to full version