Lightroom Classic

So in the import dialog I have set to import using Camera settings. My camera s set to its default standard picture control. After import, all the images have setting altered in the develop module. like exposre is set to +.33 contrast +9 highlights to -21 and these are greayed value to using the reset button restores to these values. Changing profile does not change any of these values so they are definely set at import.

Bug DescriptionSummaryCatalog conversion from Lightroom Classic v14 to v15 consistently fails when the keyword hierarchy contains keywords starting with Scandinavian characters (ä, ö).If all such keywords are removed in v14 prior to conversion, the catalog converts successfully to v15.This strongly indicates a Unicode normalization or unique-index conflict during schema migration.Environment Lightroom Classic v14 (latest build) Lightroom Classic v15 (latest build) Windows 11 NTFS file system Catalog size: ~2.2 GB ~162,000 images Large hierarchical keyword structure Face recognition enabled Exact Error MessageDuring conversion:"Lightroom encountered problems when trying to update the format of the catalog file and cannot use this catalog in this version of Lightroom."No error code is provided.Observed Behavior The v14 catalog works perfectly. Integrity test and Optimize report no issues. All backups behave identically. Conversion to v15 always fails. Removing keywo

‘compare’ has a lock, which(unlocked) allows independent movement of each image.  Is there a shortcut key to toggle to lock on/off?

Hi everyone,I’ve been experiencing an ongoing issue with Adobe Lightroom Classic, currently on version 15.2. This problem has been happening for the last three updates, not just this latest one.After importing RAW files, the thumbnails do not appear in the Library module. The folder and total file count display correctly, but the preview area remains blank.The only workaround that consistently works is fully restarting Lightroom. Once I relaunch the program, all thumbnails appear normally.System details: Lightroom Classic version: 15.2 Computer: Apple M3 Pro Memory: 18GB RAM GPU acceleration: Set to Auto File type: RAW “Generate previews in parallel”: Enabled Storage: [internal SSD or external drive] This happens every time after import. Restarting fixes it temporarily, but having to do that after every import is not practical.Has anyone else experienced this over the last few updates?Is this a known issue with Apple Silicon machines?Is there a more permanent solution besid

After upgrading to v15.2, the Library Filters cannot be enabled. Clicking the Library menu ‘Enable Filters’ will just give Library Filters Off each time is it clicked. The check mark remains on the Enable Filters menu. Using the hotkey Ctrl-L  does not work either, just keep saying Library Filters Off. No way to enable the Library Filters. I have also restarted my Windows 11, and still cannot enable Library Filters.

Hi,I am unable to use denoiser on my Mac with M1. When I click denoise, I get progress bar which disappears after a while and then denoise is unticked. After that denoise instantly untick when I try to tick it. No usefull data is provided by CMD output of the lightroom. Systeminfo:Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: en-GBOperating system: Mac OS 26Version: 26.3.0 [25D125]Application architecture: arm64Logical processor count: 8Processor speed: NASqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171Power Source: Plugged In, 36%, ChargingBuilt-in memory: 16 384,0 MBDedicated GPU memory used by Lightroom: 7 365,1MB / 12 124,1MB (60%)Real memory available to Lightroom: 16 384,0 MBReal memory used by Lightroom: 496,1 MB (3,0%)Virtual memory used by Lightroom: 428 609,6 MBMemory cache size: 344,7MBInternal Camera Raw version: 18.2 [ 2482 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2Camera Raw virtual

LightRoom Classic 15.2 build: 202602111402-ec4112e8Only this release has a fast memory leak in the graphics card memory (Nvidia GeForce RTX 4060 Ti 16GB).  It  uses up almost all the memory just exporting 8 files to Tif to be edited in PTGUI Pro that also uses graphics memory and crashes repeatedly until exiting LRC, and that fixes the problem.However it is not efficient to have to close LR every time I export files to either Photoshop or PTgui Pro.Lightroom Classic 15.2build: 202602111402-ec4112e8MS Win 11 Prov: 10.0.26200 Build 26200x-64 based PCASUS motherboard Proart z790-creator wifi96GB memoryGraphics: Nvidia GeForce RTX 4060 Ti 16GBC: drive has 495 GB free.Lightroom database and photo collection on 2 other drives has always run smoothly.Kind regards from Hans

Issue: The Point Color functionality has stopped working post upgrade.Steps to reproduce: Mask an area of the image, then go to Point Color under the mask adjustment section, click the dropper icon and then move the cursor to the image. At that point the dropper icon vanishes (as soon as the cursor moves over the image). [I can’t select any colour/area within the mask.I can see previous colours I have selected prior to the upgrade within the Point Color settings and can manipulate them.Expected result: when clicking the dropper icon, I should be able to move to my mask and select a colour to then manipulate. The dropper icon should still visible when moving my cursor across the image. Camera model: Sony FE 24-70 GMIISystem info:Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11Version: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.8GHzSqLite Versi

Ich nutze die neuste Version von Lightroom Classic und musste mir eine neue Bibliothek anlegen.Beim Importieren der Nikon NEF-Dateien mit XMP-Dateien musste ich feststellen, dass in der neuen Bibliothek die dazumal (ab 2022) getätigte Bildbearbeitung inkl. Bewertung nicht übernommen wurde.Auch ein nachträgliches Einlesen der Metadaten über (Metadaten / Metadaten aus Datei lesen) hat nicht weitergeholfen.Ich wäre froh, wenn man dieses Problem lösen könnte. Ansonsten habe ich seit 2022 all meine Bildbearbeitungen und Bewertungen verloren.

So this is still an error I experience at random times when re-ordering a small (10-12) batch of photos within a collection. Lightroom tells me something to the effect of not being able to move photos on disk or that are already in the collection (I closed the warning too quickly to be able to say verbatim). This is a glitch I’ve encountered in many versions of LR Classic over the years. I think I have 4 closed threads on the topic already.Anyone else?   Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.4GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171CPU Utilisation: 2.0%Power Source: Plugged InBuilt-in memory: 65292.0 MBDedicated GPU memory used by Lightroom: 203.7MB / 15995.0MB (1%)Real memory available to Lightroom: 65292.0 MBReal memory used by Lightroom: 1364

Still randomly receiving error messages when re-ordering a small batch of photos within a collection. LR tells me that it can’t (paraphrasing) move photos from disk in a collection...This has been an error I’ve encountered for many different versions of LR Classic over the years and have posted several times about it already.   Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.4GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171CPU Utilisation: 2.0%Power Source: Plugged InBuilt-in memory: 65292.0 MBDedicated GPU memory used by Lightroom: 203.7MB / 15995.0MB (1%)Real memory available to Lightroom: 65292.0 MBReal memory used by Lightroom: 1364.7 MB (2.0%)Virtual memory used by Lightroom: 1633.4 MBGDI objects count: 787USER objects count: 2771Process handles count: 3129M

Since the latest versions of Lightroom Classic and MacOS the masking of people always shows “No people found” – even on photos where it was working before. Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: en-DEOperating system: Mac OS 26Version: 26.3.0 [25D125]Application architecture: x64Logical processor count: 24Processor speed: 3,3GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171Built-in memory: 196.608,0 MBDedicated GPU memory used by Lightroom: 4.743,3MB / 16.368,0MB (28%)Real memory available to Lightroom: 196.608,0 MBReal memory used by Lightroom: 3.040,3 MB (1,5%)Virtual memory used by Lightroom: 55.303,7 MBMemory cache size: 62,7MBInternal Camera Raw version: 18.2 [ 2482 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 631MB / 98303MB (0%)Camera Raw real memory: 644MB / 196608MB (0%)Cache1: Final1- RAM:519,0MB, VRAM:1.818,0MB, ALP05331.ARWNT- RAM:519,0MB, VRAM

Invoking the Library Filter bar’s Restore Default Presets creates duplicates of the built-in filter presets.   To reproduce in LR 15.2 / Mac OS 26.2: 1. Set the option Preferences > Presets > Store Presets With This Catalog. 2. Open the attached catalog “filter-presets-bug”. 3. In the Library Filter bar, click the drop-down menu and do Restore Default Presets. Observe that the built-in presets Default Columns, Filters Off, and Location Columns have been duplicated.  Examining those presets’ .lrtemplate files, the contents of the duplicates are identical. Before and after of the drop-down menu: 

Hallo Forum und liebe Grüße, ich benötige nach langer Zeit eure Unterstützung. Ich bin jüngst von der A7IV auf die A7V umgestiegen. Ich nutze LrC über die Creative Cloud von Sony in der neuesten Version (V15.2). Meine Fotos erstelle ich als RAW-Dateien, in der V-er als RAW-komprimiert. Die Kamera ist auf die Version 1.01 upgated. Beim Einlesen in LrC erhalte ich die Meldung "Die Datei wird entweder nicht unterstützt oder ist beschädigt." Smartvorschauen können ebenfalls nicht erstellt werden. Zuerst dachte ich, die RAW-Version würde dies verursachen. Blöd das Ganze, weil ich morgen nach London will und die Kamera soll dort zum Einsatz kommen. Nun sieht es so aus, als müsse ich ohne die Kamera reisen, weil es keinen Sinn macht. Oder ich fotografiere in jpg. Hat jemand eine Ahnung, was der Grund sein kann?Beste Grüße, Uwe

I’m using macbook pro, Sequoia 15.3.1. I'm seeing many bugs since the LrC 15.2 release. This is one of them: when I set the profile in Print module, and then move to say, develop, and back to Print the profile is no longer selected (none is.)Another bug, may or may not be related, is that I can’t turn off mouse-hovering over History states showing the change. I have this unselected in preferences, reset preferences (very painful loss), but problem remains.

Blur toepassen met een model loopt niet lekker. Het model wordt niet herkent als de persoon die de focus moet krijgen maar objecten voor haar krijgen die. Alles wat zich voor het model bevindt is loei scherp terwijl het model de blur ontvangt. Ga je dan met de focus en blur button corrigeren dan is de verwerktijd echt heel lang en veranderd de muis keer op keer op een zandloper en kan je minuten lang niks doen, vaak omdat je een kleine correctie uitvoert. In een aantal gevallen ga je met de cursor over het gebied om iets scherp te maken of omgekeerd en dan hangrt de laptop (i9, 64GB RAM) en gebeurd er niks maar wordt er wel een item aan de geschiedenis toegevoegd. Kortom: blur zit VOL BUGS, IS SUPER TRAAG en verdient jullie aandacht om het wel werkend te krijgen. Met photoshop en layers kan het allemaal wel en Lightroom Classic blijft gewoon achteraan de lijst hangen voor updates. 

So, I have used AI masking to detect the clothes on a subject, and I am using Point Color to change some of the colors on those clothes. I want to turn up the saturation on the green spots on a military suit.   Now, as a test, just to make sure the change is noticeable, I turned the hue all the way to the left, basically the military green is now cherry red. This is only to make sure I am not going blind and that I have actually found a bug.I am NOT using global point color because I have tested global point color with the military green and if I am using global point color then half the image becomes red. When I am using just the chothes mask then only the green spots become red.   If I then export as JPG then the point color is fully ignored. If I export as PNG things behave as expected (with minor color differences)I also tested this with saturation. I turned the saturation of the military green to 0 in the point color, making it gray, exported as JPG, camo spots are green

This post applies to Camera Raw and Lightroom Classic.   Dust Removal is no longer in Early Access status and can be found in the Remove edit panel for Camera Raw & Lightroom Classic. Dust Removal helps with removing distracting spots on an image that may be caused by dust on a camera's sensor.   Once enabled, your image will be scanned, and any detected dust spots will be automatically removed using Content-Aware Remove. For refinement, you can select one or multiple spots to delete or refresh. Batch removal is also supported; simply select the "Dust" checkbox under "Remove" in the copy settings dialog.Please note that scanned negatives are not in the scope of this feature at this time.    Dust spots on scans tend to be located in the focal plane, with the negative and very sharp, while sensor dust is typically positioned out of the focal plane and therefore not in focus. Scanned negative dust typically appears as white spots on a darker backgro

Running latest LRC on Windows 11 laptop.  I don’t sync from LR, which I rarely use, and haven’t synced anything for a long time from LR mobile. (LRmobile photos are synced into a “From LR mobile” folder in Collections, none of which shows any obvious issue or activity.)  I’m not aware of other sync activity, Once or twice before, when sync has gotten stuck on a photo, I remember being able to fix this in the Preferences sync settings.  There’s nothing there now showing any sync activity at all, so nothing to delete. No help or search suggestions are useful; they involve different kinds of sync problems and mostly give only Apple and/or LR instructions.)  I’d like to get rid of the error message that appears every time I close LRC, and eventually I’ll have other mobile photos to add to some collection.  If any more info is needed, please let me know.  I’m sure I’m missing something obvious and easy.Many thanks.   

Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Enterprise EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 32Processor speed: 2.9GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171CPU Utilisation: 0.0%Power Source: Plugged InBuilt-in memory: 65241.4 MBDedicated GPU memory used by Lightroom: 1969.2MB / 12110.0MB (16%)Real memory available to Lightroom: 65241.4 MBReal memory used by Lightroom: 7285.3 MB (11.1%)Virtual memory used by Lightroom: 10360.7 MBGDI objects count: 1088USER objects count: 3663Process handles count: 8272Memory cache size: 0.0MBInternal Camera Raw version: 18.2 [ 2482 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 89MB / 32620MB (0%)Camera Raw real memory: 98MB / 65241MB (0%)Cache1: NT- RAM:0.0MB, VRAM:0.0MB, Combined:0.0MBCache2: m:0.0MB, n:0.0MBU-main: 194.0MB