Bug Reports

I just updated both Lightroom Classic and Photoshop to the latest versions (11.1 and 23.1)   I'm in Lightroom and I have an export action that ends with opening the current image in Photoshop (see screenshot below)   If the folder path where the image resides has parenthesis in it (even just one bracket, actually), Photoshop fires up but no image is open. Could you please look into this?

In Norwegian (nb_NO), the shortcuts assigned to Rotate Left (Shift + J) and Rotate Right (Shift + -) don't work.   In Library, Shift + J invokes View > Grid View Style > Cycle View Style (which is assigned J).  In Develop, Shift + J invokes Tools > Create New Mask > Color Range (which is assigned Shift + J).   In Library, Shift + - works, but in Develops it decrements the current Basic slider.   Note that shortcut help in Library and Develop is also wrong, showing Command + [ and Command + ] as the shortcuts. The offending lines in TranslatedStrings_Lr_nb_NO.txt are:   "$$$/AgLibrary/Menu/Photo/RotateLeft/Key=Shift+j" "$$$/AgLibrary/Menu/Photo/RotateRight/Key=Shift+-" "$$$/AgLibrary/Help/Shortcuts/RotateLeftKey=Command + [" "$$$/AgDevelopShortcuts/Rotate_left/Key=Command + [" "$$$/AgLibrary/Help/Shortcuts/RotateRightKey=Command + ]" "$$$/AgDevelopShortcuts/Rotate_right/Key=Command + ]"    

Hallo zusammen!   Leider funktioniert in LR Classic (hier 11.3.1. / Mac OS Monterey), deutsche Sprachversion, die Ordnersuche nach Namen in denen Umlaute vorkommen nicht. Z.B. Bäume, Äste, Hügel …    Wenn man jahrelang ein Ordnungssystem was über die Ordnernamen funktioniert aufgebaut hat, ist das äußerst ärgerlich.   Hat jemand eine Idee, wie man die Ordnersuche bei der Eingabe austricksen kann?   Ansonsten an die Entwickler: bitte diesen Bug bei der Lokalisierung unbedingt beheben!   Vielen Dank für jeden Tip / Hilfe.   Hubertus

