Questions
Recently active
the don't show either at the library or any other place just the gray box, I already tried deleting the damage preview.s.lrdata but the problem keeps happening. Can you help me please?
I am unable to export my catalog from my travel laptop. It hangs partway through. I’ve tried moving the location to a different place on the HD and reimporting. I’ve tried exporting to a variety of places, both internal and external. I’ve tried optimizing the catalog. I’ve tried quitting and restarting LR classic. Configuration: 2026 MacBook Pro running Tahoe
I have been trying to resolve an issue with several Lightroom 2 TB redemption codes through Adobe Support since July 2026. Despite multiple support cases and escalations, there is still no working solution.The problem itself is actually quite simple:I had an older Lightroom 2 TB redemption code, which I redeemed first. This activated a Lightroom subscription.I then purchased two additional Lightroom 2 TB redemption codes. Naturally, I expected these codes to extend the duration of my existing Lightroom subscription.Instead, the two new codes created a second, separate Lightroom subscription with a two-year term.So I now have two Lightroom 2 TB subscriptions running in parallel, even though all I wanted to do was extend the duration of my existing subscription.My specific question to the community, and especially to Adobe, is:How can the subscription periods from the two newer redemption codes be combined with the Lightroom subscription activated by the older code, so that I end up with
Se cierra más o menos a los 50 segundos de abrirlo. He probado las soluciones que se indican para este error en esta web de Abobe, pero sigue cerrándose. Lo he desistalado y reinstalado, pero sigue con el mismo problema.
I have been unable to use the AI Masks for about a month. When I click on one of the icons, it blinks like it is making the mask but then does not. Has anyone had this issue and figured out a solution?Thanks!Lightroom Classic version: 15.6 [ 202609251514-f839cde9 ]License: Creative CloudLanguage setting: en-USOperating system: Mac OS 26Version: 26.6.2 [25G83]Application architecture: arm64Logical processor count: 8Processor speed: NASqLite Version: 3.45.1Adobe GSDK Version: 1.4.0.213Power Source: Plugged In, 80%Built-in memory: 24,576.0 MBDedicated GPU memory used by Lightroom: 5,312.7MB / 18,186.2MB (29%)Real memory available to Lightroom: 24,576.0 MBReal memory used by Lightroom: 1,976.5 MB (8.0%)Virtual memory used by Lightroom: 442,407.6 MBMemory cache size: 670.5MBInternal Camera Raw version: 18.7 [ 2743 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2Camera Raw virtual memory: 1591MB / 12287MB (12%)Camera Raw real memory: 1657MB / 24576MB (6%)Cache1:
I’m experiencing a recurring issue in Lightroom Classic where photos temporarily disappear from filtered results and Develop loses the selected photo.My normal workflow is to cull and edit using star ratings and the star-rating filter. For example, I have a photo that is definitely rated 5 stars and edited. When I filter to show my rated/5-star images, Lightroom sometimes says there are no photos matching the filter, even though the image is still in the catalog and still has the 5-star rating.If I close Lightroom Classic and reopen it, the missing photo reappears in the catalog and shows the correct 5-star rating again.I’m also seeing a second issue in the Develop module: I can select a photo normally, but when I click a preset or try to make an adjustment, Lightroom will suddenly switch to “No photo selected.” Restarting Lightroom may temporarily resolve this as well.I have already tested turning the GPU off, but the issue has still occurred.This is especially disruptive because I ph
When I open Lightroom, I only see gray boxes in the Library, and my thumbnails don't appear. I have the same problem when I try to import photos. I can see the photos in the Develop module, though. I've already adjusted the color profile, but it didn't help.
In the Lightroom Classic Develop module, when using the HSL panel (and similar ones), I suggest using the right mouse button (context menu) to switch between Hue, Saturation, and Luminance modes, rather than constantly moving the mouse back and forth every time you need to change modes (which happens very often). Locked by moderator because reposting in feature requests (while this post was moved there) resulted in a double post.
Durch das nicht abschaltbare Raw-Details beim KI-Entrauschen, was normalerweise einen super Job macht, werden Fotos von dunklen Adlern mit leuchtend gelben Schnäbeln inhaltlich verändert, der gelbe Schabel wird mit dem Kopf mal zu einer rosa, mal zu einer grünlichen Masse umgeformt, was leider nicht nur den Schnabel, sondern auch das umgebende Gefieder betrifft, da alles irgendwie verschmolzen wird. Beim manuellen Entrauschen tritt dies nicht auf, allerdings bekommt man die Bilder dann nicht so schön detailliert wie mit dem KI-Entrauschen inkl. Raw-Details. Da ich viele Schreiadler fotografiere, betrifft mich diese Einschränkung leider besonders, schade um die sonst sehr schöne Funktion
Hello,Reflection Removal (Remove > Distraction Removal > Reflections) produces a heavily corrupted image on my Intel iMac. The result is a saturated pink/magenta image with yellow, cyan and black artifacts. The image is unusable at any Amount value. A screenshot is attached.SystemLightroom Classic 15.6, and the same result in Camera Raw (Photoshop) iMac Retina 5K, 27-inch, 2019 CPU: 3.7 GHz 6-core Intel Core i5 GPU: AMD Radeon Pro 580X 8 GB RAM: 64 GB macOS Sequoia 15.8.1 (this Mac is not supported by macOS Tahoe)Test fileRaw DNG, Nikon Z camera, NIKKOR Z 24-70mm f/4 S at 70 mm, 1/80 s, f/4, ISO 640What I tried, without any change in the resultSetting Use Graphics Processor to Custom, with GPU for display only Setting Use Graphics Processor to Off in Lightroom Classic Disabling the GPU in Camera Raw preferences Restarting the applications Reapplying the effect from a clean stateOther AI features, like noise reduction, are not affected .Expected result: Reflections removed from th
Ich habe ein ungewöhnliches Problem in Lightroom Classic.Ich erstelle einen neuen Katalog und importiere einen Ordner mit Bildern. Im Importfenster werden alle Fotos korrekt angezeigt, und ich kann die Vorschaubilder ganz normal sehen.Sobald ich jedoch auf „Importieren“ klicke, verschwinden die Vorschaubilder in der Bibliotheksansicht. An ihrer Stelle werden nur noch graue Kästchen angezeigt.Die Bilder selbst sind jedoch vorhanden:Die Metadaten werden korrekt angezeigt. Im Entwickeln-Modul werden die Fotos normal angezeigt und können problemlos bearbeitet werden. Die Dateien befinden sich weiterhin am richtigen Speicherort und sind auch im Finder sichtbar.Folgende Punkte habe ich bereits überprüft:Es sind keine Filter aktiv. Es gibt keine Dubletten. Der Ordner ist klein und enthält nur wenige Bilder. Das Problem tritt sofort nach dem Import auf.Es scheint, als würden die Bilder korrekt importiert, jedoch werden die Vorschaubilder in der Bibliotheks-Rasteransicht nicht angezeigt.Können
Using an m1 Max, didn't have this issue prior to the latest update to version 9.4 Denoise introduces banding that continues on through to exported files. Not an issue prior to the update.
I was changing around some things within Lightroom files last week and thought everything was done correctly. But today I saw that there is a wrong connection. In am working on a Mac. In finder, my folder structure is this: 2026 → 2026.08 → other folders. But in Lightroom, there are two 2026.08 folder. One is within the 2026 parent folder, containing other folders. But there is also a separate 2026.08 folder, which contains only one other folder (2026.08.08 - Ameland - sunset walk). In finder, this is all under the same 2026 → 2026.08 folder. There is another problem. When I click on show or hide a parent folder, I am getting this error message: Database "/Volumes/HD Frouke/Lightroom backup/2026-10-01 1214/Lightroom Catalog/Lightroom Catalog backup 01-10.26 1.lrcat": UNIQUE constraint failed: AgLibraryFolder.rootFolder, AgLibraryFolder.pathFromRootsql: UPDATE AgLibraryFolder SET rootFolder = ?,pathFromRoot = ? WHERE id_local = ?; (error code 2067)I have tried many different things in
He copiado el catáolgo a otro disco duro junto con la carpeta de imágenes. Cambié el nombre y no me reconoce el catálogo. He abierto desde una copia de seguridad, me abre el catálogo, pero no se visualizan las imágenes antiguas, sólo las que acabo de importar. necesito ayuda urgente por favor. Gracias
I created folders and albums in LR and now have started using LRC, but Lrc doesn't automatically create the same structure as Collection Sets/Collections. It'll be very annoying if I have to do it manually as as far as I can see Collection Sets = Folders and Collections = Albums. Shouldn't be rocket science.... At the moment, every single folder from Lightroom (cloud) is just listed in a single list under "From Lightroom"... great, thanks! Also would be good if this was automatically maintained when I sync the two, if it doesn't already.
Hi everyone,I'm having a persistent issue in Lightroom where all files appear blank/grayed out during import, and clicking "Import" does nothing. The issue: Happens with all file types and folders from all different cameras/drives. What I've tried: Completely uninstalled/reinstalled Lightroom, tested multiple different versions, and tried every troubleshooting fix found online. Nothing has worked so far. Does anyone know how to fix this? Thanks!
I have more external USB drives than USB sockets on my PC. This requires me to occasionally swap the main USB drive holding my RAW files to another socket or to reconnect after it has been removed. Lightroom often doesn’t recognize that it is the same drive and allocates a new drive letter, consequently it says files not found and I have to re-sync all of the files which loses the history of which files have been edited. Could you have Lightroom recognize the drive and allocate it the original drive letter and retain it even after removal.
MacBook Pro M3 Pro and MacBook Pro M5 Max MacOS 27.0.1 aka Golden Gate I have a catalog i made for test purposes this June containing 109 Nikon Z8 non compressed photos.When i tick the Denoise box runtime is 3 seconds, great!However, if i make a new catalog with the same 109 photos then runtime is 11 seconds :-(I did many test and catalogs and same happen, denoise time is 11 sec on the M5 Max and 17 sec on the M3 Pro what is not surprising.It seems to me that the catalog who does denoise in 3 seconds have the photos only in a collection as but no photos are shown on disk. See the attached screenshotNow i am a bit confused about why i can edit photos if the original is not on the disk but in a collection ?Exporting the edited photo i get a warning window saying, but export works perfectly fineSo from what i understand in this case i work with smart previews instead of the original file.What i am wondering why is the Denoise time for Smart Preview so much faster; 3 seconds instead of 11
Hi guys,I am a wedding photographer and web developer quite okay with colour spaces. So here is my problem. Adobe Lightroom Classic is using Adobe Colour profile for my images but when I export the images the image looks totally different. Before you think I am a newbi here is what I have done so far. 1. I understand colour space differences. I also used the soft proofing option within LR with sRGB profile to see how it will look. Soft proofing and develop module gives me the same look, but after exporting is totally oversaturated. 2. I am using my Dell Ultrasharp Premier Colour monitor calibrated to perfection and I am using the monitor in sRGB mode. 3. The exported image is oversaturated compared to LR on ANY DEVICEs. So I export the image, and that images looks exactly the same oversaturated on Iphone, Ipad, Samsung phones, and laptops. 4. I have the same version of Lightroom on my laptop, and if I export it there, it does not alter the settings. I use the s
I use the fabulous autostack by time feature in LR Classic (latest version as of the date of this post). This neatens and clarifies what is included in any stacks I have made most of which are in the hundreds of raw images.However when I want to select a stack to export to other applications selecting the stack only grabs the first image and the stack must be laboriously expanded and then the firsts and last images must be selected (in windows) via the shift key. This is not so easy when navigating down several pages of thumbnails.A simple feature beneath the right click ‘stack’ option could be added to those already there to ‘Select all images in the stack’ Simplez cheersIan
AI processing is in progress for this photo. Editing is temporarily unavailable. Happened on a few photos when I tried to sync settings. Hasn’t resolved and its been over 24 hours.
Hi, I’m using macOS 12.7.6 (Monterey) and the latest Lightroom Classic isn’t supported on my system.I have an active Adobe account and I’m also a student.Could you please help me access or provide a download link for Lightroom Classic 11, which is compatible with Monterey?Thank you very much!
Lightroom Classic tether function was finally working without issue, but after latestest update (14.1.1) will no longer fire via the tether shooting panel when camera (Nikon 850) is in mirror lock-up mode. The other functions work fine, i.e., shuutter speed, aperture, ISO.. all communicate with camera and adjust, but after first click of shutter release (via tether panel) camera just locks with "PC" on LCD. OS: Win 11
ISSUE: Main thread pinned in recursive Lua cycle (AgKernel) during Library interaction. It should be reproducible with a stripped catalog and zero-byte files.---Lightroom Classic 15.5.1Camera Raw 18.5.1macOS 27.0 (though it has been occuring since macOS 15)Mac Studio (Mac13,1), Apple M1 Max, 64 GB RAMStudio Display, 5120x2880 (2560x1440 logical)Catalog: 40,748 photos, 1,133 folders---SUMMARY: Within seconds of ordinary Library interaction (scrolling the grid, switching to another app and back), Lightroom Classic's main thread enters a Lua coroutine via a run-loop source and never returns. The run loop stops servicing its Mach port, so the application stops processing events. CPU sits at exactly 100% - one core, one thread. The only recovery is quitting and relaunching. This has persisted for almost two years across fresh macOS installs, fresh Lightroom installs, and rebuilt catalogs.IMPORTANT FOR REPRODUCTION: This requires real hand interaction. Scripted activation (AppleScript “activ
One feature I still find lacking after switching from Apple Aperture is the ability to “split folders based on shooting time.”This feature splits the folder if the interval between shots exceeds a specified duration.
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.