• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
61

P: Still inconsistent capture date/time for photos and videos

LEGEND ,
Dec 09, 2014 Dec 09, 2014

Copy link to clipboard

Copied

Update 5/17/2018: Though LR 7.1 made improvements, LR 7.3.1 still has two closely related problems with a single underlying cause:

- With photos and videos missing metadata capture date/times (e.g. scans), there is still an inconsistency between the times shown under the thumbnails in grid view and in the Metadata panel and the hidden, internal times used for sorting in grid view.

- Changing IPTC Date Created in the Metadata panel, either by editing the field or using Metadata > Copy/Paste Metadata, similarly causes inconsistent values to be shown and sorting and searching to work inconsistently.  It also causes date metadata to be written back to the files that doesn't conform with the Metadata Working Group's standard.

The underlying cause is architectural: LR doesn't have a single internal catalog field representing "capture time".  Rather, it maintains capture time in several different fields, and the various parts of LR update those fields inconsistently.

See here for precise recipes to replicate these bugs:

https://feedback.photoshop.com/photoshop_family/topics/lightroom-still-inconsistent-capture-date-tim...

https://feedback.photoshop.com/photoshop_family/topics/lightroom-still-inconsistent-capture-date-tim...

See here for a workaround: 

https://feedback.photoshop.com/photoshop_family/topics/lightroom-still-inconsistent-capture-date-tim....  

-------------

LR 5.7 still shows inconsistent capture date/times for videos. For a test .avi on Windows 8.1, the date in grid view appears to be the file system's last-modified time, while Capture Date/Time is set to the time of import.This problem was declared fixed in LR 5.5, and it appears to have been fixed for images, but not videos:http://feedback.photoshop.com/photoshop_family/topics/inconsistent_dates_for_files_missing_date_time...I'm opening a new topic, since the previous one has been marked "Solved". Untitled2_inline-402b28f5-7fce-4485-bbc7-1eba2e9ee1ed-622028544.pngUntitled2_inline-402b28f5-7fce-4485-bbc7-1eba2e9ee1ed-622028544.png Untitled_inline-a0d82271-2553-4a54-8824-20de68939af3-906850541.pngUntitled_inline-a0d82271-2553-4a54-8824-20de68939af3-906850541.png

Bug Investigating
TOPICS
macOS , Windows

Views

2.7K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Dec 13, 2017 Dec 13, 2017
Hi all,

Just to reiterate what Sunil said in a comment above, this issue should be fixed in Lightroom Classic CC 7.1. Please let us know if you're still seeing this issue after updating.

Thanks,
Melissa

Votes

Translate

Translate
replies 168 Replies 168
168 Comments
Enthusiast ,
Feb 15, 2018 Feb 15, 2018

Copy link to clipboard

Copied

Hi Laura. I understand your frustration, but if you are looking for a work-around while you are waiting for a fix, i suggest you look at A Better Finder Rename. You can create droplets that use metadata to rename files, which you would apply before importing the video into Lightroom. (If you are on Windows, I suspect that there are umpteen utilities that offer the same options.) I use A Better Finder Rename all the time.

Votes

Translate

Translate

Report

Report
Explorer ,
Feb 15, 2018 Feb 15, 2018

Copy link to clipboard

Copied

Thanks, Alan!

Actually, I received a helpful reply on another forum last night which had an easier (IMO) and effective workaround: 

Workaround:
1) Import iphone .MOV videos as you normally would.  (I use "YYYY-MM-DD Hour.Minute.Second_iphone" and use it to check against the metadata). 

2)  Select all previously imported files and, under the metadata tab, Click "Edit Capture Time".  Select Type of Adjustment: Adjust to a specified date and time.  Don't change anything.  It will appear nothing needs changing as the original time already matches the corrected time.  Select Change All.  You'll notice there is now a 3rd metadata date/time entry: Date Time Original.  This matches the metadata list of .CR2 and .jpg file and is CRITICAL in order for ALL .MOV files to be renamed correctly*.   

4) NOW select all files and rename your using a date/time preset.  I used the same one that I use upon import and it works.  The filename matches the date and time the video was TAKEN/Created (not imported).  This works for a single file or multiple files.

**Note: I tried skipping step 3 to see if it was necessary, and it IS.  Without editing the capture time the files were renamed using the IMPORTED date/time. In fact, when I tried renaming an .MOV file from my 5d Mark iv, which had the correct date/time in the filename upon import, it was renamed using the IMPORTED date/time also.  This must be ANOTHER BUG on top of the bug that randomly adds 5-6 hours (for CST) to the Date Time Digitized.  The renaming feature must use the "Date Time" metadata (which is the IMPORTED date/time) if there is no "Date Time Original" metadata entry.  So stupid.  Therefore, step 3 is necessary in order to create the "Date Time Original" metadata entry, which eliminates the mis-naming in all video files.  

Hope that helps!  But also hope it gets fixed!!

Votes

Translate

Translate

Report

Report
LEGEND ,
Mar 20, 2018 Mar 20, 2018

Copy link to clipboard

Copied



Testing.

Votes

Translate

Translate

Report

