Lightroom: Import: Wrong folder names organizing by date when using camera USB

  • 22
  • Problem
  • Updated 1 week ago
  • Acknowledged
  • (Edited)
When importing from a camera connected to USB (at least for a Canon EOS 40D Firmware 1.1.1 in my case), lightroom generates wrong folder names when organizing folders by date, at least for the "2011/2011-07-22" format (I guess it's the same for the other formats). 

I use Lightroom 3.4.1 on Windows XP 32 Bit SP 3 and my time zone is CET+DST (Paris, Berlin). I shot six photos an hour apart around midnight CET+DST from 21:30 on Thursday to 02:30 on friday (I changed the camera's time for that) and got the following folder/file structure using a USB connection to the camera: 

2011\2011-07-21\20110721-213022-IMG_0314.CR2 
2011\2011-07-22\20110721-223033-IMG_0315.CR2 <<< wrong folder 
2011\2011-07-22\20110721-233041-IMG_0316.CR2 <<< wrong folder 
2011\2011-07-22\20110722-003049-IMG_0317.CR2 
2011\2011-07-22\20110722-013055-IMG_0318.CR2 
2011\2011-07-22\20110722-023102-IMG_0319.CR2 

Clearly, the two marked files are in the wrong folder. Note that the file naming itself (date and time) is absolutely correct! 

When I import the same six photos using a card reader from the CF card, I get the correct structure: 

2011\2011-07-21\20110721-213022-IMG_0314.CR2 
2011\2011-07-21\20110721-223033-IMG_0315.CR2 <<< now correct folder 
2011\2011-07-21\20110721-233041-IMG_0316.CR2 <<< now correct folder 
2011\2011-07-22\20110722-003049-IMG_0317.CR2 
2011\2011-07-22\20110722-013055-IMG_0318.CR2 
2011\2011-07-22\20110722-023102-IMG_0319.CR2 

This seems to be some "time zone / daylight savings time bug" affecting all photos made from two hours before midnight until just before midnight (my local time is UTC plus two hours) - but why only for camera USB and not for card reader? I didn't test it for a date that has no DST, but I would bet that it would affect photos from *one* hour before midnight, then. 

P.S. The wrong folder structure also already shows in the folder preview in the import dialog. Here is the wrong structure using USB to camera: 
 
...and the correct one using a card reader: 
Photo of LRuserXY

LRuserXY

  • 426 Posts
  • 41 Reply Likes
  • confused

Posted 7 years ago

  • 22
Photo of Ralph

Ralph

  • 1 Post
  • 1 Reply Like
Is there going to be a fix released for this issue any time soon? It is unbelievable to think this issue has gone unresolved for over two years.
Photo of Sarit Sotangkur

Sarit Sotangkur

  • 2 Posts
  • 1 Reply Like
This really needs to be fixed in the next update.
As a software developer myself, I know the fix will be relatively simple. Also as this is a workflow/productivity issue, it should really be considered a high severity issue for a core workflow/productivity application like LR.

Adding an extra step to your workflow is really not an acceptable solution for a product advertised to simplify your workflow.

Everyone else, please bump this thread if this is also important for you.
Photo of Luis Alfaro

Luis Alfaro

  • 1 Post
  • 1 Reply Like
It's Lr 5.4 now, three years later and the bug persists... unbelievable!
Photo of Andrew Kielbasinski

Andrew Kielbasinski

  • 1 Post
  • 0 Reply Likes
Anyone try this in LR 5.6? I ran into this while demoing LR and it has kept me from making a purchase.
Photo of Mike Hazlett

Mike Hazlett

  • 4 Posts
  • 0 Reply Likes
I'm a new user of LR v5.6.
I am auto-importing JPG images from a scanner. The scanned images are placed in a temp folder and LR auto-imports to a "Destination" folder using a file renaming template......
{Date (YYYMMDD)>>}_{Hour>>}{Minute>>}{Second>>}
And, of course the hour appears to be off by my timezone offset to UTC. Or something like that.
So, I don't see how the SDcard work around can help me out.
Also, waiting for the fix, I guess. Maybe only another year, or so. 8-)
Photo of Ray Vran

Ray Vran

  • 8 Posts
  • 0 Reply Likes
Just use the "Metadata > Edit Capture Time" feature using "Shift by fixed number of hours", (In some case you don't have to shift anything - you go in it shows the "right time" - you execute the commard).

The above will work on batches of photos preserving their date/times relative to each other.

Then go into "Library>Rename Photo" where you have similar options to "Import" for filenaming.

I'm not sure why the time of capture of the scan is particularly important or would cause concern (as long as scan times relative to each other are consistent). i can see why the original correct capture time of the photo is useful (as metadata)- but not the scan of the photo.
Photo of Mike Hazlett

Mike Hazlett

  • 4 Posts
  • 0 Reply Likes
Well, you are right that the time of capture is "not important". The point is that LR is not performing the operation , as intended. The end product that I need is a unique filename.
When I first tried to import a batch of scans, the hour-minute-seconds piece of the filename that was assigned by LR didn't make sense to me. I thought that I messed up the "filename template editor". So, I came to this forum looking for solutions. And I find that others have been experiencing this issue for a long time.
I understand it is a bug in Windows but not for the Mac.
Don't you think Adobe would want to make it right?
Photo of Ray Vran

Ray Vran

  • 8 Posts
  • 0 Reply Likes
I have been "watching" this bug for a while and I am pretty sure its not an easy fix and possibly not a LR bug. here are 3 examples.
1. If I import from and SD card I get different outcome to importing the same stuff from the camera through a USB interface. This suggests an operating system problem rather than an LR problem.
2. It only happens for windows not Macs - LR picks up data from fields populated by the OS - (same conclusion as for 1 above)
3. In LR I use a preset to rename images to a date/time format. Sometimes this is wrong. I go in to Edit capture time, change nothing in the dialog since I see the capture time shown is correct (but not the one used by the preset) then still execute the change capture time, then reuse the preset and the time is now right. So different bits of LR pickup different time stamps - I know there are squillions of timestamps to choose from in the metadata associated with a file and I suspect that in Windows these may not be defined as well as they should be - so programs comply with the not clear definitions but the outcome is confusing. So this last one gives me hope that even if LR is not the problem, it could maybe fix things up by working around a windows problem (as it does in getting the time for the edit capture time dialog) - however not sure if such a fix will introduce other problems - or will cause probelms downstream.
Photo of Michael Artz

Michael Artz

  • 7 Posts
  • 0 Reply Likes
Wouldn't it be nice to have one of those programmer "engineer" type dude or dudettes explain this?
Photo of Michael Shkolnik

Michael Shkolnik

  • 1 Post
  • 1 Reply Like
More than anything, it's plain shameful to Adobe that 3(!!!) major releases of lightroom were released since this problem was reported and many more smaller releases and this bug hasn't been fixed. It's lightroom 6 now, people!

Seems like a relatively easy thing to fix as the problem has been already pinned down to certain circumstances.

I just can't get why isn't anyone dealing with this.
Photo of Benjamin Warde

Benjamin Warde, Employee

  • 483 Posts
  • 72 Reply Likes
"I just can't get why isn't anyone dealing with this."

This may have been rhetorical, but in case not, I'll answer it. We need to prioritize everything we do. Low impact bugs with easy workarounds get prioritized lower. It doesn't necessarily mean that it will never be fixed, but it does mean it's hard for it to get to the top of the list.

-Ben
Photo of John F

John F

  • 5 Posts
  • 3 Reply Likes
I never found an easy work around. I always had to manually do a lot of work every time I did an import to ensure that the correct folders were created and photos moved into them.

Perhaps you could be so kind as to outline the easy workarounds??

This ancient but still present bug no longer affects me. I did an expensive workaround and bought a Mac and bug does not exist in the Mac version. However I'm sure the Windows users would be grateful for any tidbit of help you can reveal to workaround this painful yet trivial to fix bug.
Photo of Benjamin Warde

Benjamin Warde, Employee

  • 483 Posts
  • 72 Reply Likes
Sure thing. The bug occurs only when importing directly from a connected camera. If you use a card reader, the bug will not occur. If you don't have a card reader, you can connect your camera directly, and first copy the photos from the camera to your hard drive in the OS, then import into Lightroom from the hard drive.
Photo of fred_worley

fred_worley

  • 1 Post
  • 0 Reply Likes
I have experienced this problem when importing from a card reader, not from the camera.  The problem only seems to affect .MP4 files, not .CR2 or .JPG files.  Importing from a card reader results in 20160708-IMG_9555.CR2 and 20160709-MVI_9556.MP4, followed by 20160708-IMG-9557.CR2.  A .MP4 shot at 2:13pm imported into the correct (7/8/16) folder.  A .MP4 shot at 5:19pm imported into the incorrect (7/9/16) folder.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3676 Posts
  • 961 Reply Likes
Here's what's likely happening with your MP4s: The QuickTime spec (which is also for MP4s) says that capture times should be recorded as UTC (similar to GMT).  If you're in the PDT time zone, then a pic taken at 7/8/16 5:19p PDT would be recorded in the MP4 as 7/9/16 0:19a UTC.  The spec provides no mechanism for recording time zones, so LR reads that date and time as "local" time.

Apple, and the industry at large, has made a mess of date/times in QuickTime video. There's no perfect solution for what LR should do in the face of this mess, but I made a proposal for how LR might better (but still imperfectly) handle the situation.  See here: https://feedback.photoshop.com/photoshop_family/topics/iphone_video_capture_time_is_shifted_upon_imp...
Photo of Michael Artz

Michael Artz

  • 7 Posts
  • 0 Reply Likes
Can someone explain how this isnt resolved... its a right royal pain in the butt!

EVERY TIME I IMPORT!
Photo of Jim Wilde

Jim Wilde, Champion

  • 272 Posts
  • 87 Reply Likes
Immediately above your post are two posts from Benjamin Warde (Lightroom Engineer). The first explains why the problem has not yet been fixed, and the second explains the very simple workaround.
Photo of Michael Artz

Michael Artz

  • 7 Posts
  • 0 Reply Likes
Yes, save to desktop first or use a card reader?
I travel and whilst card readers are minimal sized, I will move heaven and earth to travel with one less apparatus in my burgeoning camera bag.
and saving to HD first...egad, it's a work around..yes it is

For me, maybe moving my camera date to Greenich (is that the problem?) would be the easiest...I cant think when ive checked a time on the camera?
Photo of Michael Artz

Michael Artz

  • 7 Posts
  • 0 Reply Likes
Oh and...saying its "on the list"...for 4 years come on... Like John below Ive worked in software engineering..and what he (Benjamin) describes is not anything to do with software engineering. Im unsubscribing from this list now, thanks for the work flow intrusions. Ill keep trying from time to time to see if it gets resolved.
Photo of John F

John F

  • 5 Posts
  • 3 Reply Likes
The two workarounds would be fine if importing was something you did every few months. However a serious user may do importing four or five times a day, every day, and in this case the annoyance of using the workaround multiples many fold until you just want to scream.

In particular one workaround suggested was to remove the memory card from your camera and use a card reader. This is ok if done rarely but I would never suggest that one do this repeatedly. The memory card and card reader are physical devices and if stressed repeatedly they will fail. If the memory card reader in your camera fails or becomes intermittent you must throw the camera away...

The other work around where you copy the files via usb to the computer and then import from a folder takes a lot of monitoring by the photographer to make each step happen. Comparing that to just plugging the camera into the computer and clicking import you end up wasting a tremendous amount of your time waiting for copying to occur and you end up thinking poorly of Adobe.

As a programmer myself working on a long running project with many releases I understand the concept of reviewing bugs and choosing those to be fixed in the next release. You have someone at Adobe who is doing that job and I suggest you fire that person and hire someone who is a photographer and who uses the Windows platform. I guarantee that this bug will get fixed. The fact that it still exists after all this time is a tremendous embarrassment to Adobe.
Photo of Jim Wilde

Jim Wilde, Champion

  • 274 Posts
  • 89 Reply Likes
I take the opposite view. In my experience, importing via card reader (built-in or usb-attached) is both quicker and safer (and has the other advantage of being bug-free). If I'm asked for a recommendation, I'll always say use a card-reader, which is the method used by the majority of my photographer acquaintances.

I spend a great deal of time on various Lightroom forums, trying to help other users with their varied problems. And I can honestly say that the number of problems I've seen, which are directly attributable to importing via direct camera attachment, far outweigh the number of card-reader associated issues. Only today I was dealing with such a problem at the Adobe U2U site: https://forums.adobe.com/thread/1849151

Not wishing to be argumentative, just wanted to offer a counter-view.
Photo of Michael Artz

Michael Artz

  • 7 Posts
  • 0 Reply Likes
and all the while Adobe are silent...
Photo of John R. Ellis

John R. Ellis, Champion

  • 3676 Posts
  • 961 Reply Likes
"and all the while Adobe are silent..." Actually, search the entire thread in your browser for comments from Benjamin Warde (employee). He's provided updates to this thread for the past several years, he's explained why Adobe hasn't prioritized a fix, and he's provided workarounds. (You need to expand some of the comments to see all of his replies.) You may obviously disagree with him, but it's unfair to say that Adobe has been silent.
Photo of Michael Artz

Michael Artz

  • 7 Posts
  • 0 Reply Likes
thanks John. Perhaps I should say ineffectual. I have used many different importing/file storage solutions over the years and none have had this flaw reading from a camera.
Reading other forums it seems this module is quite "unstable" and I would expect a company of Adobe's reputation to have dealt with it in the time frame of this thread!
I guess firstly I was quite happy to see it wasn't something I had inadvertently missed in camera setup and that this was a common problem expressed in this thread..however when I then read the date of the posting... and scrolled

Ill do one of the work rounds (like everybody else) but it really ought to be resolved
Photo of John F

John F

  • 5 Posts
  • 3 Reply Likes
Compact Flash cards are very rugged compared to SD cards and have a more reliable way of connecting to the card reader. SD cards however are the future so more and more issues will come up from using the card reader solution.
You won't see the problems reported in this forum. The photographer will be complaining in the camera forums about the fact that he can't seem to write images to his SD cards any more.

What's particularly bad about this bug is that it affects so many people and it is so trivial to fix. Clearly Adobe knows how to deal with time zones. It does the right thing with the direct file import. There's no reason it can't correctly deal with time zones when reading the files via a USB cable. Just copy and paste the code to do the time zone adjustment from the file importing code to the USB importing code.

The time need to fix this would be less than a hour. We've spent more time talking about it than it would take to fix it.
Photo of Michael Artz

Michael Artz

  • 7 Posts
  • 0 Reply Likes
Heck open the code and we'll do it for ya!
;)
Photo of LRuserXY

LRuserXY

  • 426 Posts
  • 41 Reply Likes
> "Just copy and paste the code to do the time zone adjustment from the file importing code to the USB importing code."

The "funny" thing is: The date in the filenames is already correct (see my original problem report), so it would be much simpler: Just use the existing code for the date in the filenames! ;-)
Photo of Eric Blumer

