BobSmithTX
Explorer
BobSmithTX
Explorer
Activity
‎Nov 25, 2023
10:51 AM
10 Upvotes
I shoot tethered a lot, mostly with Canon R5 cameras. I just upgraded from a Mac M1 Mini on Ventura to an M3 Mackbook Pro on Sonoma. I'm using the same displays, drives and catalog as before. Tethered shooting is working as expected except that I can't show the control panel that lets me alter camera settings and fire the camera. The menu option to hide and show that panel is there... just does nothing. I can fire the camera from the camera or using command-T and images appear normally. I just can't see the controls. Any ideas? LRC 13.0.1 Sonoma 14.1.1 Bob Smith
... View more
‎Sep 20, 2023
04:10 PM
1 Upvote
Solved. I uninstalled 14 and removed prefs. I uninstalled 13 and kept prefs. I reinstalled 14 only and imported 13 prefs as part of the install. My ancient template is recognized and works just fine now. I *think* the first time I installed 14 that I neglected to select the option to import 13 prefs. The new 14 prefs did something to caused the template to not be recognized in either version on this computer. My workflow is very happy again. Thanks all! Thanks all! Bob
... View more
‎Sep 20, 2023
01:44 PM
I recall doing that for exactly that reason a few years ago. I’ve not seen any notice or documentation of a change since. The template that is not recognized at all anymore still works fine in the latest v13 on another computer. I would think there’d be some sort of prominent notice from Adobe if a change was made to v14.
... View more
‎Sep 20, 2023
12:55 PM
1 Upvote
Install of v14 broke my main reason for opening Bridge... to run a very simple custom output module template. It's not recognized in v14. I reinstalled v13 and it wont work there either now. The computer involved is an M1 Mini, Ventura 13.5.2. Ive used the same template reliably for many years on numerous versions through the last v13 version without any issues. I haven't upgraded the Bridge install (13.0.4.755 on my laptop (M1 Air, Ventura 13.5.2.). Same template works fine there. Any ideas how to troubleshoot this? Thanks! Bob Smith
... View more
‎Apr 24, 2023
01:34 PM
2 Upvotes
Thanks John & Bob! I was unaware of the "preserved filenamename" option. I'll use it. But I would still strongly prefer a set-once-and-forget-it option in preferences
... View more
‎Apr 24, 2023
10:12 AM
4 Upvotes
I've used Lightroom Classic regularly since V2. I've always used the option in prefs under External Editing to enter my chosen way of appending the filename of files that have been edited in Photoshop. I choose nothing. In my catalog, I know that a TIF or PSD was edited outside of Lightroom. I don't need anything extra added to the file name. I LOVE that you give me the option to work that way and keep original file names clean and intact. Simple! I've always hated that we can't do the same with Pano and HDR files. A dash and small p or h added to the name would plenty sufficient for me and less confusing to clients getting the files. Now we have a wonderful new AI noise feature that adds an even more complex name to derivative files with no option to alter it. You've moved me to finally sit down and write this! Batch renaming files with another app outside of Lightroom is a recipe for disaster and workflow nightmare. PLEASE give a simple option in prefs to specify what we want appended to HDR, PANO and now ENHANCED images. Thanks, Bob Smith
... View more
‎Jan 03, 2017
07:05 AM
Just posted there... Thanks for the link Hal
... View more
‎Jan 03, 2017
04:27 AM
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.
... View more
‎Jan 02, 2017
03:39 PM
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
... View more
‎Jan 02, 2017
02:12 PM
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
... View more
AdChoices