Report
Participant ,
Apr 03, 2018 Apr 03, 2018

Copy link to clipboard

Copied

LR 7.3 on MacOS 10.13.4
Setting correct Capture Time universally across all fields on a paste of Metadata - Still not fixed
Using the 'Edit' workaround to correct the above - Not yet broken

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 22, 2018 Apr 22, 2018

Copy link to clipboard

Copied

The issue is not fixed in 7.1 - or at least if it was  it is back in 7.3....

Votes

Translate

Translate

Report

Report
Explorer ,
May 17, 2018 May 17, 2018

Copy link to clipboard

Copied



Not sure whether this is relevant, but a similar problem occurs with scanned tiff images interspersed with camera taken pictures. In other words, scan some pictures as tiff and import Imp light room, then import pictures .ARW files, and then scan some more pictures as tiff. The new tiff images cluster with the older tiff files, and will come before the ARW files. In this situation there is no THM file.

Votes

Translate

Translate

Report

Report
LEGEND ,
May 17, 2018 May 17, 2018

Copy link to clipboard

Copied

Unfortunately, there is still a bug with the capture times of imported files missing EXIF:DateTimeOriginal (e.g. scans) -- the sort order in grid view doesn't always match that implied by the capture time shown under the thumbnails and in the Metadata panel.   LR sets the capture time of each scan to the file's modified time, but the internal catalog field used for sorting gets set n hours earlier, where is the UTC offset of the computer's time zone. 

To reproduce:

1. Create a new catalog.

2. Download and unzip this folder: 
https://www.dropbox.com/s/gkytf55c88vrm8k/capturetimebug.2018.05.17.zip?dl=0

3. Run these ExifTool commands to set the file modification dates of "before.jpg" and "after.jpg":
exiftool -filemodifydate="2001:05:01 h:01:00" before.jpg
exiftool -filemodifydate="2001:05:01 h:03:00" after.jpg
where = 15 - the UTC offset of your computer's time zone. My computer is in PDT (UTC - 7), so I set h to 8:
exiftool -filemodifydate="2001:05:01 08:01:00" before.jpg
exiftool -filemodifydate="2001:05:01 08:03:00" after.jpg
4. Import "before.jpg", "test.jpg", and "after.jpg" using Add (not Move or Copy).

5. In Library, select All Photographs and View > Sort > Capture Time.

6. Observe that the sort order of the photos is inconsistent with the capture times shown under the thumbnails and in the Metadata panel:

RackMultipart20180518532911861-866e2a4d-830e-4572-9305-eb5d8dbae6ef-163710226.png

LR sets the visible capture time of each scan to the file's date-modified time expressed in the local time zone, but it sets the hidden internal field used for sorting to the date-modified time expressed in UTC.

The usual workaround fixes this: Select all the photos, do Metadata > Edit Capture Time, and click Change All.

Votes

Translate

Translate

Report

Report
LEGEND ,
May 17, 2018 May 17, 2018

Copy link to clipboard

Copied

The original merged topic contains details about Steven's symptoms (thanks!).  See the next post in this topic for a diagnosis.

Votes

Translate

Translate

Report

Report
LEGEND ,
May 17, 2018 May 17, 2018

Copy link to clipboard

Copied

Steven, you can delete the Dropbox folder -- the recipe in the next post quickly reproduces the symptoms you observed.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
May 18, 2018 May 18, 2018

Copy link to clipboard

Copied

Hi John,

When I downloaded the zip and checked the filemodifydate for before and after.jpg, I am getting the following 
before.jpg - 2018:05:17 22:15:08+05:30
after.jpg - 2018:05:17 22:15:08+05:30

Also for the test.jpg file is as follows:
2018:05:17 22:15:08+05:30
and I have value for DateTimeOriginal as follows
2001:05:01 15:02:00

DateTimeOriginal value is only present in test.jpg

Here is the screenshot from the Lightroom Classic:
RackMultipart20180518941851j3u-e58221d1-1262-4e77-bc85-6ff612c13bfc-1579496912.PNG

PS - I was testing on Win10

Thanks,
Smit

Smit | Lightroom Team

Votes

Translate

Translate

Report

Report
LEGEND ,
May 18, 2018 May 18, 2018

Copy link to clipboard

Copied

To observe the bug, you need to run the ExifTool commands in step 3 before importing the files.

Votes

Translate

Translate

Report

Report
LEGEND ,
May 18, 2018 May 18, 2018

Copy link to clipboard

Copied

Also, if you are located in a time zone whose offset is not a whole number of hours, it might be easiest to temporarily change your computer’s time zone to, say, UTC - 7:00.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
May 18, 2018 May 18, 2018

Copy link to clipboard

Copied

My Apologies. I misread your step.

Based on your suggestion, when I changed the TimeZone to UTC -7, I was able to reproduce the issue. I will update this to our bug.

Also, if I just use the date-time values you have shared, I am still able to reproduce this when reset my Laptop to IST - UTC +5:30

Thanks again for following up on this for such a long time!

Thanks,
Smit
Lightroom Classic CC Team

Smit | Lightroom Team

Votes

