Lightroom Classic

There is a recurring issue where the Loupe view displays an entirely incorrect image immediately following a folder import. Specifically, if a user enters the Loupe view before the initial preview fetching is complete, the view will load a cached image from a previous session - even if that image belongs to a folder that has already been removed from the catalog.While toggling between images can sometimes force the view to refresh, the incorrect preview sometimes gets “stuck”. This allows the user to browse the gallery in Loupe view and randomly see photos from long-gone folders, despite the thumbnails in the filmstrip displaying correctly. Steps to ReproducePrepare two folders containing a large number of high-resolution photos (to ensure preview generation takes a noticeable amount of time). Import the first folder into Lightroom Classic. Select any photo and press Spacebar to open it in Loupe view. Press G to return to the Grid view. Remove the first folder and its images from the L

Background: I was in the middle of restoring a Lightroom Classic catalog after a drive recovery. During the process, two folders got merged, let’s call them “June” and “July”.  Both folders exist correctly on my external drive.Current situation in Lightroom Classic 13.3:Only the June folder appears in the Folders panel It shows 1212 photos total — approximately 300 June images and 900 July images All images appear normal (no question marks or error badges), but they do have a white square that says Smart Preview.  All images have edits I need to preserve When I click "Show in Explorer" on a July image, it correctly shows the file in the July folder on disk But the metadata panel shows the June folder as the location When I try to drag July images to a different folder in LR, it says "All files selected are missing. No files can be moved."What I've already tried:Adding the July folder via Add Folder — resulted in 900 duplicate catalog entries, so I deleted the folderWhat I need:A safe w

Running on Macbook M5 Pro 2026.  MacOS 26.5.1.Fonts, including the application menu on 4K external display are not rendered correctly.  They look like they are being smoothed for a retina display.  Built-in display on the macbook looks fine.In the screenshot below, the width of the vertical lines vary depending on position.   

As the title says, While using the Remove tool, the cycle new spot fill type (or Shift + T) shortcut is not working with lightroom classic, my version is Lightroom Classic 15.3.1. Is anyone else experiencing this? I have tried resetting the preferences or holding (Shift + Alt) upon launching the program but to no avail. Any help is appreciated, thank you!

after  recent edited files they are getting lost and files cannot be found even though original file exists in LR classic  

Using the Copy Settings Subset option of modifed doesn't recognise the cropping if the image angle or aspect ratio haven't been modified. Please delete this post or merge with my later post here: https://community.adobe.com/t5/lightroom-classic-discussions/copy-settings-gt-subset-modified-ignores-crop/m-p/15501384

When applying the Color Profile “Adobe Standard” to an image in Lightroom Classic and then exporting as DNG. Then later importing the DNG back into Lightroom Classic, the Color Profile is set to “Adobe Color” instead of “Adobe Standard”.When opening in Photoshop, ACR shows “Adobe Standard” correctly. Lightroom Classic Version Number 15.3.1 Mac OS 26.5.1  Reproduction Instructions:Either use a random image, set the Color Profile to “Adobe Standard” and export as DNG. Then import the DNG back into Lightroom Classic and see it applies the “Adobe Color” profile.Alternatively, import the attached DNG file and see that the Color Profile is set to “Adobe Color”. Open it in Photoshop and see that the Color Profile is set to “Adobe Standard”.Expected Result: Lightroom Classic also applies the correct Color Profile: “Adobe Standard”.The Actual Result: Lightroom Classic applies the “Adobe Color” profile.Lightroom Classic:  ACR:  

When in Libary, move to a day with has a DJI Mavic 4 still photo .dng (114MB) the application becomes unresponsive showing the spinning colorwheel.  When Importing from the DJI media, it also imported the .jpg file.  The apps needs to be Force Quit.Loading a .dng file takes very long (~15 sec) and then after another ~15 sec it becomes unresponsive.Easiest to see experience with a second monitor, but also happens in Library single photo.The import also contained .mp4 files.  Lightroom Classic version: 15.3 [ 202604090947-8f3672ed ]Apple M4 Max - MacOS Tahoe 26.4.1Screenshot does not show the spinning color wheel but the zoom loop (in the center of the controller display)  

I applied Denoise to 115 files by selecting the files, select Autosync, the clicking the check box on Denoise.  After all files complete Denoise, I again selected the same 115 photos, select Autosync, then uncheck denoise.  The process starts and a status bar appears labeled “Removing Denoise on 115 photos”.  The status bar progresses but after a short time stops.  Checked the photos and find the first 21 have had denoise removed.  Did “Optimize Catalog...” and then restart.  Tried to denoise the remaining 94 photos. Same result as before but this time it denoised another 21 photos before hanging up.  Restart, the did the same process to remove denoise on the remaining 73.  This time it removed denoise from 18 before hanging up. LrC is unable to remove Denoise from the entire set of selected photos.   LrC 15.3, Win11 

