Lightroom: iPhone video Capture Time is shifted upon Import

  • 25
  • Problem
  • Updated 5 days ago
  • Solved
  • (Edited)
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.
Photo of Peter Preston

Peter Preston

  • 10 Posts
  • 3 Reply Likes
  • frustrated

Posted 4 years ago

  • 25
Photo of jpolastre

jpolastre

  • 4 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled Wrong time for iPhone videos in Lightroom.

When importing a video (MOV) from an iPhone 6S to Lightroom 2015 6.10, the date and time imported is incorrect.

In Lightroom, an example video shows 3/4/2009 in LR but correctly 12/24/2015 in Finder.

I'm seeing this across all recently imported videos.
Photo of Smit Keniya

Smit Keniya, Employee

  • 121 Posts
  • 64 Reply Likes
Hi @jpolastre,

Could you share a sample video? You can send it to keniya@adobe.com

Thanks,
Smit Keniya
Photo of jpolastre

jpolastre

  • 4 Posts
  • 0 Reply Likes
Example video:
https://drive.google.com/file/d/0B0RbSsWZLvUhQ3oxQVpwLVBSNlU/view?usp=sharing

I think this is happening when video is shot in other iOS apps and saved to the camera roll (eg, Hyperloop, Snapchat, etc)

Photo of Smit Keniya

Smit Keniya, Employee

  • 121 Posts
  • 64 Reply Likes
Hi,

Sorry for delay in response.

I am able to reproduce this issue with Videos captured by other iOS Apps.

But, with the video you have shared, I am not able to see the issue. 

Thanks,
Smit Keniya
Photo of herrclich

herrclich

  • 11 Posts
  • 2 Reply Likes
This reply was created from a merged topic originally titled Wrong date on import photos from iPhone.

Import from iPhone takes date from modified file and not from taken photo.
That seems to be on my system, because on an import I saw already imported photos from some time ago. I do not know why this happens, but maybe this is caused by the face recognition or some iPhone internal routines. nevertheless I checked one specific photo and windows 10 reports the correct capture date and the modified date that is shown as proposed folder in LR 6.10.

Example:
Lightroom shows the date 26.04.2017 on hovering the mouse over the picture during import.
Accessing the iPhone while Windows 10 file Explorer shows 29.03.2017 as 'Date created' and 26.04.2017 as 'Date modified'.
After import into Lightroom the file resides in the subfolder 2017-04-26 and shows the Capture date of 2017-03-29.
This happens only when the import is done directly from the iPhone. Copied from the phone and imported afterward from disk does not have this issue.

If that is the case it would mean that I get really problems with a new phone when it modifies the file (while a new face recognition starts). 

