Connect with fellow editors in our Lr Classic community.
Recently active
My Lightroom Classic just updated to the latest version (13.0). When I exit, rather than the option of delaying writing XMP, it now says I should wait until it completes. The first time, I let it complete in case the delay was due to the update. I didn't time it, but it took several minutes. I went back in, and made minor edits to two images and then exited. It's been over 5 minutes, and it's only up to 14%. Why has the message changed to say you should wait? Why is it taking so long?
I even went back and looked at a JPG I exported out of Lightroom earlier this year and that image had a hefty resolution of 5000x4000. No problems there! I’m not sure what happened! help!
SUMMARY=======Importing a large image (approx. 143 MP) into Lightroom Classic crashes theapplication 100% of the time on my machine. The same crash occurs on threedifferent LrC versions, including after a full downgrade, so it does not appearto be specific to one build. Smaller images import fine, so this is asize-dependent failure in the import path.CRASH SIGNATURE (identical across 10+ occurrences)==================================================Faulting application : Lightroom.exeFaulting module : ntdll.dll (10.0.19041.7548)Exception code : 0xc0000374 (STATUS_HEAP_CORRUPTION) 0xc0000005 (ACCESS_VIOLATION) on some occurrencesException offset : 0x00000000000ff509 <-- identical every single timeWER Sig[7] : PCH_08_FROM_ntdll+0x000000000009E164Adobe crash reporter stack, top frames: [0] mems... (memset / memcpy family) [1] RtlAllocateHeap [2] RtlAllocateHeap exception = EXCEPTION_ACCESS_VIOLATIONWindows subsequently applied Fault
Lightroom Classic 12.4 / Camera Raw 15.4Just imported a dozen Fuji X-T5 raw files. White balance and tint value is slightly different for all of them as they were shot in 'Auto WB' on the camera. Wanted to adjust the tint value on all images but retain their existing WB value. Selected all, made sure Auto Sync was on in Develop mode, and moved the Tint value to 5. Expected result: all selected images should now have a Tint value of 5, while retaining their original WB value. Actual result: the WB and the Tint value for the main image was applied to all selected images, even though I had not adjusted WB at all.Did an Undo, went through all images to confirm they all had different WB and tint values. Selected a different image. Did a Select All, Auto Sync on. This time I set the WB value for my main image. Expected result: all selected images should now have the same WB as the main image, but their Tint values should be unchanged. Actual re
click on import photos and nothing happens .On iMac latest software
Everytime I open lightroom classis now and try to use my pixieset plugin I get the error code #1000 "Connection failed, please check your internet connection and try again". I have strong internet connection so this isn't the case. I am using Lightroom classic v 14.5.1 on Windows 11 and recently switched internet from spectrum to fiber, not sure if this has anything to do with it. I have removed and added the plugin several time as well. Would appreciate any insight, this has been very frustrating!!
How my work led me to videography I discover an amazing tool/way for skin correction in Premiere pro, which I would definitely like to see in Lightroom if possible. Excellent way to correct skin tones.There are countless tutorials on how to fix skin tones what you can found on the famous video service. I am sending a randomly selected one in order to better explain what it is about.https://youtu.be/u3_yp3YbbEg?t=152 Thanks
Once a photo is loaded from my library, after hitting develop, pictures have color splotches on them that makes editing them impossible. This seems to have started on or about 7/20/26.Original:In Develop mode without starting any editing (note: I have restarted my computer since the issue started):
I encounter an issue with the latest update (V11) on shortcuts to assign a color label (6,7,8,9).Those shortcuts won't anymore assign a color label, it will now only remove the color label. The shortcut "Assign a color label and go to next photo" (Shift+6 to 9) still work well as previously.Please fix this adobe, my culling speed depend on it. Thanks in advance,
· Title: LrC 15.4.1 UI Issue: Closing Remove Tool leaves gray panel area; fails to redraw Edit/Basic panels. · Product: Adobe Lightroom Classic v15.4.1 Release (Camera Raw 18.4) · OS: macOS 25.6.2 · Description: In the Develop module, using Solo Mode with the right panel visible, activating and then closing the Remove (spot removal) tool completely breaks the right panel interface. The panels vanish into a blank, dark empty column. Global panel keys (F8, Shift+Tab) and top menu toggles fail to restore it. Workaround: Clicking the Edit icon (sliders) manually, or toggling Crop (R) or Masking (M) or Red Eye Removal icons on and off forces Lightroom to redraw the UI, successfully bringing the Basic and edit panels back. Exiting the develop module to the Library module, (G or E) and then re-entering the Develop module (D) will also bring back the Basic and edit panels. · Camera model: N/A · Steps to Reproduce:Open Lightroom Classic 15.4.1 in Develop module with Solo Mode active.
Hey,I’m stacking in PS from LRC, saving works fine, flagging, color label works fine. During the same session, these files disappear from LRC. They’re on the disk. I can’t import them, the import module won’t “see” them.
EnvironmentAdobe Lightroom Classic 15.4 Lightroom SDK Windows 11 Standalone reproducer plugin attachedSummaryA floating dialog opened via presentFloatingDialog() does not consistently receive keyboard input.The same floating dialog implementation exhibits two different behaviors depending on the SDK calls executed immediately before the dialog is created.In one case, keyboard input is routed to the floating dialog immediately after opening.In the other case, keyboard input remains with Lightroom, allowing Lightroom keyboard shortcuts to continue working while the floating dialog is visible.A complete standalone reproducer plugin is attached. Steps to ReproduceInstall the attached reproducer plugin via File > Plug-in Manager > Add. Run via File > Plug-in Extras > Floating Dialog Keyboard Input Reproduction. Choose one of the two test configurations: Plugin dialog receives keyboard input Lightroom receives keyboard input Press the Tab key.A complete standalone reproducer pl
When Use Graphics Processor is enabled, the audio on my PC either freezes or crackles, especially during more demanding tasks such as masking and AI-powered masking.I assume Lightroom Classic is utilizing the GPU at or near its maximum capacity in these situations.It would be helpful to have an option to limit or control GPU utilization, similar to the hardware resource controls available in Photoshop. This could help users balance performance with overall system responsiveness and avoid issues such as audio stuttering.GPU acceleration provides a very noticeable improvement in Lightroom Classic's speed and responsiveness, so I prefer to keep it enabled.
라이트룸에서 생성형 업스케일를 사용하면 파일은 어디에 있나요! 내보내기를 해도 해상도가 업스케일 하기전의 해상도입니다. 여러번 업스케일을 시도해도 크레딧만 소모하고 이미지해상도가 그대로입니다.
Hi,I recently switched from a MacBook to a Windows PC, and it seems to me that Lightroom Classic is not working properly — although Adobe support says everything is fine.The program runs very slowly. When using masks, there is a noticeable delay in the preview, and the image appears to jump or refresh. I’ve attached a video below showing the issue:https://youtu.be/Rdp1xHr3LAk?si=JiAgedctehGnfyoIIs this normal? On my MacBook M1 I never had any problems with smooth performance.I also noticed that when Lightroom Classic is open, the entire computer seems to slow down — even moving a Chrome window feels laggy and stutters. When the program is closed, everything becomes much smoother again.Here is my computer specification: AMD Ryzen 9 9950X3D ASUS Prime X870-P WIFI 192 GB DDR5 5200 MHz RAM RTX 5080 16 GB 2 TB Samsung 990 PRO M.2 (up to 7450 MB/s) 4 TB Samsung 990 PRO M.2 (up to 7450 MB/s) 4 TB Samsung 990 PRO M.2 (up to 7450 MB/s) 1200 W BeQuiet modular PSU Fractal Meshify
Lightroom Classic Version15.4.1macOSTahoe 26.5.2HardwareMacBook Pro (Apple Silicon)DescriptionExport as Catalog consistently fails when the destination is an external exFAT SSD.After several minutes Lightroom displays:“An unknown error occurred while exporting the catalog.”The partially created export folder is then deleted.The identical export succeeds immediately when the destination is the internal APFS SSD.ReproductionOpen any Lightroom catalog. Choose File → Export as Catalog. Select an external exFAT SSD. Export with or without negatives. Wait. Lightroom reports “Unknown error occurred while exporting the catalog.”ExpectedCatalog exports successfully.ActualGeneric error.Export folder deleted.Reproduces onSamsung T9 (exFAT) SanDisk Extreme SSD (exFAT)Does NOT reproduce when destination isInternal APFS SSD.The same catalog (approximately 415 GB including negatives) exports successfully to the internal APFS SSD in a few seconds. The resulting exported folder can then be copied to th
Customizable keyboard shortcuts in Lightroom would be great. I just find it so confusing that crop and brush tools and things like that have such odd keyboard shortcuts in Lightroom. I understand that changing that all now would be awful for many existing users, but being able to override them like I can in Photoshop would be helpful. Doesn't anyone else out there find they use to wrong keyboard shortcuts in the wrong program?
When I try to start lightroom classic I get the error message ?:0: attempt to index field'_nglController' I cannot get it to start in any other way. Greg Hoglund
Product: Adobe Lightroom ClassicUI language: Polish (Polski) — issue also affects English source copyOS: Windows 11Lightroom version:[paste from Help → System Info → Copy]Steps to reproduce:1. Library → select any photo → File → Export (Ctrl+Shift+E)2. File Settings → Image Format: JPEG3. Enable “Limit File Size To” → set to 5000 K4. Click ExportActual result:A dialog appears. In Polish UI the title is “Aktualizacja limitu rozmiaru pliku” and the message reads:“Jeśli obraz nie może osiągnąć limitu, zostanie on eksportowany do minimalnego możliwego rozmiaru pliku.”The English source text (approximate) is:“If the image cannot reach the limit, it will be exported to the minimum possible file size.”Problem:Both wordings are misleading. “Minimum possible file size” strongly suggests Lightroom will crush JPEG quality to the smallest file (e.g. tens of KB). That is alarming and contradicts what users expect from a paid subscription.What the message should describe is the opposite scenario: wh
Lightroom Classic version: 15.3.1Operating System: macOS 26.5.1Computer: MacBook Pro M1 Max, 64 GB RAMCameras affected: Canon R5 Mark II Canon R6 Mark II Description:AI Denoise suddenly stopped working during an editing session. It had been working earlier the same day and then began failing on every RAW file.The issue affects RAW files from both Canon cameras and occurs across different folders and catalogs.When I select Photo → Enhance → Denoise → Enhance, Lightroom either displays:"An unexpected error occurred while processing."or no Enhanced DNG is created.Troubleshooting already completed: Restarted Mac. Reinstalled Lightroom Classic. Cleared Camera Raw cache. Verified over 600 GB of free disk space. Tested multiple RAW files from different folders. Tested files from two different cameras. Catalog and RAW files are on an external drive. Lightroom edits, exports, and all other functions work normally. AI Denoise is the only feature that consistently fails. This ap
I purchased Lightroom Classic v15 but recently it has been crashing all the time. Was recommended to download the latest version (15.4.1) but now it says I have rebuy the program. As I already purchased it don't want to pay again. how do I get back to my original working version?
Description of Issue:Merge to HDR stalls (application unresponsive, beachball) when merging exposure-bracketed images on 15.4.1. Another user in an original 15.3 thread reported this resolved after updating to macOS Tahoe 26.5. I am on macOS Tahoe 26.5.2, a newer build, with a fresh OS install, fresh Creative Cloud install, and a brand-new catalog, and the stall still occurs on 15.4.1. This rules out the macOS-update fix reported by others for the 15.3 version of this issue.Lightroom Classic Version Number: 15.4.1 (Help > System Info)OS Version Number: macOS Tahoe 26.5.2Camera Model: Sony a7r V & DJI Mavic 4 ProComputer Version: Mac Studio M3 UltraStep-by-step Reproduction Instructions:Fresh macOS install, fresh CC/LrC install, no plugins, brand-new catalog. Select a set of exposure-bracketed RAW images. Photo > Photo Merge > HDR (or Ctrl+H or Ctrl+Shift+H). Merge stalls partway through; have to quit to reset the merge process.Expected Result: HDR Merge completes and produ
I moved a folder from one hard drive to another and Lightroom is throwing me in a loop. I’m at a loss, I don’t know what to do here! This makes zero sense I’m going in circles.
As the title says the folder where my Lightroom catalog is stored only shows the folder 0 to 9 and A to F. In these folders there are seperate folders (like 0A2A). Is there a way I can rebuild/restore my catalog? It is not showing any .lrcat / .lrdata files.
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.