Eric Blumer

  • 1 Post
  • 0 Reply Likes
What is the workaround if you are importing from an iphone?
I bought a new iphone and didn't notice for two months that the photo restore did not work properly. I was missing 5 months of photos. No problem I thought, I will manually copy them back from Lightroom.
After that when I import the photos are imported into a folder with the manual create date and not the metafile capture date. I therefore now have duplicates. The original photos that are in the metafile capture date folder and the newly imported photos that are in the manual load create date folder. On these photos the metafile capture date is correct.

Work around someone???
Photo of the user

the user

  • 1 Post
  • 0 Reply Likes
This reply was created from a merged topic originally titled Lightroom: HHMMSS file naming in import is 5h later then original video file, plu....

Adobe Lightroom CC 2015.1.1
Canon 6D, Windows 7

I use the following name convention for my files (partialy shown):
_YYMMDD_HHMMSS_
When I import videos in Lightroom, directly from the camera, the hour is behind 5h.
My local time is MST (-7).

For example:
time of file in camera : 9:54:57
file name after import: 16:55:08

The minutes and seconds difference, besides the 5h, is due to the fact that LR uses the time when the file was written, not the time when the recording started. So this particular file was a 11 seconds long video.

Would very much like to get the right hour and the time the recording was started not the time it ended.