LR handles camera model names containing parentheses inconsistently (e.g. "iPhone SE (2nd generation)").  The model name shown in the Metadata panel and returned to plugins via photo:getFormattedMetadata () discards everything from the first parenthesis to the end, while smart collections and the Camera column in the Metadata browser see the entire model name. I first noticed this using my Any Filter plugin. 1. Make a new catalog. 2. Import the attached photo. 3. In the Metadata > EXIF panel, observe that Model is "iPhone SE": 4. Observe that the Camera column in the Metadata browser shows "iPhone SE (2nd generation)": 5. Create a smart collection "Camera contains words 2nd generation". 6. Observe that the smart collection matches the photo. 7. Exiftool shows that EXIF:Model is:  $ exiftool -a -G -s -model IMG_2955.jpeg [EXIF] Model : iPhone SE (2nd generation)   8. Observe that photo:getFormattedMetdata ("camera

Locking the crop aspect ratio doesn't work after copying/pasting a crop or after using LrDevelopController to set a crop from a plugin.  Attempting to resize the locked crop will reset the aspect ratio to Original.  This appears to have broken in a recent version, and it makes my Any Crop plugin significantly less useful.To reproduce:1. Go to a raw photo in Develop.2. Open the crop tool and make sure the aspect ratio is unlocked (Settings > Constrain Aspect Ratio is unchecked). 3. Use the crop tool to set a long, narrow crop.4. Close the crop tool.5. Do Settings > Copy Settings, Check None, check Crop, then click Copy.6. Go to another raw photo in Develop.7. Do Settings > Paste Settings.8. Open the crop tool and lock the aspect ratio (Settings > Constrain Aspect Ratio is checked).9. Resize the crop by dragging one of the corner crop handles. Observe that the aspect ratio immediately reverts to Original (bug).10. Do Reset to reset all the photo's dev

Rotate Left and Rotate Right are not greyed out in the right-click context menu for videos in Library:   They should be greyed out.   Tested on LR 11.5 / Mac OS 12.4.

Allowed the upgrade to 11.4 LR Classic happen. Follow that by an import of some new images. Adjusted and then exported using my usual pre-set that includes "simple watermark". No watermark showing in created image. Today I experimented with exporting an image from my last imporot prior to upgrade.  No changes to any data including the export preset. No watermark showing on the exported duplicate image. Something is amiss. Opoeratingi system is OSX 11.6.6. As a workaround I created a custom watermark text. But I really like the "simple watermark" that gets the data from the copyright data field that way I don't have to worry about the mark being different than what I put in my data for each image. Is this an image data disconnect or a disconnect with system fonts? In either case I would have expected the simple watermark capability to work like before.   Regards,

I've had two sessions with Adobe support for Lightroom Classic Case ADB-25583947-S0X9.  Neither has solved a problem that's been going on for two months.  They promised another share session and CLAIM they are not able to get through to me.  All I get is a voicemail saying they've tried on both my contact numbers BUT neither phone rang, I've not been on either phone and this has happened two days in a row.  Then I get an email with a link for a share session.  I click on the link and get message that I was trying to use an invalid session key.  I WAS NEVER GIVEN A SESSION KEY, JUST THE DAMN LINK.  It seems to me that Adobe is out of ideas on trying to fix my problem and just trying to frustrate me so I will give up.  Adobe, please I hope somebody who really cares at all will read this and try to help.

When synching a number of folders, resulting in some photos from being added, and other being removed, empty photo-objects result in the library in place of the original photos. These do not show when browsing by folder, but do show when selecting All Photographs and filtering for instance by date. They result in a blank, gray photo thumbnail, that does not have a file name or any other metadata associated (therefore the assumption these are NULL). Optimizing the catalog does not improve this situation. Issue occured on 8.1 and remains on 8.2. Working with the files now becomes very slow, as Lightroom has great problems handling the NULL objects.

Als Benutzer kann ich keinen Kopiennamen im Feld "Metadaten > Kopiennamen" eintragen.Trage ich einen Namen der Kopie ein, wird dieser nicht gespeichert. Trage ich zusätzlich eine Bildunterschrift ein, dann wird der Kopiennamen und die Bildunterschrift gespeichert. Lösche ich die Bildunterschrift wieder, dann bleibt der Kopiennamen erhalten. Meine Lightroom Classic Version ist die 11.4.1   Ich habe Lightroom Classic neu gestartet, auch den PC komplett heruntergefahren und neu gestartet. Das Problem tritt trozdem weiterhin auf.  

Lightroom classic v10 (Win) does not sync aspect ratio changes to cloud. Images appear distorted (stretched) when you view them on mobile devices. Using the edit mode in cloud based Lightrooms shows that the aspect ratio change has not come through during sync.

Issue:  Lightroom Classic Version Number: V15 and V14 OS Version Number: Windows 10 Steps to reproduce: import a Photo with GPS geo-location tags the location fields (state, country, city, details) will be set automatically and shown greyed out Edit and change e.g. the city Navigate away from photo and come back (Added by Mod) Expected result:  the city shows the new value (not greyed out) and all other greyed out location fields stay with their old value derived from the GPS-coordinates.Actual result: the city shows the new value (not greyed out) and all other  location fields have their old values removed/cleared.   This is annoying if you have to adapt a lot of locations (typically CITY) where the default is not suitable. In V13 it worked as expected. I have 80,000 geo-tagged aerials where this information is crucial.

If I have an active tether session and then click on the gear icon to update the tether settings and making any changes to a live tether, hitting the return button causes LR to crash. It will not crash if I click on "Ok"   I have a team of computers using the following: LR 11.0 or later Big Sur or Catalina  Canon 6ds or canon 6dII.     This is an issue on all computers using the above set up.

LrStringUtils.compareStrings() doesn't compare strings containing digits correctly.  For example, it says that "a9b" comes before "a10b":It appears that compareStrings() is comparing sequences of digits numerically, e.g. as the numbers 9 and 10 in the example above.   While that definition can be useful in some cases, such as ordering filenames containing sequence numbers, it is not generally useful for sorting.  The SDK should restore the traditional meaning to compareStrings() and optionally provide a second compare function for the current functionality.

I have one image with two virtual copies (A - original, B, C).All images have presets applied.When I quickly switching from A to B and then to C (using arrow keys on keyboard) the preset from the image B is being applied to image C.   MacOS 12.4 Lightroom Classic 11.4.1 Camera Raw 14.4.1   Here's a screen recording. The only input is right arrow pressed twice. You can see that the preset from image B (B'n'W) is being applied on image C. https://youtube.com/shorts/QP12dwse9ms?feature=share   

Lightroom issue. When I import a few Pictures sometimes some Pictures has a wanring "Lightroom can't read the Picture" (germen). The Picture is correctly imported, I also can open it with other programs. I'm able to remove the Picture from Lightroom (and Hard Drive), restart Lightroom an try to import it again (from Disk oder CF-Card). Import succeeded but the error still remains. I'm using Lightroom 3.4.1. Thanks for suggestions!

hiI have a problem after the last update, the sidebar with the navigator does not work, it is partially obscured. the new installation did not help, resetting the preferences does not help, I also tried to change the panel display options, nothing helps. While the English language is set, everything is fine, I am asking for advice and possible help.          

Keyboard shortcuts for Create A Depth Range are missing for ES, IT, and SV.  All other languages assign Shift +Z.   ES, IT, and SV assign Shift + Z to Create  A Radial Gradient, while all other languages assign Shift + M.   This is as-coded but surely not as-designed (what possible design rationale could there be?) -- it's just a clerical error.   To make those languages consistent with all the others:   - Assign Shift + Z to Create A Depth Range - Assign Shift + M to Create A Radial Gradient (currently assigned Shift + Z)   Shift + M is not currently assigned in those three languages.   $ grep -i view/depthrange/key *.lproj/*.txt de.lproj/TranslatedStrings_Lr_de_DE.txt:"$$$/AgDevelop/Menu/View/DepthRange/Key=Shift+z" es.lproj/TranslatedStrings_Lr_es_ES.txt:"$$$/AgDevelop/Menu/View/DepthRange/Key=" fr.lproj/TranslatedStrings_Lr_fr_FR.txt:"$$$/AgDevelop/Menu/View/DepthRange/Key=Shift+Z" it.lproj/TranslatedStrings_Lr_it_IT.txt:"$$$/AgDevelop/Menu/V

Since I upgraded to lightroom classic from lightroom 5.7.1, imports are now importing duplicate images, even though I have checked don't import suspected duplicates. It happens on both my nikon and canon camera images.

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   You can't create a preset group containing a space when the option Preferences > File Handling > When A File Name Has A Space is set to Replace With An Underscore. Originally reported by David Brookens: https://www.lightroomqueen.com/community/threads/masks-as-presets.44625/    To reproduce:   1. Set the option Preferences > File Handling > When A File Name Has A Space to Replace With An Underscore.   2. In Develop, create a preset, and in Group, select New Group.   3. Enter "X Y" for the group name, and observe that Create is greyed out: 4. Instead, enter "XY" and observe that Create is now enabled.   5. Set the option Preferences > File Handling > When A File Name Has A Space to Leave As-Is.   6. Repeat steps 2-3 and observe that Create is not greyed out.   Obviously, preferences about file namin

In past versions of Lightroom Classic, if a map location was marked as "Private", all location data (including both GPS data and hand-entered IPTC location data) would be stripped from the photographs on export. As of Lightroom Classic 11.4, it appears that the "Private" switch on locations is no longer being honored: exported photographs that have been marked as being at a private location are exported with all location data included.   STEPS TO REPRODUCE 1. Create a location in the Map module, checking the box to mark the location as private. 2. Select a photograph and apply the location to it. 3. Export the photograph. Make sure that the checkbox 'Remove Location Info' is unchecked. 4. Inspect the metadata on the exported photograph (on MacOS, use the Finder's Get Info)   EXPECTED BEHAVIOR Latitude, Longitude and other location-related metadata should not be included.   ACTUAL BEHAVIOR Latitude, Longitude and other location-related metadata are present in the exported

Currently if you select the 'high' option for export sharpening, the resulting image is less sharp than the 'standard' option. The outputted file for the 'high' option is identical to the 'low' option.

Hello,over quite a long time it was easy to take photos with my android smart phone in heic format and import it and use it in LrC on my iMac.But suddenly, the heic images are not supported any more by LrC - they can still be open on the iMac. It's possible to load the files to the cataloge, but not even the preview in LrC is working. Unfortunatelly I can not upload these files here. I put them to my nextcloud server - hopefully the link will not break:https://cloud.hoststar.at/s/DjLJT22oZ8HofDk Can please somebody explain, whats the reason why the one file is supported and the other one not?And my be even tell me, what to do to make the not supported image work with LrC?(Until I have no better idea, I have to convert all my not any more supported heic files to jpgs and import then and for new pictures, I also have to use jpg as file format. You can imagine - this workarround is something I don't like to go...)

I have been living with this problem for a while where I get errors trying to move folders and files and rename folders in Lightroom Classic.Some of the time I can unselect al files and try again and it works but not always.Normally for clients I work catalog by catalog so don't really deal with the issue heaps but ive started going through all my old catalogs and preparing them to merge into one so now i'm seeing the error repeatedly.I've posted an example of it in an unlisted video to show the problem.You can see here https://www.youtube.com/watch?v=T10d5ZTGl6w&feature=youtu.beHelp appreciated , the lack of information and a simple "retry" button would save me so much time even with the problem in place.I've still got hundreds of catalogs to go and in each hundreds of folders so i'm going to see these errors a lot.Seems like lightroom is doing something with the files in the background and tripping over itself.ThanksRob

Hi, I'm using a new Wacom Intuos Pro with latest Firmware. According to Wacom's Diagnosis Tool the pressure sensitivity works fine from 0-100%.However, in LR I cannot use the pressure sensitivity as I'm always getting the full 100% (e.g. when using the adjustemnt brush). I know this was an issue in the past but should be solved by now.I'm using Windows 10, latest release, on a high perfomance PC.Does anyone have a clue where I need to search for a solution? Without that feature the tablet is almost useless....BTW: It's working in Photoshop without any problems...Thanks!