During the last year I use the phone more and more for photos and in fact it destroys my workflow. I get also duplicated files that Lightroom does not recognize. :-(
Photo of John R. Ellis

John R. Ellis, Champion

  • 3123 Posts
  • 738 Reply Likes
I think this is a different problem from the other reports in this topic.  Here, the capture date appears correct but on import via USB cable the photo is getting moved into the wrong dated folder (whose date differs by over a month).    When the photo is imported directly from the local disk, the issue doesn't occur.

I'm guessing this has the same cause as this long-standing bug: https://feedback.photoshop.com/photoshop_family/topics/lightroom_import_wrong_folder_names_organizin... . In that bug report, I hypothesized:

"Here's my hypothesis of the bug: When LR reads directly from a card, it is going through the FAT filesystem and getting the capture date from photo's metadata. When it reads via a USB cable, I think it is using the Picture Transport Protocol (or an extension of that).  In the protocol, the capture date is transmitted separately from the photo.  Somewhere in that code path, either in LR or the OS libraries, lies confusion about time zones."

Similarly, my educated guess here is that PTP code (used only when importing via USB cable) in the iPhone, Windows, or LR has gotten confused and is reporting the wrong date for the import folder selection.
Photo of herrclich

herrclich

  • 11 Posts
  • 2 Reply Likes
Hi John,
somebody joint topics that are not belonging to each other anymore. My problem is still existent and I do not import movies. Thank you for checking the issue. 

Even if this might be an Apple issue I really get angry now, because the Windows import is sorting the photos correctly on import. Nevertheless the dates are wrong and Lightroom does not provide a function to automatically relocate the photos by their date scheme.
My proposal is still that the issue has nothing to do with time zones, but with modified dates.

When you(Adobe) know you have troubles with your meta data access, why do you not copy the picture to an intermediate location and recheck the file for meta data. Should be no problem, because this process seems to be still not parallelized. 
And if you ask why I am angry - the mismatch of dates is visible in your own SQLite database :-((.
(Edited)
Photo of Smit Keniya

Smit Keniya, Employee

  • 122 Posts
  • 64 Reply Likes
Official Response
Hi,

Capture Time for Videos captured on Apple's iOS Camera app now shows correct value in Lightroom (CC 2015.10 / 6.10 onwards).

Note:
  • Videos captured from other iOS apps like Instagram, Facebook, Hyperloop, Snapchat, etc are shot with MPEG4 Standard. 
  • The MPEG4 standard only provides specification of capture time in GMT. That is the reason why each vendor decides (or not) to put time zone info into proprietary location in a proprietary format. 
  • Videos by these apps do not have Time Zone info.
Thus, for such videos, Lightroom will only show Capture Time in GMT.

Thanks,
Smit Keniya
Photo of Mark L

Mark L

  • 36 Posts
  • 2 Reply Likes
This reply was created from a merged topic originally titled Lightroom Defect: iPhone 7 video UTC timezone fix from 2015.10/6.10 randomly and ....

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:
https://feedback.photoshop.com/photoshop_family/topics/iphone_video_capture_time_is_shifted_upon_imp...


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

Smit Keniya, Employee

  • 117 Posts
  • 62 Reply Likes
Hi Mark,

Could you share a sample video where you are seeing the problem consistently to keniya@adobe.com? This will help us investigate more.

Thanks,
Smit Keniya
Adobe Lightroom Team
(Edited)
Photo of Mark L

Mark L

  • 36 Posts
  • 2 Reply Likes
Hi Smit, thanks for your reply - the problem is that this is random, so sending you an example single file is not going to be too helpful. Every time I import the exact same set of files, a random different set of files are affected.  How else would you like to drill down into this?
Thanks,
Mark.
(Edited)
Photo of Smit Keniya

Smit Keniya, Employee

  • 117 Posts
  • 62 Reply Likes
Hi Mark,

I am trying to reproduce this on our end.

Just to confirm, you were facing the issue with videos from iOS Camera app or did you use other apps for capturing the video?

Also,  could share the set of the videos on which you are facing this continuously with some of the random files with me?

Thanks,
Smit Keniya
Photo of Mark L

Mark L

  • 36 Posts
  • 2 Reply Likes
Hi Smit, the set I had been using was about 50GB. Perhaps we could arrange a screen share session at I can show you what is happening? Otherwise I will try do repeated imports and see if there are any files that consistently have issues.

And yes, all from the iPhone.

Thanks,
Mark.
(Edited)
Photo of Smit Keniya

Smit Keniya, Employee

  • 117 Posts
  • 62 Reply Likes
Hi Mark,

Could you share the details of the videos?
  • Shot in - 720P, 1080P or 4K?
  • Were any of them slow-mo or time-lapse?
This will help in creating a set on our end which is like your set

Thanks,
Smit Keniya
Photo of Mark L

Mark L

  • 36 Posts
  • 2 Reply Likes
Hi Smit, 
They were all in 4K, and I think there was one or two slo-mo files - I'll double check and confirm.
What I'll try and do is repeatedly import the set, and generate a report each time which I can share with you, and I'll include as many data points in the report as possible.

Thanks,
Mark.
Photo of andrewrbell

andrewrbell

  • 13 Posts
  • 3 Reply Likes
Just FYI that my experience above is identical to marks.  The importing is hit or miss, sometimes it gets the timezone right, sometimes it's wrong, and If I reimport the same files, the ones it gets it right/wrong on changes.
Photo of Smit Keniya

Smit Keniya, Employee

  • 117 Posts
  • 62 Reply Likes
Thanks, Mark! I will try to reproduce on our end.

Thanks,
Smit Keniya
Photo of andrewrbell

andrewrbell

  • 13 Posts
  • 3 Reply Likes
I did my 3 month unloading photos/vidoes from various devices today and ran into this a bunch of times.  The problem is that the same video imported over and over again will sometimes come in in GMT time and sometimes the correct local time.  Unfortunately us sending videos in isn't going to help resolve this.  I took a video of my lightroom experience of a video from 2 this afternoon which showed 9 in lightroom after initial import. I removed that single video from the catalog and then resyncd the folder and on the second sync, it got the correct local time of 2pm.  I sent the details to your e-mail address Smit.
Photo of Smit Keniya

Smit Keniya, Employee

  • 117 Posts
  • 62 Reply Likes
Thanks, Andrew!

I am trying to reproduce the issue on our end.

Thanks,
Smit Keniya
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 2920 Posts
  • 414 Reply Likes
Official Response
Lightroom CC2015.12/6.12 was released today and should address this issue.  Please update your Lightroom to the latest version and let us know if you continue to see the issue. Thank you for your patience.

http://blogs.adobe.com/lightroomjournal/2017/07/lightroom-cc-2015-12-now-available.html
Photo of Ethan Isenberg

Ethan Isenberg

  • 23 Posts
  • 0 Reply Likes
Thanks, Rikk.  Hope it finally works. 

My desktop app is not showing the latest update, nor does this page.  Is there another way to get it, or should I just wait and be patient?
(Edited)
Photo of John R. Ellis

John R. Ellis, Champion

  • 3123 Posts
  • 738 Reply Likes
You can download updates directly from here: https://helpx.adobe.com/lightroom/kb/lightroom-downloads.html
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 2920 Posts
  • 414 Reply Likes
It can take a few hours for the updates to propagate through the server. Your CC app refreshes every 24 hours. If you can't/won't wait, you can get it from the link John provided. 
Photo of Ethan Isenberg

Ethan Isenberg

  • 23 Posts
  • 0 Reply Likes
The update's not at the link John posted, either.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3123 Posts
  • 738 Reply Likes
You need to click on the blue arrow to see the actual download links (see the screenshot):
Photo of Ethan Isenberg

Ethan Isenberg

  • 23 Posts
  • 0 Reply Likes
That's right.  And when you do, what do you see?
Photo of John R. Ellis

John R. Ellis, Champion

  • 3123 Posts
  • 738 Reply Likes
Interesting, 6.12 has been removed from that page since I downloaded it from there late last night.  But these links work:

Windows: http://swupdl.adobe.com/updates/oobe/aam20/win/AdobeLightroom-6.0/6.12/setup.zip

Mac: http://swupdl.adobe.com/updates/oobe/aam20/mac/AdobeLightroom-6.0/6.12/setup.dmg

Photo of Ethan Isenberg

Ethan Isenberg

  • 23 Posts
  • 0 Reply Likes
Thanks.  How do I go about installing from that file?  The AdobePatchInstaller didn't work for me.  Do I just drag the Lightroom application from within the unzipped Assets1 folder to the Application folder?
Photo of John R. Ellis

John R. Ellis, Champion

  • 3123 Posts
  • 738 Reply Likes
On Mac, I just run the AdobePatchInstaller.  What happens when you double-click it?
Photo of Ethan Isenberg

Ethan Isenberg

  • 23 Posts
  • 0 Reply Likes
It says it's not for me.  Sounds like something I say to my 7-year old.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3123 Posts
  • 738 Reply Likes
Do Help > System Info -- what is the exact version shown?
Photo of Ethan Isenberg

Ethan Isenberg

  • 23 Posts
  • 0 Reply Likes
CC 2015.10 [ 1111918 ]
Photo of John R. Ellis

John R. Ellis, Champion

  • 3123 Posts
  • 738 Reply Likes
If the error is, "This patch is not applicable for you", see this thread for possible solutions: https://forums.adobe.com/message/9689982 .  In general, the update process isn't too robust, unfortunately: https://feedback.photoshop.com/photoshop_family/topics/what-is-wrong-with-the-lightroom-update-proce...
Photo of Ethan Isenberg

Ethan Isenberg

  • 23 Posts
  • 0 Reply Likes
I uninstalled LR and then reinstalled from Creative Cloud.  It's now up-to-date.
Photo of Ethan Isenberg

Ethan Isenberg

  • 23 Posts
  • 0 Reply Likes
I uninstalled LR and then reinstalled from Creative Cloud.  It's now up-to-date.
Photo of Mark L

Mark L

  • 36 Posts
  • 2 Reply Likes
Thanks Rikk - I will try this asap and let you know how it goes.
Photo of Ethan Isenberg

Ethan Isenberg

  • 23 Posts
  • 0 Reply Likes
I tried importing just a small sample of videos, and I'm glad to report that so far, all of them have correct time information!

The question is, what to do about photos that are already in the library? 

John Ellis originally suggested reading the metadata from file, but then recognized that it isn't allowed with video. 

I realized that any videos that don't have any added metadata or keywords can simply be deleted from the library (but not the disk), and then you can synchronize their containing folder, automatically adding them back in.  Their dates should now be correct. 

If a photo does have metadata, then you can first apply the "Copy Metadata" command from the Metadata menu (not the context menu), delete, then synchronize and paste the metadata back in.  (Not sure if this would work for multiple photos at a time, esp if the metadata varies). 

However, this doesn't do anything for keywords.  Any way to copy/paste keywords?

Better yet, any way to reload a photo in one step, where the keywords/metadata remain the same, but the captured date is refreshed?
Photo of John R. Ellis

John R. Ellis, Champion

  • 3113 Posts
  • 734 Reply Likes
"Any way to copy/paste keywords?"

The Metadata > Copy Metadata command will also copy keywords (you have to scroll the list all the way to the end to select Keywords).  So your method of doing Copy Metadata, removing the video from the catalog and reimporting it, then doing Paste Metadata, should preserve all the metadata changes you've made, including keywords.

Another method would be to select all the videos with wrong capture dates and then use the Lr/Transporter plugin to save their metadata as a text file.  Then remove all the videos and reimport them. Then the plugin to read their metadata from the text file.

I recommend making a catalog backup before you use either method!
Photo of Ethan Isenberg

Ethan Isenberg

  • 23 Posts
  • 0 Reply Likes
Ah, I realized that when I copied metadata before, the option to copy keywords was not checked by default.  Thanks for the tip on the Transporter plugin.
Photo of Laura Kent

Laura Kent

  • 39 Posts
  • 3 Reply Likes
I have updated to Lightroom Classic CC 7.2, and while the metadata is now correct, when I rename my iphone 6s Plus video files upon import using date and time (YYY-MM-DD hour.minute.second), the time is always exactly 6 hours off the capture time (5 hours during daylight savings).  The Date Time Digitized metadata shows the correct capture time and the Date Time metadata shows when it was imported (completely irrelevant info, IMO).  Any videos taken after 6 pm also have incorrect dates because of the incorrect time.

For those who said the issue has been fixed, did you rename using the time?  Renaming using only the date is still misleading/dangerous because while the metadata appears correct, the date in the filename may be a day ahead.  

Example (iphone 6s plus .MOV video file):
FILENAME: 2018-01-30 02.15.09 (6 hours off, resulting in 1 day off)
Metadata:
Date Time Digitized: 1/29/18 8:15:09 PM (actual capture date/time)
Date Time: 2/15/18 12:52:05 AM (actual imported date)

I've been using workarounds for years and they are awful.  My latest workaround is airdropping my camera roll to a watched folder on my computer and auto importing into lightroom that way.  Renaming using date/time is correct for images and videos.  However Lightroom re-imports files if I accidentally airdrop them twice, and it's really hard to keep up with which files have been auto imported and which haven't.  As a result, I'm not backing up my photos the way I should, and while I know they are only "iphone pictures" and not my professional camera pics, but in all honesty they hold the most precious of my everyday memories and deserve to be imported just like any other camera.  I don't understand why it's hard to get the date correct.  Why 6 hours off?  And why only for iphone videos?  My 5d Mark iv .MOV files are named correctly, with correct metadata.  

I'm in Dallas, TX, CST, if that means anything.
(Edited)
Photo of Mark L

Mark L

  • 36 Posts
  • 2 Reply Likes
Hi Laura,

I also rename all my files with the local date and time that they were taken.  For me, there is a super-crucial step I always perform immediately after importing ANYTHING into LR, which I have found to be the only way to ensure consistency, after a LOT of experimenting.  It seems counter-intuitive but here are the steps:

1. Import new files
2. Select all files that have just been imported, using the "Previous Import" built-in collection
3. Click Metadata menu
4. Click Edit Capture Time...
5. Leave the option to adjust to a specified date and time selected
6. Click Change All
7. Rename all using the following format: "Date (YYYY)-Date (MM)-Date (DD)_Hour-Minute-Second"

Now that you have posted this, I am going to re-check all my files to see if I can find any mismatches as you have described, but perhaps give my steps a try and let me know if it worked for you.

Regards,
Mark.
Photo of Laura Kent

Laura Kent

  • 39 Posts
  • 3 Reply Likes
Thanks, Mark! That works! It is a counter intuitive workaround because nothing actually changes in the metadata update (the date and time were already correct and the “corrected” time is the same as the original time). However, when I renamed using the same preset I use on import it renames correctly... It didn’t use to rename or correct metadata correctly when the actual metadata was off before 7.1, so progress has been made!

Your workaround got me thinking that maybe the renaming is all I need to do (AFTER videos have been imported in LR), and sure enough, it works. No metadata update needed. Filename date and time correctly matches the Date Time Digitized metadata (capture time). It even correctly renamed files that were off a day due to the incorrect time.

It’s really dumb that it has to be done twice!! But that seems to be the theme with the latest updates... like having to update snapshots with the same settings in order to correctly reflect hidden tone curves after selecting another snapshot, etc. But THANK YOU!!! I feel confident that I can import videos from my iPhone and have everything be correct eventually.

                     -----------------------------------------------------------------------------------
Update:  Just kidding!  I must have been looking at the "Date Time" metadata instead of the "Date Time Digitized" metadata because I can not replicate the results (crossed out) above.

 Mark, you are completely right.  It IS vital to edit the capture time, as you stated.  Without doing that, renaming ALL my video files (iphone .MOV files AND 5d Mark ii .MOV files) results in a new filename with the IMPORTED date/time and NOT the capture date/time.  Again, this affects ALL my videos, including my 5d Mark iv .MOV files that were renamed with date/time correctly on import. This happens if I rename one file at a time or if I select multiple files and rename.  Renaming other files (.CR2, jpgs) by date/time under the library module does not result in a filename with the IMPORTED date like my .MOV files have.  

More Observations:
*I noticed that after editing the capture time there's a 3rd metadata date/time entry that wasn't there upon import: Date Time Original.  This matches the date/time metadata list of .CR2 and .jpg file and seems to be CRITICAL in order for ALL .MOV files to be renamed correctly.   Without the "Date Time Original" metadata entry, renaming files by date/time uses the "Date Time" metadata (Imported date/time).  After editing the capture time (even though nothing appears to change), renaming files by date/time will use that new "Date Time Original" metadata instead.

I hope this gets fixed.  But in the meantime, I will use Mark's workaround.
(Edited)
Photo of Mark L

Mark L

  • 36 Posts
  • 2 Reply Likes
Glad to hear it worked for you Laura :)
Your notes are completely consistent with my findings - the DateTimeOriginal attribute appears to be the critical piece of data, but it was often not present, or not accurately populated.  Using the Edit Capture Time feature actually generated it when it was not present, and set it correctly when it was present.  I believe the parameters used in the Renaming function actually look for the DateTimeOriginal first, and only if that is not present, goes off looking for other datetime attributes.  As far as datetime metadata goes, I only ever pay attention to the DateTimeOriginal one; I ignore all the others.
One extra note - I did find that it was critical to perform those steps immediately after importing the files; I found that if I did not, I would not get reliable results.
Best,
Mark.