Thanks !

If I may, there's a problem with the tags, if I edit the post, the tag box has all the tags concatenated with no commas in between, so I have to add the commas back between the words every time I edit this post.
Photo of Bob Smith

Bob Smith

  • 11 Posts
  • 3 Reply Likes
This reply was created from a merged topic originally titled Incorrect time based filenames when shooting tethered.

I shoot tethered quite a bit with a variety of Canon cameras.  I prefer to have Lightroom rename my files on import based on date/time.  The time in the file name is always off while the time in the metadata is correct.  This seems to be happening because Lightroom file naming function is incorrectly using the Time Zone setting on the camera during tethered capture.  The amount of error exactly matches the time zone correction.  My 6D and 5DS-r both show this problem and both cameras have a time zone setting.  My 5DmkII does not have the time zone setting and does not show the problem.

This problem with time base renaming ONLY happens during direct Lightroom tethered shooting.  Renaming files when importing images from a camera card always works as expected.  Using a workflow where EOS Utility tethers the camera and dumps images into a watched folder... then Lightroom takes over to import (including rename)... works as expected.

Mac OS 10.12.2  Lightroom 2015.8 but this problem has persisted for quite a while. At least two years?  My 6D is at least that old.  That's where I first discovered this issue but I rarely use that camera tethered.  My relatively new 5Ds bodies will spend most of their life tethered so I'm taking the time now to track down the source of the problem.


