Skip to main content
Participating Frequently
February 3, 2014

P: iPhone video Capture Time is shifted upon Import

  • February 3, 2014
  • 110 replies
  • 2392 views

Beginning with at least the iPhone 4S, and continuing with the 5 and 5s, I see that videos shot with those devices show a capture time that seems to relate to GMT, when it was actually shot at GMT -5.

The videos show a correct creation time in Finder prior to import, but this odd shift occurs upon import. I know that the capture time can be edited in Lightroom, but I'd rather see the correct time on import.

This happens in Lightroom 5.3, but also occurred all the way back into 4.

This topic has been closed for replies.

110 replies

Smit K
Participating Frequently
April 13, 2017
Hi Andrew,

Please find below the date and time shown in Metadata Panel for the video you shared in Lightroom 6.10/CC 2015.10



I do not see any issue. Could you confirm the same?

Thanks,
Smit
Smit | Lightroom Team
Participating Frequently
April 12, 2017
Done.
Smit K
Participating Frequently
April 12, 2017
Hi Andrew,

Could you share a sample video and screenshot of your metadata panel for the same video to keniya@adobe.com?

Thanks,
Smit Keniya
Adobe Lightroom Team
Smit | Lightroom Team
Participating Frequently
April 12, 2017
Iphone7 here and the fix still doesn't seem to be working.

I've got a video that shows this in it's metadat:
Create Date 2017:03:26 23:50:09
Creation Date 2017:03:26 16:50:09-07:00

and after updating lightroom to the latest version, delete the file from the library and reimporting, the time in lightroom for it is still 3/26/2017 11:50:09 PM when it was taking at 4:50 in the afternoon PDT (UTC-7).
jamescodeglia
Participating Frequently
April 11, 2017
Seems to be working for me with my iPhone 6s! Thanks, Rikk!
Rikk Flohr_Photography
Community Manager
April 11, 2017
This issue should be fixed in Lightroom CC2015.10/6.10.  Please update your system and let us know if you have any additional issues. 

Additional information on this update can be found here: http://blogs.adobe.com/lightroomjournal/2017/04/lightroom-cc-2015-10-now-available.html
Rikk Flohr: Adobe Photography Org
Known Participant
March 13, 2017
I find it surprising that this "fix" wasn't tested with actual video from an iPhone. I'm not aware of any iPhone owner who has not run into this problem in LRm, which begs the question do none of the developers at Adobe have an iPhone which they can take their own video and try it out? I strongly applaud Adobe for now finally trying to address this issue, but seriously, how could a release that "fixes" fthe problem be released and not tried on sample videos?
tred56utAuthor
Participating Frequently
March 13, 2017
Thanks for being the voice of reason, Andrew.  

If some very fair criticism causes them to "change their mind and ruin it for the rest of us," then things are far worse than they even seem.  
Participating Frequently
March 13, 2017
Peter, calm down.  They are on it and fixing it.  Please don't make them change their mind and ruin it for the rest of us.

Simon and Tom, I appreciate your dedication to making your product better, keep up the good work!
tred56utAuthor
Participating Frequently
March 13, 2017
Simon,

Thanks for the update.  What's the timeframe for the actual fix?

Are you blaming Adobe's delay of over three years (read up on this thread to my original post) on legal issues?  Seriously?  If that's what you mean, I call BS.  But maybe you mean something else.  

Do you mean that the reason this so-called fix is actually no fix at all is due to legal considerations?  I don't think so.  

In any event, here's some advice:  The next time you are asked, or decide, to acknowledge that your employer has screwed up royally, leave it at that.  Don't go on to vaguely blame the need for "legal clearance."  That just is not the reason for this comically bad effort on Adobe's part.  

Finally, when acknowledging that your so-called fix isn't a fix at all, I wouldn't recommend finishing the same post by saying, "The technical detail is usually the easy part."  It clearly is not.