black and white outline on my pictures in lightroom classic after update  v15.3 ->  Filmstrip 

I wanted to follow up on this topic as it's been radio silence on it for nearly 8 months since AI DeNoise was launched.  In the meantime we've not only had multiple updates by Apple to Ventura, we've also had the release of MacOS Sonoma which is rapidly approaching the release of version 14.2.   While I have pretty much left Topaz behind with the release of Adobe's DeNoise and my dissatisfaction with earlier releases of PhotoAI, I just checked it again and with their model updates its now back to being the equal of Adobe's Denoise, but it's a lot faster--it takes less than half the time to process a file on my M2 Ultra with Topaz as it does with Adobe DeNoise.  They are using the Apple Neural Engine, regardless of any bugs--and this is confirmed as I can monitor the power draw of the neural engines in the console as I process images.  DxO is also using the neural engines.  Clearly there are ways to work around the bugs, or these companies have already taken adv

I’m getting the “AI Edits Storage Error” in Lightroom Classic, and I’ve already followed all the steps listed on Adobe’s help page, but the issue is still happening.Here’s what I’ve tried so far: Confirmed there is enough free disk space Restarted Lightroom and my Mac Ensured only one instance of Lightroom is open Gave Lightroom Classic Full Disk Access and Files & Folders permissions in macOS Verified my user account has Read & Write permissions Checked that the catalog and .lrcat-data folder are accessible Not using any cleanup tools or cloud sync on the catalog while Lightroom is open Despite all this, the error continues to appear and AI edits fail to save properly.

Lightroom Classic 15.3.1 on macOS Tahoe 26.4.1, Apple M4 Max, hangs with “Not Responding” during Loupe view / quit / preview build. Full Disk Access is enabled. Fresh install and fresh catalogue tested. macOS hang report shows: “Deadlocked: 1 thread - Thread 0x2be29 AgServer” and “Blocked by Deadlock: 7 threads - AgServer”.full hang report here

It will not let me open lightroom classic. It pops up as repair and the process stops, and wont move. I’m paying for something i can’t use.

Mon processus actuel est de passer via bridge pour la previsualisation et les mots clés, puis d’effectuer un premier jet de traitements via Camera Raw.Je viens de faire des importations dans Lightroom classic et là surprise, je ne retrouve pas les modifications effectuées dans Camera Raw?Pourtant les xml et air sont bien dans le même dossier que les fichiers raw.Comment faire?Merci

in a RAW landscape photo, when I want to emphasize distance I should be able to use the Depth Range mask. I should be able to access it via the Range Masks. where one can find Luminance Mask, color mask and Depth Range. Depth Range is greyed out and not available. Using Shift D yields no response. why can it not be used? Isn't it available to LRc version 15.3.1?

Is it possible to import my PSE26 catalog to Lightroom Classic? It seems looking at the list only up to 2021 might be supported. Lightroom Classic 15.3.1 Photoshop Elements 2026 Organizer PSE26DB catalogIf it isn’t, is it likely to be added or do I need to make a decision about whether I can be bothered to start over with 50000 photos which have been tagged, faces added, albums created, dates and places all checked?

Lorsque j’indique le n°de série pour la mise à jour de LR5 soit <deleted>on me demande un n° de série précédent que je n’ai plus puisque cela fait très longtemps…Pareil pour LR6 soit <deleted>, or sur l’explication de l’installation on me dit que si on me demande le numéro précédent, il faut indiquer 0000-0000-0000-0000-0000-0000 mais rien ne marche, on paye et nous ne sommes pas libres de réinstaller nos ACHATS, merci Adobe….

Lorsque j'importe dans Lightroom Classic un fichier raw et son xmp déjà traité dans un catalogue Lightroom Classic sur un autre Mac, les modifications déjà faites n'apparaissent pas... Comment faire??? Merci

Seit ein paar wenigen Tagen erstellt LrC keine Himmel-Masken mehr. LrC scheint diesen nicht mehr zu erkennen. Vorher lief das problemlos. Die anderen Masken scheinen zu funktionieren (Ausnahme: Landschaft. Auch dort erkennt er keinen Himmel). Habt /hattet ihr das selbe Problem?Konntet ihr das lösen und wenn ja, wie?

This error message appears when I try to open LRC. The version I have is 15.3.1. I have exited LRC on my other laptop. I’ve also tried to uninstall LRC but it isn’t doing so. Any suggestions, please?