Copy link to clipboard
Copied
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 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 any where else in the workflow works as expected.
I can and do use an EOS Utility to Lightroom workflow for tethered shooting that gets the proper naming results. There are situations where a simpler (and slightly faster) workflow is needed. After several months of only using this workflow I just tried to go back to a Lightroom only tethered workflow and was quickly reminded of why I had abandoned it with my newer Canon DSLRs.
I'm posting primarily in hopes that this gets some sort of notice by someone in a position to correct the problem. Except for this very annoying glitch, tethered shooting has worked quite well for me.
Thanks
Bob Smith
Copy link to clipboard
Copied
Why aren't the cameras and your computer set to the same time zone and time? It seem doing that should clear up the problem.
Copy link to clipboard
Copied
They are all set to the same time and time zone. Again, the time in the metadata of the file is exactly correct... matches the computer exactly... but the time in the file name is different by the same number of hours as the time zone correction
Copy link to clipboard
Copied
Recheck the camera clock settings to make sure the time zone is set correctly as opposed to the UTC time being set to local time.
Copy link to clipboard
Copied
Time and zone are set correctly on both. I just checked again to be sure.
If this was an issue with that setting then I assume that I'd be seeing errors in ANY date/time renaming. I only see it if renaming occurs during Lightroom's tethering connection. It doesn't happen on imports from a camera card out of the same camera. It doesn't happen if I shoot tethered with EOS Utility to a specific folder then let Lightroom's Auto Import take over and import (and rename) the files. And this is only an issue with the time in the filename... not what appears in the metadata.
for what its worth... I use EOS Utility to sync the camera's clock to the computer's every time they are connected. It keeps multiple cameras exactly synched to the second.
Copy link to clipboard
Copied
Bob,
This definitely looks like a bug. Try submitting a post here:
Community-powered support for Photoshop Family
That site is looked at by Adobe developers. This site isn't.
Hal
Copy link to clipboard
Copied
Just posted there... Thanks for the link Hal
Copy link to clipboard
Copied
I think you've encountered a variant of the import-via-USB-cable bug, which has been outstanding for at least five years: https://feedback.photoshop.com/photoshop_family/topics/lightroom_import_wrong_folder_names_organizin...
Copy link to clipboard
Copied
FWIW, I have the same problem using a Nikon D850. I've been experiencing this for years when shooting Canon 1Dx tethered as well. My file naming is 5 hours off and I'm in the Eastern Time zone (UTC+5). Any update on how to work around this bug?
Copy link to clipboard
Copied
Hi I have tested tethered with an 5D and i have found the same bug there. The Metadata of the images importet are correct bat the reaming during tethered shoting hast the wrong name and if i import the same images from card later they are not detected as duplicates.
Is ther any fix for that. I think only the reaming inside of the tethered function is using the laptop time with wrong timezone. But the reanming have to use the date und time form the file meta data and the it will be corect.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now