Thanks



Bob Smith
Photo of John R. Ellis

John R. Ellis, Champion

  • 3676 Posts
  • 961 Reply Likes
As you can see in the rest of this topic, importing via a USB cable causes file renaming to use the wrong time.  It's most likely that tethering suffers from the same underlying bug.  Given this bug has been around at least 5 years, in my opinion it's unlikely Adobe will ever fix it.  

For those not tethering, the workaround is straightforward, if mildly inconvenient for some: Import directly from the card.  Of course, that's not an option when tethering.
Photo of Bob Smith

Bob Smith

  • 11 Posts
  • 3 Reply Likes
Thanks... certainly seems related.  The age of this thread does not inspire confidence that I'll see a solution soon (ever?).  That's a shame.  Adding EOS Utility to the workflow works just fine but in high pressure time sensitive situations you really don't want one more app in the workflow.  It's just one more possibility for something to go wrong... and it slows down by a second or two the time it takes for an image to appear on screen.  I've had very good luck with Lightroom direct tethering except for this annoyance.
Photo of Sarit Sotangkur

Sarit Sotangkur

  • 2 Posts
  • 1 Reply Like
The only hope to getting Adobe to fix this is to get your friends to come here and complain about it. "The squeaky wheel gets the grease."
Photo of Jim Wilde

