VAR=$(exiftool -s -s -s -quicktime:createdate "$i") I'll post the script here in case its useful to someone.įor i in `ls *.MP4` #change extension accordingly I am by no means very proficient at either tools, but this was the best way I came up with to batch change video metadata dates. quicktime:createdate is one of the few video tags that exiftool can write, so this enables the great batch capabilities of exiftool to be used with the power of ffmpeg. Regarding changing dates with ffmpeg I just wrote a simple bash script that extracts the -quicktime:createdate tag from video files, parses it into a date that can be used with ffmpeg, and then changes all the dates with ffmpeg. For now I may have to put up with some incorrect sorting in Digikam for video files. Then it should not display timezone shift, correct? My only thought is that I can change my system timezone to UTC 00:00:00, and then change the -FileModifyDate for all video files. (Interestingly enough Digikam reads the incorrect -FileModifyDate as correct, as it apparently doesn't incorporate timezone shift, but this doesn't help for the files that actually have the correct -FileModifyDate.) I do finally have correct DateTimeOriginal/CreateDate tags for all the video files now, however Digikam and other software read the -FileModifyDate as the capture date, and that is what is complicating things. As you said, pictures are easy, but videos on the other hand. However for all avi and mov, and most other mp4's it shows an incorrect -fileModifyTime, with just the -CreateDate-6:00.Īny recommendations? My goal is to have a unified DAM system through Digikam, but that is not looking very doable. When I change the -fileModifyTime on *some* mp4's, it shows the correct time with the timezone shift (ie -6). The more I dig the more discrepancies I am finding. Thanks, its good to know I can do that as well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |