Bug Reports

Hi, I just recently purchased a Hasselblad 907x CFV 100c and loving the in-camera crop feature, especially the 65:24 ratio (mimicking X-Pan's). However, it has come to my attention that Lightroom Classic does not automatically apply the in-camera crop to the raw files (3FR format).   My understanding is that for Hasselblad X2D, the in-camera crop is automatically applied to the 3FR files in Lightroom. If it is a bug, then can Adobe please fix it?   If not, please add the support for in-camera crop for Hasselblad 907X CFV100C files.   Thanks, Norman   [Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules. A ‘bug’ is not just another word for any problem with software!]

Just got off a 1 hour call with tech support and they verified my bug on both mac & windows.   After the update 13.3 the yellow badge no longer shows up for "Likes" on either the individual photo or on the collection name for sync'd collections.  If someone whos selecting pictures via the shared link to a sync'd collection clicked a heart on a picture, using the previous version, a small yellow badge would appear on the picture in Lightroom Classic as well as a badge would appear next to the collection name in the left hand column.  This No Longer Works after the update for "Likes".  It does still work for Comments though.   This is an issue because "Likes" allow us to sort by our clients selections in order to know which pictures they've chosen.  Comments require typing something and clicking "Submit" which seems to work, but "Likes" only require clicking on the heart.  Both actions used to cause the Yellow Badge to appear.  Now it only appe

LR treats location fields (Sublocation, City, Country, etc.) that have been "suggested" by Address Lookup inconsistently -- while some parts of LR recognize the suggested values, other parts behave as if the fields are empty.  Smart collections, filters, and exporting of metadata recognize the suggestions. But Print > Page > Photo  Info, Save Metadata To File, file renaming templates, the Book module's Photo Text, and the SDK's photo:getFormattedMetadata() behave as if the location fields were empty.These are bugs -- there's no sensible design rationale for the inconsistencies. All parts of LR should recognize the suggested address fields. The bugs were reported years ago in other topics but were buried in long threads:https://feedback.photoshop.com/photoshop_family/topics/lightroom_improve_control_over_reverse_geocod...https://feedback.photoshop.com/photoshop_family/topics/sdk_inconsistent_handling_of_uncommitted_loca...The longstanding working around is to "commi

Ok first the setup:I start with LR Classic (in a shared album, smart-previews in the cloud) and send a RAW to Photoshop, after I'm done with my edit the saved tiff gets added my LR classic and automatically added to the shared album as a smart-preview too (thats nice).In LR Mobile I can see my edit in develop mode and in the preview, so far so good.Then later I continue working on that tiff (sending it to Photoshop via LR Classic again, so LR gets the update). And it does get the update, LR classic shows the changes I have done.Back to mobile, here I get the old version in develop mode, the preview thumbnail gets updated to the new version, if I open the tiff smart-preview into activity, rating, or info view, I see the updated version as it should be.But if I get into develop mode in LR mobile, it shows the current version (as it should be), but only for a second and then switches to the version that was first shared when I saved the first edit (that is now outdated and not what LR cla

For the past few weeks, LrC is crashing when I attempt to create a mask, any mask.  I have not found a workaround. I am using Version 12.3 on a Mac Studio, which is also up to date.

photo:getDevelopSettings() sometimes returns nil for Temperature and Tint.   Tested in LR 12.2 and 10.4 on Mac OS 12.6.1. To reproduce:   1. Download and unzip this catalog folder ("Temperature"): https://www.dropbox.com/s/z527z9to4ie46vx/Temperature.2023.03.02.zip?dl=0   2. Copy the file "get-temperature.lua" from the catalog folder to the User Scripts folder.   3. Open the Temperature catalog.   4. Select the one photo and go to Develop.   5. Go to Library and do Scripts > get-temperature. Observe the temperature and tint are correctly displayed:   6. Do Quick Develop > Reset All.   7. Do Scripts > get-temperature and observe that temperature and tint are incorrectly nil:    

The Filter Collections box in the Library Collections panel  gets confused when switching its filtering between All and Synced Collections.   To reproduce in LR 13.5.1 / Mac OS 14.6.1 (see the attached screen recording):   1. Download and open this tiny catalog: https://www.dropbox.com/scl/fi/47a2qcjulogkdc3b0cefh/collections-filter.2024-09-22.zip?rlkey=5alhwb2f5r0fchbury420619e&dl=0   2. In the Library Collections panel Filter Collections box, type "Test". Observe that all three collections are displayed (correct).   3. Change the magnifying-glass drop-down from All to Synced Collections. Observe that no collections are displayed (correct).   4. Clear the text in the Filter Collections box. Observe that no collections are displayed (correct).   5. Change the magnifying-glass drop-down to All. Observe that all three collections are displayed (correct).   6. Change the magnifying-glass drop-down to Synced Collections. Observe that al

For many versions of  Lightroom, the sync settings keyboard shortcut (ctrl-shift-S) will randomly change exporting images. This first started many versions ago and is still happening in Version 8.3. I'm running Windows 10 Pro. Trashing preferences temporarily fixes the issue, but of course, I then have to spend hours/days rebuilding all of my preferences since Adobe still doesn't have a preferences backup.  Adobe Support has tried to fix this on numerous occasions but has yet to solve it. 

Since updating to version 13 ...   The entire LR interface will disappear for a second or two from my secondary screen if it's displaying the thumbnail grid while marking images with filters set. For example, filters are set to only show unflagged images. I mark an image rejected, it disappears from view, the grid changes and this causes the interface to disappear. It does not happen every time ... but at least half the time. Occurs, regardless of the type of filter enabled and in both Loupe and Develop modules. The issue does not hinder my workflow, but it is very annoying.    And possilby related ... the main LR window on my primary display automatically pushes the Mac OS window header out of view to where I can only see a few pixels of it running across the top of my screen. I am unable to access the close, minimize and expand buttons or move the window around. The perfect click-drag will pull it down, but it snaps right back.    I am using a fully spec'd Ma

1. Version 13.5.1, Camera Raw 16.5, Build [202408271704-d15d09cd] 2. MacOS 14.6.1 3: Have main monitor in Fullscreen with Menu Bar mode. Secondary display is active, in Full Screen. On primary display, change from Library to Develop module. The main library window will jump from the primary display onto the secondary display. This also happens when switching the other way around, or when changing from Loupe to Grid, for example. Sometimes I have a third display attached, and when I do the main window sometimes jumps to the tirtiary display instead of the secondary. 4. Basically, display handling has gone bonkers. I can no longer use Lightroom Classic in Fullscreen with Menu Bar mode, or the screens jump around whenever I switch views.   System info: Lightroom Classic version: 13.5.1 [ 202408271704-d15d09cd ]License: Creative CloudLanguage setting: en-USOperating system: Mac OS 14Version: 14.6.1 [23G93]Application architecture: arm64Logical processor count: 12Proce

1. Create 2 desktop spaces on macOS.2. Open Lightroom in the first space.3. Open Mission Control (press F3).4. Drag Lightroom window to the second space.5. Switch to the Lightroom on the second space.Should be: Lightroom must remain on the screen.Actual result: Lightroom changes desktop space automatically to the first one without Lightroom in it. Can't use Lightroom anymore.

Sorry Adobe,but until the release of the new profiles function you have got not solved the problem, that for some profile patterns it’s not possible to add a vignette. It's also still the same in the new major version.The bug is shown when the amount of the vignette is 0. Select another profile, like Modern 03. Try to change the amount value for vignette.A work around is to add a vignette with another working profile, change to the not working profile and change the value for the vignette. This is needed When do you want to fix the bug? Please try- reset the develop settings- select profile 'Modern 03' (with some others it's the same)- try to change in the effects the amount value for Post-Crop VignettingBest thanks,B

