Lightroom Classic

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

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

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

There is a one-way sync issue between Lightroom (cloud) and Lightroom Classic. Sync works correctly from Classic → Cloud:If I create a collection in Lightroom Classic and enable sync, it appears in Lightroom (cloud) with all photos. However, Cloud → Classic does not work:If I create an album in Lightroom (cloud) and upload photos, the album and its photos do not appear in Lightroom Classic in the Collections list. Both apps are logged into the same Adobe account. Only one catalog is syncing in Classic. I have already tried pausing/resuming sync and restarting Classic.System info:macOS Tahoe 26.3Lightroom 9.2Lightroom Classic 15.2

I’ve had this problem for awhile now and haven’t been able to find a solution.  On the import tab when attempting to import pictures it takes Lightroom classic forever to generate the thumbnails. I’m not talking about the previews that get built based on my choice during the import. I talking about the grid view where you can select which files to actually import.  I just tried on a sample of 280 pictures and it took the better part of 3 or 4 minutes to generate the thumbnails. Which is about as long as it takes to do the actual import AND generate 1:1 previews…  I’m shooting primarily a fujifilm XT5 with and only shoot .RAFLightroom version 13-3 (but has been happening for the better part of the last 2 years) I’ve got a very good homebuilt computer Intel Core i7-13700k (liquid cooled)RTX 4070 (GPU acceleration turned on)64 gigs of RAMHarddrive in question is a 30% full M.2 NVME SSD I previously bought a high end card reader and usb 3.0 cabling hoping this would help. Which is doesn’t.

When I try to import photos from my iPhone 14 Max to Lightroom Classic, it is always SUPER SLOW and ow it won’t download all of the,. Currently, I’m trying to import all 1633 photos but am only able to get 776 and then it just stops. I have tried again and again. Not sure what to do. 

ProductAdobe Lightroom ClassicVersion: 15.2OS: Windows 11Camera RAW Format: Canon CR3GPU: NVIDIA GeForce RTX 3050 Laptop GPU (4GB)Graphics Processor Setting: Custom GPU for image processing: Enabled GPU for export: Enabled GPU for preview generation: On Full graphics acceleration enabled  Summary When “Use Smart Previews instead of Originals for image editing” is enabled, exposure adjustments made before the full-resolution original is loaded are reverted once the original file loads (triggered by zooming to 100% or any other zoom).Both the Exposure slider value and the visual rendering reset to their previous state.This issue is 100% reproducible under the configuration described above. Expected Behavior Develop adjustments applied while editing via Smart Previews should persist. Switching from Smart Preview to the full-resolution RAW should not override committed develop parameters. Slider state and render output should remain consistent across rendering pipeline transition

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. 

Is there any downside to applying “remove chromatic aberrations" to all files? Normally only certain images show chromatic aberration, such as wide-angle images of buildings or trees against a sky.Is there any reason not to simply apply the correction to an entire folder, even though many of the images don’t show any aberration? Looking at the files in Lightroom Classic I can't see any effect on those without any chromatic aberration.I am working on a project involving thousands of 20-year-old canon files. Back then, both lenses and sensors produced more chromatic aberration than they do today.Any thoughts?

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.

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

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

Ich verwalte in LR Classic eine umfangreiche Stichwortliste.Immer wieder passiert es, dass ein Stichwort in einer anderen Gruppe, oft in der obersten Ebene vergeben werden, ohne dass ich sie dort eingetragen hätte.Hier ein Beispiel:Ich habe eine Gruppe "Familie" erstellt, in der verschiedene Namen als Gruppe der nächsten Ebene von mir angelegt wurden.  Dann erscheint an anderer Stelle entweder noch einmal unter der obersten Ebene die Gruppe "Familie" mit einer Untergruppe mit einem Namen und einer geringen Anzahl von Bildern, die ich dort nie hinzugefügt habe.Hat jemand eine Idee, wie das zustande kommen kann?Und wichtig wäre mir eine Lösung, wie ich die Eintragungen, die in einer nicht gewollten Gruppe auftauchen, der richtigen Person in der richtigen Gruppe zugeordnet werden können.Bisher habe ich tausende Bilder nacheinander markiert und geprüft, ob ein Bild in der falschern Gruppe auftaucht. Dann habe ich das Bild in der falschen Stichwortgruppe entfernt und der richtigen zuge

Since LR Classic 15.2, toggle filter in grid view is not working anymore, neither by Cmd+L keyboard shortcut nor by menu Library > Enable Filters.When activating any library filter by choosing any setting in the filter bar above grid view (for example by attribute pick flag) and then pressing Cmd+L, the library filter is deactivated for the active grid. In the menu Library > Enable Filters, the check mark is still visible left to “Enable Filters” and the filter bar above library grid view is still visible but no filter is actually applied.Pressing Cmd+L again, doesn’t do anything, clicking on “Enable Filters” doesn’t do anything either. 

Greetings!I updated LR Classic to 15.2 a few days ago and am unable to import “new” panoramic photos that I create in a new subfolder within the folder structure. Additionally, I started a new batch/project that I imported after the upgrade. To start my project in LR, I first import the folder(s) and files and then start my editing tasks.My workflow is to choose my series of photos in LR with which I want to create a panoramic photo in PS. I then pass them to PS using LR: Edit In> Merge to Panorama in Photoshop. The files are passed to PS and merged/edited/flattened to my satisfaction. I save the panorama in PS, but within the folder structure I create a new subfolder titled “Panoramas” with the very first panorama that I create for this new batch of photos/project in the PS save image dialogue box. I then create additional panoramic photos as I wish and store them in this Panoramas subfolder. This is the workflow that I’ve been using for years.When I return to Lightroom, this time,

Tried everything as I really like these presets they are working on the app on my Mac but when I edit on my phone the app is glitchy and the auto + retro filters will not apply to any of my photos 

Recently I bought a Mac Mini to be able to work on Adobe applications. I have an external SSD that I used on my old MacBook M1. I uninstalled the Adobe applications on the SSD. Then, I downloaded Creative Cloud on my Mini, but when selecting the installation path of my SSD in Creative Cloud, for some reason Creative Cloud continues to install its apps on my Mac's internal storage.Yes, my SSD is in APFS format

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