Lightroom Defect: iPhone 7 video UTC timezone fix from 2015.10/6.10 randomly and inconsistently applied to imported files

  • 1
  • Problem
  • Updated 3 years ago
  • (Edited)

This conversation has been merged. Please reference the main conversation: Lightroom: iPhone video Capture Time is shifted upon Import

When .MOV files are imported into LR 6.10.1 from my iPhone 7 Plus, LR randomly applies the UTC timezone fix described in the release notes for 2015.10/6.10.  Some of the videos show the correct time rather than UTC, while others still show in UTC time.  There does not appear to be any obvious pattern, since each time the same set of videos are imported, the fix is randomly applied to some files but not others.  This is most perplexing.  At least before the "fix" was introduced, I could bulk shift the datetime to fix the defect, but now that isn't even an option, so now the situation is much worse than before.  As least before it was predictable behaviour. 

I have figured out another workaround, which work perfectly so far after repeatedly importing.  It is however, slightly “destructive” which is unfortunate, and I am working on some alternatives.

The workaround fix is to simply run the following ExifTool command on all .MOV files that came out of myiPhone, before importing into LR:

exiftool -overwrite_original "-quicktime:createdate<quicktime:creationdate" "-quicktime:modifydate<quicktime:creationdate” FILE/DIR

I really don’t know what on earth is going on in the LR code, but if I could fix the issue so quickly and simply, it’s quite beyond me why this is so hard for LR to resolve.  Just use the quicktime:creationdate tag in .MOV files from iPhones.  Maybe there is more to it, but the randomness of the defect is very worrying, and this works perfectly so far.

I notice that I am not the only one experiencing this defect - here is another:

I am using LR 6.10.1 on Mac Sierra 10.12.5 and my iPhone is running 10.3.2.
Photo of Mark L

Mark L

  • 36 Posts
  • 2 Reply Likes
  • perplexed

Posted 3 years ago

  • 1

There are no replies.

This conversation is no longer open for comments or replies.