Lightroom Classic

When tethering it's common to change lenses or batteries. This causes the "detecting camera" dialog to appear directly in the middle of the screen, and it blocks the viewer.  My clients often almost reflexively hit the cancel button, meaning I need to manually restart the tether session. Capture One handles informing the user of the tether status a lot more gracefully. The current implementation isn't really appropriate when clients or other team members may be monitoring the shoot via the tether session. 

Lightroom Classic 11.1, MacOS Monterey 12.0.1, M1 Max MacBook Pro The following is repeatable for me and leads to a constant and rapid memory leak that will consume all avaiable system memory:1. Add around 250 photos and some videos to Quick Collection. Select Quick Collection2. Select slideshow. Run the slideshow3. Lighroom will now leak memory at a rate of several GB per minute until all system memory is exhausted. Attempting to quit the application will hang with a spinning beachball. Memory continues to leak while the application is unresponsive until it's forced to quit.4. Now whenever I start Lightroom the same behaviour occurs - it begins leaking memory immediately, regardless of whether I attempt to run the slideshow or not5. The only way to fix this is to start Lightroom, quickly clear the Quick Collection, then force quit. Lightroom is now back to normal. In anticipation of the initial response I have reset Lightroom settings using the Opt/Shift on startup, and the

Lightroom Classic WIndows 11 14.0.1 Camera Raw 17.0Checking image at 100 percent using shift-PgDn there is a noticeable delay each time I move to the next section with no tools selected in Develop. But if I select Masking, Redeye or Remove, the move on shift-PgDn is instantaneous.I was one of the original beta-testers for Lightroom while it was being developed.

When Command-E to send an image to Photoshop, (DNG from iPhone), the image is much lighter. I've been using Photoshop since verion 3 and Lightroom since version 1 and have never come across this. In order to make it work, I have to Export as PSD, only then does Photoshop match what I see in Lightroom. Any thoughts? Mac Studio 2025, M4 Max 128 GB,  15.6, latest versions of LR and PS.    

Ich fotografiere seit vielen Jahren mit der Nikon Z6 und seit Anfang 2025 mit der Nikon Z6 III und u. a. mit 5 Zeiss Objektiven ZF.2.Mit der Z6 III werden 3 dieser Zeiss Objektive in Lightroom unter Objektivdaten mit 5mm f1 angezeigt, obwohl die richtigen Daten 35 mm f2,0 und 50 mm f 2,0 und 100 mm f2,0 sind. Mit der Z6 werden die vorgenannten 3 Zeiss Objektive dagegen korrenkt angezeigt!Die Firmware beider Kameras ist auf dem aktuellen Stand.   In den RAW-Aufnahmen mit beiden Kameras werden im Exif-Viewer die korrekten Objektivdaten angezeigt!   Folglich müssen in Lightroom Fehler in der Kombination "Profildaten" Kamera Nikon Z8 II und den "Profildaten" der genannten 3 Zeiss Objektive sein.   Wegen des Fehlers kann ich bei den Aufnahmen mit der Z6 III nicht erkennen, welche Aufnahme mit welchem der 3 verschiedenen Zeiss-Objektiven entstanden sind.   Ich hoffe, dass die Adobe Lightroom Systembetreuer das Problem lösen können.    

Help required: I get Lr crashes when I move an image to the print module in LR classic.  2022 m1 max iMac studio with 32gb of ram. I noted that memory pressure was only at 40% at last occurrence. I have reported via the submit crash report pop-up on numerous occasions with no reply, and the system check pop-up finds no fault within my system.   extract from the crash report>>   Process: Adobe Lightroom Classic [5066]Path: /Applications/Adobe Lightroom Classic/Adobe Lightroom Classic.app/Contents/MacOS/Adobe Lightroom ClassicIdentifier: com.adobe.LightroomClassicCC7Version: 14.0.1 (14.0.1)Code Type: ARM-64 (Native)Parent Process: launchd [1]User ID: 501 Date/Time: 2024-10-27 16:50:27.7684 +0000OS Version: macOS 14.7 (23H124)Report Version: 12Anonymous UUID: 6BC1FE9C-D164-90F3-6A59-95387E283444 Sleep/Wake UUID: C3527BE1-A19E-4F28-9F25-1754EEBC87DF Time Awake Since Boot: 30000 seconds System Integrity Protection: enabled Crashed Thread: 0 CrBrowserMain Dispatch queue:

hi, i works with a canon 5d mark2 and seveal lenses from canon Lso the 100 mm canon macro L lens isn't in the lens profile to vind.it was visible at first, why is it desappear?and can i take it back? thanks for your reaction grtz marcel  

I notice that LR eats all memory when you start importing images. When opened, it takes about 1.5-3GB ram. Then import 100 images, and RAM shoots up to +17GB   Iv been doing some tests with smaller raw files, same thing, always goes up to 17GB ram usage. The folder i imported as test contains only 5GB of raws, and LR uses more then twice that amount to import those images? When you delete the images, 17GB ram is still in use. Then tested less images, like 30, and memory still goes up, but less, around 5GB ram extra, for images that on disk only take around 1GB. Importing more images, like +300 will not make memory to increase more then 17GB.   Solution? Import images, restart LR to clear memory, edit... and ram usage will stay "normal" around 6GB during edit after some testing. Thats 10GB less then just doing an import. Whats up with that?   Im on 13.5 btw   [Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules.]

Lightroom 14.3.1/Camera Raw 17.3.1 Windows 11 Version 24H2   For all non-adaptive profiles the histogram in the develop module's Histogram widget and the histogram displayed behind the Tone Curve widget match in shape and the tone curve works correctly (c.f. first screenshot).   As soon as an adaptive profile is applied the tone curve seems to be compressed to the first 3 quadrants and reacts overly sensitive. (c.f. second screenshot) Also when adjusting the tone curve picking the brightness values directly from the image even whites/blown out hightlights are not mapped to 250+ values but rather to 180+ (c.f. third screenshot).   Steps to reproduce: 1. Select a raw file (Canon .cr3 from a R6 II in my case) 2. Go to develop module 3. In the Basic widget switch to one of the adaptive profiles e.g. Adaptive Color 4. Go to the Tone Curve widget and check the histogram; the histogram only use the 3 leftmost quadrants 5. Now switch to a non-adaptive profile e.g. Adobe Color 6.

Hello,  still not working in LRC 14.0.1.  , I have old yellow badges but not new ones on last sync. collection. Any idea ?

The Edit Capture Time command doesn't preserve fractional seconds when shifting the time of multiple photos. For example, if you select a batch of photos taken with "continuous shooting", e.g. at a sporting event, and then use Edit Capture Time to shift their time by 60 minutes, the fractional seconds of each photo will be dropped and the photos will no longer be correctly ordered by capture time. To reproduce, take several photos that were all shot within the same second with the continuous-shooting option of the camera. LR will correctly transfer the capture time into their .xmp sidecars: [XMP] Date/Time Original : 2011:05:13 18:32:44.51 [XMP] Date/Time Original : 2011:05:13 18:32:44.52 [XMP] Date/Time Original : 2011:05:13 18:32:44.53 Then select those photos and invoke Edit Capture Time. Use either the "Adjust to a specified date and time" or the "Shift by set number of hours" option to shift the time by 1 hour. Observe that the fractional seconds in the sidecars is now dropped: [X

Hi Lightroom experts,I am using Lightroom Classic CC on my Mac. Both on latest versions. Within Lightroom, when I move a file from one folder to another I get a pop up with the following message/warning.Quote:Moving a File on DiskThis will cause the corresponding file on disk to be moved. If you proceed, neither this move nor any change you've made prior to this can be undone.End quoteWhy is this so? Is there no way to move a file in lightroom and keep the ability to undo previous edits?Some times I edit an image and then realize I need to move it to a different folder or rename the folder. Given the above, I would lose my edits. This seems wrong and should be an easy feature to add.Thanks,Puneet

Have updated to LR Classic CC 7.3  Develop module when using the crop tool it shows the last image cropped for about 1 second before showing the current selected image.