When in the Develop module my second monitor becomes blurry.  This happened at the time of 10.2 update. I am running iMacPro and MacOS Big Sur 11.2.3.  Interestingly, LR system info incorrectly shows I'm running MacOS 10.16.0.   iMacPro  64GB Ram Radeon Pro Vega 64 16GB LG Ultra Fine Display 27in - Secondary Monitor

As the title says:  - I choose Enhance... - The dialog loads then the preview spinner stops after about a second - LRC freezes - SSD use shoots up to 100%, it cripples the whole PC, even the Task Manager becomes non-responsive - CPU / GPU close to 0% use, SSD write fluctuates between 10-12MB up to 500MB/s, but mostly in low-tens, read speed is marginal - After several minutes (!) with my non-responsive PC I get a crash report with the below reason:       crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x0000000061239077"       PC is fairly powerful, 14-core i5 (13600k), RTX 3070 with the latest Studio Driver, 64 GB RAM. Performance profile maxed out. Outside of this issue, Lightroom runs fairly well (by Lightroom Classic standards that is...)   There seems to be no consistency on which file this is produced. I normally shoot sequences of the same scene, and one image works okay, the other one brings Lightroom

Lightroom Classic version: 13.5 [ 202408062022-6258095b ] macOS 14.6.1   When requesting an export file does not contain camera data the resulting exported file does contain these metadata. It is important to note that while the camera's EXIF space data is stripped, that information is retained and included in the resulting exported file in XMP.   Select an image choose File -> Export... to open the Export dialog Choose to 'Export to Hard Drive', make required output settings In the 'Metadata' section set 'Include' to 'All Except Camera & Camera Raw Info' and export Open the exported file using Photoshop, use File -> File Info... to view metadata Select 'Raw Data' to view  <photoshop:CameraProfiles>    Expected result is that the exported file doesn not contain any metadata relating to the camera, lens or settings used. Actual result is the file metadata does include details of camera including make, model, lens and exposure.   This example