Jim Wilde, Champion

  • 274 Posts
  • 89 Reply Likes
John, I don't see this as being related to the initial problem. There are a couple of significant differences:

1. Bob is seeing actual file-names with the wrong date/time, not the folder names which is what this thread was about.
2. If I'm reading Bob's post correctly, it's not a simple "USB cable" problem....there are apparently no problems when tethering with his 5D2, only with his cameras which have a time-zone setting.

Personally, I think this should stand as a separate bug report for now, and not be simply bundled into this "wrong folder names when importing from a direct camera attachment" thread.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3676 Posts
  • 961 Reply Likes
Some others have reported time-zone errors in the filenames, e.g. https://feedback.photoshop.com/photoshop_family/topics/lightroom_import_wrong_folder_names_organizin...

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.
Photo of Bob Christensen

Bob Christensen

  • 1 Post
  • 0 Reply Likes
Totally pathetic this is still an issue. Must be some kind of petty personality conflict. Very basic feature.
Photo of Robert Cullen

Robert Cullen

  • 145 Posts
  • 40 Reply Likes
Still a problem for iPhone imports by USB.  Six photos- all with same date metadata, imported into three different dated folders. See my Post#3 at- https://forums.adobe.com/message/10621597#10621597

Photo of PLATT JOHNSON

PLATT JOHNSON

  • 2 Posts
  • 0 Reply Likes
So - this has been going on for 7 years. WOW - thought I would repost this from a similar thread in hope of getting some traction.
"It's embarrassing that after many years of this bug being reported, Adobe still hasn't fixed it. It completely messes up my workflow"
Photo of herrclich

herrclich

  • 11 Posts
  • 2 Reply Likes
This reply was created from a merged topic originally titled Lightroom Classic: iPhone imports photos to wrong folders (date).

with LR 6.10.1 the import of photos seems to be random regarding the date of capture. Photos are not detected as already imported and will be placed in a totally wrong folder. I use a standard LR folder structure that is based on the capture date.
Today I was importing again from the iPhone and LR found over 800 new photos to import. A lot of them were already there, but the actual LR version placed them in totally wrong folders (capture date). some are from 2012 and are now imported to a folder of 2017. The exif data and also the LR meta data is showing the correct capture date.

Some weeks ago I have already posted the issue, but somebody merged the topic with a video import issue. Please do not merge it again with such a topic. It is strictly related to the photo import and has nothing to do with mpg4 time zone issues.

I am referring to the following initial report:
https://feedback.photoshop.com/photoshop_family/topics/wrong-date-on-import-photos-from-iphone