Hello reader,I can't adjust the settings in Lightroom Classic preferences because I have a Canon RF 24-105mm f/2.8 camera lens. What am I doing wrong, or what do you recommend? See examples.Regards, Henk

Bonjour,J'ai un vrai souci avec LRC depuis plusieurs mois : il se plante de manière intempestive.Je voudrais savoir la cause, et comment réparer ... Quelqu'un peut m'aider ?Merci !!! Ma configuration : Version [202508231203-c2638d01]Ma version de Windows 11 :Édition               Windows 11 ProfessionnelVersion              24H2Installé le         ‎05/‎12/‎2024Build du système d’exploitation       26100.6725Numéro de série          CZC427720MExpérience      Pack d’expérience de fonctionnalités Windows 1000.26100.253.0Mon PC :Processeur      Intel(R) Core(TM) i7-14700K (3.40 GHz)Mémoire RAM installée          32,0 Go (31,7 

Generative remove content seems correct but image generated on thin line removal is blurry / lacking resolution.  This is the case with all varaitions.Source image is 40Mpx Fuji Xtrans file. Selection was about 2.5 width of the line ( smaller than the blurry area) Reproduction : import  Lightroom Classic v14.5.1windows 11 10.0.26100

My Lightroom Classic keeps bugging in the Develop module. I only see visual glitches on the screen and I have to close and reopen Lightroom. I’m using a 2019 MacBook Pro and Lightroom version 14.5.1. What should I do?

I created nested Keywords without any problems but tonight I can't created keywords.   I creted the following keywords: WHO, WHERE and WHAT.  I had to create the WHAT keyword inside another keyword and then drag and dropped where I wanted.  The "+" on the Keyword List tab doesn't seem to be working anymore.  I tried adding the following keyword, 0 GENRES PORTFOLIO as the top level of nested series.  When I click ok it never appears in the list and it gives no errors.  One fix said to delete the helper.irda files which I did,  but it did not resolve the problem.  Should I reinstall Ligthroom Classic?  That's what I use.

I have had successful uploads from LR to Blurb for years. For the last three months it has failed to upload. I want to send to Blurb to publish the book. I do not need PDF only - I need to send to Blurb for publishing.I have tried all their suggestions with no success.Blurb says it's a glitch in LR.Any ideas? Thanks  

When using the Remove tool and ticking the "Use generativeAI" box, it identifies the areas. When you click the remove box it comes up with a message "We have encountered a problem and cant complete your request. Try again later". Tried restarting the program and the PC and get same message

 Description of IssueWhen moving between images, and sometimes when updating develop settings, the main window doesn't update sometimes, for periods of over 10 seconds.  The OS doesn't seem strained and there's no beach ball - it's as if the application hasn't woken up for some reason.Lightroom Classic Version Number (Help>System Info…) 14.5.1  (this issue started - I believe., when moving from 14.4 to 14.5).OS Version Number14.8 (23J21)Camera Model (sometimes necessary)Canon EOS R1, EOS R5Step-by-step Reproduction Instructions (in precise terms, please)Import images into lightroom, switch to develop, scroll thorugh images in filmstrip.The Expected Resultimages load quickly and consistentlyThe Actual Resultsometimes when selecting an image, Lightroom seems to have not figured this out for over 10 seconds at times.  System is not at high load (fans aren't spinning at full speed and CPU doesn't seem to be thermally throttling).System specs: MacBook Pro 2019 16

I'm wondering if anyone has seen this before and has an explanation for what is going on. I shoot Fuji RAF format and have a preset on Import that applies my preferred profiles & default Develop settings. Sometimes I make a few other edits before eventually converting all my images to DNG (typically I wait until I'm connected to a power source to do the DNG Conversion because it drains my laptop battery).   Here's the random bug I've experienced over the last few versions of LR: I'll batch convert hundreds of images from RAF to DNG in LR. Then I'll notice that some random images have lost all my edits - including the default edits applied on Import. The History Panel will show "From Metadata" and if I go back one state everything is back the way I had it before the conversion. (see screen recording of one such file) It's quite annoying to have to go back through ALL my images and check each one to see if it has lost the edits as there is no way to filter and see only the ones