Hallo zusammen, ich habe seit etwa sechs Monaten ein Problem mit Lightroom Classic, das mich zunehmend frustriert. Um mögliche Treiberkonflikte auszuschließen, habe ich mich vor kurzem dazu entschlossen, mein OS X komplett neu zu installieren. Problembeschreibung: Ich habe mein Betriebssystem vollständig neu installiert, indem ich die Festplatte mit dem Festplattendienstprogramm gelöscht (via USB stick installiert) und das System von Grund auf neu aufgesetzt habe. Leider musste ich feststellen, dass das Problem weiterhin besteht: Lightroom Classic stürzt direkt nach dem Start mehrfach ab (meist zwei- oder dreimal) und läuft dann eine Weile stabil, bevor es erneut abstürzt. Lightroom Classic hat Vollzugriff auf die Festplatte. An meinem iMac sind zwei zusätzliche Monitore angeschlossen, und ich arbeite in Lightroom mit zwei Monitoren. Ein weiteres Problem ist, dass der Hauptbildschirm, auf dem Lightroom gestartet wird, manchmal plötzlich wechselt und das Programm dann auf einem der and

Have had 2 issues for about a year that have not been fixed despite support calls.   Issue 1: Creating a Virtual Copy in Develop Module or Library Loupe View, while MULTIPLE images are selected, will create the virtual copy and also advance to the next image instead of keeping the new virtual copy selected. Ex if I create a virtual copy of image #80, it will create #81 as the virtual copy, but then automaatically advance to select and show image #82 in the edit window.    Issue 2: When advancing through the timeline in Develop Module using the keyboard arrow keys, if you advance too quickly the image you advance to will adopt the previous image's editing preset.    Both problems happen in multiple catalogs. You can see the screen recording below for examples of each.   

Hello,   The 13.3 version added thousands of old images that were deleted in the cloud for years. That was easy to clean but took me half a day. The main problem I have now is collection names are being switched by synchronization. Exemple to clarify :   On LrC 13.3 I have a "master collection" called "Shooting 1", inside I have a collection called "Bad" (not keepers) and another one called "Shooting one" (keepers). Same for a second shooting. So my collection tree is LrC is :   * Shooting 1     - Bad (1000)     - Shooting 1 (100) * Shooting 2     - Bad (2000)     - Shooting 2 (200)   After installation of 13.3 my tree is :   * Shooting 1     - Bad (1000)     - Shooting 2 (100) * Shooting 2     - Bad (2000)     - Shooting 1 (200)   And it doest that with my full synchronized catalog containing around 60 collections. So when showing files to customer on an iPad, the images colle