Translate

Translate

Report

Report
Adobe Employee ,
May 18, 2018 May 18, 2018

Copy link to clipboard

Copied

Steven,

I was able to reproduce your issue. We are looking into this.

Thanks,
Smit Keniya
Lightroom Classic CC Team

Smit | Lightroom Team

Votes

Translate

Translate

Report

Report
New Here ,
Jun 17, 2018 Jun 17, 2018

Copy link to clipboard

Copied

This error starting appearing for me for a few months. Shot stuff on 17 June 2018 and some got sorted into the not-yet-happened 18 June folder. Checked the camera and made sure my settings were right too.

Votes

Translate

Translate

Report

Report
LEGEND ,
Jun 17, 2018 Jun 17, 2018

Copy link to clipboard

Copied

Are you importing using a USB cable or by using a card reader?

Votes

Translate

Translate

Report

Report
New Here ,
Jun 18, 2018 Jun 18, 2018

Copy link to clipboard

Copied

I use a card reader to import my files.

Votes

Translate

Translate

Report

Report
LEGEND ,
Jun 18, 2018 Jun 18, 2018

Copy link to clipboard

Copied

OK, there's a separate bug with putting photos into the wrong folder that's triggered by importing with a cable.

Votes

Translate

Translate

Report

Report
Explorer ,
Oct 21, 2018 Oct 21, 2018

Copy link to clipboard

Copied

Using Lightroom 8 and the issue is not fixed. Videos taken on the 10/19 imported as they were taken 7 hours later, and imported as if taken the following day. Lightroom also locks up when importing the videos.

RackMultipart20181021243611wcs-74fc18cf-d862-454d-acda-5778fa1ff5e9-352337735.jpgRackMultipart201810211202952pz-6a7f29c8-8faf-4955-b809-ab913c292e16-950194004.pngRackMultipart2018102142554ovks-a3072001-304f-4ee6-acb1-540a3d40c0c2-698319370.jpg

Votes

Translate

Translate

Report

Report
LEGEND ,
Oct 21, 2018 Oct 21, 2018

Copy link to clipboard

Copied

"Lightroom also locks up when importing the videos."

You might post this as separate topic with more details -- Adobe won't see it buried in this thread.

Votes

Translate

Translate

Report

Report
LEGEND ,
Dec 06, 2018 Dec 06, 2018

Copy link to clipboard

Copied

I am running Lightroom Classic 8.0 on MacOS and noticed today that video files are still being wrongly renamed based on file Date/Time and not Creation Date/Time metadata, any idea how to fix it?

What is the exactly "field" that Lightroom uses as reference for renaming files?

Votes

Translate

Translate

Report

Report
Explorer ,
Dec 24, 2018 Dec 24, 2018

Copy link to clipboard

Copied

Hi


I’m having a similar problem here. After updating to the new version of LR classic Lightroom is incorrectly reading MTS video file capture times. The capture times for the same file in Adobe Photoshop, Adobe Bridge and Mac finder are all correct. Only in Lightroom is there a problem. It’s most annoying when I’m trying to filter files based on what year the photos and videos were shot. LR shows me files from 2015 when i’m trying to view files from 2017. The incorrect files all have the same incorrect capture time also. Very strange. I have about 50,000 so i’m Worried about files getting completely lost in the mix.The screenshots show the file info in Lightroom being incorrectly seen and then the file info in Photoshop being CORRECTLY seen. Any help would be greatly appreciated.RackMultipart2018122443528rxlx-ceac98ef-55bf-4c72-9650-c9d4bf13bf68-170563524.pngRackMultipart201812241046326cv-b3c11e4e-8156-4cab-a795-e39df2abdf5a-435562030.png

Votes

Translate

Translate

Report

Report
Explorer ,
Jan 31, 2019 Jan 31, 2019

Copy link to clipboard

Copied

Has this not been fixed yet? I tried creating a new catalog and now there are hundreds of mts files (aka Sony's hd video format) all incorrectly having the capture time as the date I created the catalog not the actual capture time. See the post above.

Votes

Translate

Translate

Report

Report
Community Beginner ,
May 10, 2019 May 10, 2019

Copy link to clipboard

Copied



When exporting files that have an adjusted capture date, the capture date is not reflected in the custom file name (where capture date is selected), but the unmodified date of the original scan is used instead.  This is a problem when trying to export a chronological set of files by file name (using capture time in export), and the unmodified scan date is being used to create the export file name.

Votes

Translate

Translate

Report

Report
Community Beginner ,
May 10, 2019 May 10, 2019

Copy link to clipboard

Copied



Thank you for your time Tom and John.  I finally figured out my problem.  I was updating using the capture time adjustment on the right side panel in the Library module.  Then I would highlight a bunch more images and sync the metadata (with only the capture time selected).  This changed the capture time in the panel on the right under the default metadata dropdown, but it did not change the EXIF capture date on the files.  I now use the Change Capture Date under the Metadata dropdown menu at the top on a Mac.  This changes the EXIF capture date and is reflected in the export name.  Thanks again for your time everyone.

Votes

Translate

Translate

Report

Report