Hi Guys,and Photoshop staffI have a big problem since the new catalina 10.15.2.0 i can't use the tethered mode. Lightroom don't see my canon 5D Mark III. Could you fix the problem ? Thank you. I uste the new macbookpro 16.

In LR version 13.2, a video in a Publish Service Collection will fail to publish if the Publish Service has a post-process action installed and inserted. An attempt to publish a video will typically fail with either a This photo was not rendered or This photo is missing error message.   This has been tested with the Hard Drive Publish Service as well as the services SmugMug and jf Collection Publisher.  Post-process actions tested include Lr/Mogrify 2 and jf Metadata Wrangler.   This has also been tested with a new, "virgin" catalog and the issue persists.   It has been tested on MacOS 13.6.4; I have not tested it on Windows.   Workaround: Remove all post-process actions from the Publish Service.   Note: Unlike with the previous Assertion failed error present in 13.1, one can remove the post process action when publishing videos but reinsert the post process action when publishing still images; the mere presence of a video in a publishe

Synchronize Folder sometimes shows photos as missing when they're not. To reproduce in LR 13.0.1:   1. Download and unzip this catalog folder: https://www.dropbox.com/s/rzpzmsn1cpc3xlg/sync-bug.2023.10.27.zip?dl=0    2. Open the catalog in LR.   3. Uncheck the option Preferences > General > Treat JPEG Files Next To Raw Files As Separate Photos.   4. In the Folders panel, right-click "pics" and do Synchronize Folder.   5. Observe that the three photos in the catalog are reported as missing:   6. Click Show Missing Photos and observe that the special collection Photos Missing From Folder "pics" contains the three photos, and they are not marked as missing:   7. Right-click "pics" and do Synchronize Folder again, this time checking Show Import Dialog Before Importing, unchecking Remove Missing Photos From Catalog, and clicking Synchronize.   8. Observe that the three JPEGs in the folder are shown for import. Click Import, and they will

  The shortcuts for "Select the Spot Removal tool" and "Flag photo as a pick" have been swapped. (P&Q) The manual says "Select the Spot Removal tool" is Q and "Flag photo as a pick" is P. In Lightroom, both shortcuts are written as Q. https://helpx.adobe.com/lightroom-classic/help/keyboard-shortcuts.html Win10、Win11、Japanese version

Whenever I open the Library Grid View and hover over a photo with my mouse, a tooltip appears the metadata I selected. If I hover over another photo, there is no there is no tooltip. If I hover onver the original photo there is no tooltip. If I leave Grid View and comeback, the tooltip only appears for the first photo I select.  Tooltips in Loupe View work fine. I'm using LrC Release 13.1 macOS Sonoma 14.1.2.    Any helap would be greatly appreciated.   Thanks, Phil

Hello, I am trying to see the full file path for a photo in grid view. By itself, the full path should appear when I hover over the folder field. Actually, the full path should be displayed, but nothing is displayed. The hand appears, but no path. Hovering does not seem to work.   Thank you

The Update AI Settings command hangs indefinitely when it is applied to a photo with a Sky mask to which Generative Remove has been copied/synced, and LR must be force quitted.   To reproduce on LR 13.   1. Download this tiny catalog, unzip it, and open it in LR: https://www.dropbox.com/scl/fi/x5xa41n0lv7dwc9z6f9rh/update-ai-settings-bug.2024.06.30.zip?rlkey=h0jzd2kxe7q4ni45ydo3ar34e&dl=0    Observe that 1.jpg has a Generative Remove applied to it, and 2.jpg has a Sky mask.   2. In Library, select both photos, with 1.jpg most selected.   3. Do Sync Settings with just Remove selected.   4. Select 2.jpg and do Photo > Develop Settings > Update AI Settings.  Observe the Updating AI Settings progress window opens but hangs indefinitely:   Clicking Stop has no effect, and you have to Force Quit LR.   5. The same symptoms occur if you invoke the SDK's photo:updateAISettings() on the photo.