Lightroom Classic

I have newest version of LR Classic 11.1 AND MBP with OS 12.1 tethered to Canon 5D Mark IV with latest firmware. Running in Rosetta Emulation Mode with an external monitor. Tether control panel doesn't come up. I can manually trigger capture from the camera or from File>Tethered Capture>Trigger Capture but the control window is nowhere to be seen. Yes, tried to hide and show. Tried CMD+T. Tried disconnect and reconnect. Tried stop and start. Tried Full Screen and not. Last week it worked intermittently and sometimes would  on secondary display. Today not at all. Also lost connection today after multiple attempts to start and stop. Had to make the clients wait and pull the card and import manually. Please fix this and better yet, fix tether where it doesn't have to be switched to Rosetta. I feel like Adobe was finally taking tethered shooting seriously and consistent dependability has been so improved recently. Until I bought my new M1 MBP that is. Now it's back to a crapshoo

Today I imported 6 new image files into LR. After doing some edits on one image, I continued on to another image to edit. When I returned to the first image in the Develop module and selected the Crop tool, the image broke down into dashes of color across the entire image. When I view the image in the Library module it looks fine, but when I go to Develop module it breaks down. The same applies to all 6 new images. However when I view any of the 6 images in the Print module, it returns to "normal". I quit LR and reopened it; I deleted the images from the LR catalog and imported them again, and still encountered the same result in the Develop Module only. I then opened the image in Photoshop via LR and no issue - the image looked fine. All 6 images looked fine in Bridge. But when I opened them in Camera Raw, I encountered the same problem with those images as in LR. This issues does not occur with any other image file in my catalog when viewed in the Develop module. I have included scre

Hey all,  I have my Lightroom catalog and smart previews set to store on my MacBook Pro's SSD and my main image library stored on a LAcie Thunderbolt Quadra drive. I import with standard previews and smart previews and when viewing the file using Lightroom on my external montior set to 3000x1670 resolution the actual picutre in lightroom at 100% is vastly smaller than the screen area. I've tried unchecking edit with smart previews, i've also attempted to render 1:1 previews and nothing seems to be working.  It's frustrating not to be able to zoom into the file at a true 100% and check for focus and sharpness. I'm assuming this is a setting somewhere but i'm at a loss as of where to find it.  As a side note, the files are from a variety of cameras however all were shot in RAW at a resolution greater than my screen display size. Thanks! 

I'm sorting through photos I've taken of my girlfriend. Made a folder for only pictures taken with a flash. But when I sort the pics by Did Fire and Did Not Fire, the metadata has it incorrect. Some pics I know I used flash on are marked as Did Not Fire, and vice versa with some pics I know I didn't use flash on.I would have thought it was the camera writing wrong metadata, if this hadn't been the case with pics from three (3) different cameras. Two Canons and one Fujifilm. So what's up, is this a widely-publicised problem, or what?

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.... I have just been on chat with support and was told that if i create Coll Sets and Colls in LRC, then they will sync to LR... shame it doesn't do it the other way!

Issues with Adobe used to drive me nuts because I kept asking why is it that a company so successful that employs genius developers (let's face it Adobe has features that requires that genius!) allows so many high profile bugs to be released into production. I am well past that point now (call it fatigue?), because it is what it is.   And here I am writing yet another post about sync feature not working...   Adobe has a number of competitors these days and while many of them a truly amazing, all of them are missing critical and painfully obvious features. So that leaves me with Adobe. One of the features that I should be excited about is Sync. I use(d) sync to view and edit photos on iPad, and it is a great feature…when it works.   A few releases ago (sometime in 2024) Adobe released Lightroom Classic with all the sync setting and troubleshooting buttons gone. I was a bit shocked thinking ‘How will I at least attempt to fix sync when it fails’. But all of a sudden sync

Hello!I've been using Lightroom for a very long time, my current version is 5.6, I've been uploading from my Canon 5d mark iii effortlessly. I just got a new Canon mirrorless camera with an sd card and for some reason it is not letting me upload images from that card. Any ideas why? Thank you!Emilie Szabo

Hello, I added a custom metadata to my plugin and in the metadataThatTriggersRepublish function :  function exportServiceProvider.metadataThatTriggersRepublish( publishSettings ) return { default = false, title = true, caption = true, keywords = true, gps = true, dateCreated = true, ["com.myplugin.mymetadata"] = true, customMetadata = true, } end But when I update mymetadata in a photo from a published collection, it does not mark the photo to republish. I don't understand why and if it's a lightroom bug or if I miss something? Do you have this working like expected? Thank you

I cannot openj lightroom.  It seems like all of my saved catalogues are corrupted.  When I try to start a new catalogue I am locked out also. I have deleted all the "lock" noted catalogues.   I was able to start a new catalogue earlier but when I tried to import from any previous catalogue I received a message that says an error occured when trying to open this new catalogue.  Another problem I was having is that I am not able to update or open Creative Cloud to run a diagnostic. I am on a Mac using:221.45 GB available of 1.03 TBRunning Mac SonomaLatest Lightroom Classic Update. Any help would be appreciated. Steve

Hallo zusammen,ich habe seit letzter Woche das Problem, dass lightroom im entwickeln modus nur einen grauen Kasten anzeigt und die Bilder somit nicht bearbeitet werden können.Folgendes habe ich schon ausprobiert um das Problem zu beheben:Grafikkarten Beschleunigung deaktiviertCamera Raw Cache geleertLightroom neu installiert (Update ist keins verfügbar)Windows geupdatetbeim Farbprofil des Bildschirms sRGB als Standard ausgewähltHat alles nix gebracht, bin echt am verzweifeln...

Light room has been my go to for several years. The only thing im so bummed about the constant freezing and not saving my edited pictures like the time I put on them and i have to re- edit whats going on light room? 

Dear community, I would like to know if there are users of Lightroom Classic who know if there is an option to show the highlight clipping in red at thumbnail level. With having to whiten a large amount of files and being able to check which files need editing, this would be useful. Does anyone know this or can do this in a roundabout way? Thank you in advance, an adobe user for 25+ years.

After i imported new Pictures (taken with an Iphone 14 Pro Max with iOS 18) I get a call sign for every image with the error: a problem occurred in lightroom while reading this photo.I am currently still on version 13.1 on MacOS, but I can't update because Creative Cloud says that no new version is available. Does anyone have an idea?

PLEASE. HELP. Photography is my primary profession and this god awful performance is crippling my work flow. Its gotten increasingly slow with each new update.  Everything else runs blisteringly fast. User benchmark shows me in the top 10% in performance.   Im running: ASUS X570 TUF GAMING w/WifiAMD Ryzen 9 5900X 12-Core 3.7 GHz ProcessorGeForce RTX 3070 TI 8GB (PCIe 4.0) - latest studio drivers128 GB DDR4 3600MHz 18-22-22-42 RAM (32GB x 4)4TB NVMe WD Black SN850X (7300 MB/s read/6600 MB/s write) PCIe 4.0 installed in the M.2_1 slot (closest to processor)Windows 10 Pro - Moving photos or removing/deleting albums takes obscenely long and culling is obscenely laggy. (Even in develop tab)- denoise takes nearly twice as long vs initial release- significant stuttering and lag after editing albums, have restart app or the computer Yes, I have…- latest updates.- tried turning off sync- disabled GPU- tried experimenting w/preview quality up and down- optimized catalog- increasing cac

When I open a RAW image in Develop, the colors seem to be really "cool", almost like there's a blue overlay applied. When I perform an action in Develop, whether it's something like clicking a setting (without changing it) or if I simply zoom in on the picture, the color tone changes into a much more warmer one. When I open the same picture again, the "cool" version is shown for half a second, and then the tone changes again to warm.   I deleted my monitor color profiles and downloaded my latest GPU drivers (RTX 4080), but have no idea where to go next. Any help would be much appreciated.   Thank you.   [moved from bugs to discussions according to the community guidelines - Mod.]

My hard disk is getting full so I want to remover things I don't need. It seems to me that the only catalog backup I would need to save is the last one created. I use the default 'pictures' folder that Lightroom defaults to for catalog backups which is fine with me. Can I safely just delete old catalog backups as Lightroom saves them every time I make a backup, which is often, so now I have over 40 GB of catalog backups I want to dump most of but thought I would be wise to check here first before doing anything damaging. I have backups of all of the catalog backus saved to an external drive just in case... What are you thoughts and best practice for this?TIA, Ken

Printing on Epson P-900 through Lightroom Classic, the print dialogue box changed after MacOS 15 Sequia update and won't print like it did prior to the update. Typically when I update MacOS, I uninstall the Epson print driver then reinstall it and the issue resolves itself. This time it is not working and I have tried multiple times to uninstall and reinstall the Epson print driver. I keep getting the different looking print dialogue box and my prints are saturated in color and with dramatically increased contrast. They look like hell. With the print dialogue I typically work with, it prints beautifully. Has anyone encountered this and is there a solution? I read online somewhere that the printer is selecting the Apple print driver instead of the Epson driver. I contacted Epson and they said it's likely an Adobe or Apple problem. Thank you kindy for any help you can advise.   [Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules. Changed 'iOS' to 'MacOS'.]

I am suddenly unable to use subject, background or People masking in Classic. I was on v 13.5.x, rolled back to 12 and still had the same issue. Moved back up to 13 and it seems to sometimes work but not consistently. Machine hasn't changed, 2021 MBP with an M1 chip and 16gb RAM. Has been perfect until now. Example of the issue and LR specs attached, please help! I couldn't get a longer video but it does the same thing on almost all photos. Selects most or all of the back/foreground in addition to the subjects, and it used to be almost dead on with any subject.   Lightroom Classic version: 13.0 [ 202309270914-5a1c6485 ]License: Creative CloudLanguage setting: en-USOperating system: Mac OS 15Version: 15.0.1 [24A348]Application architecture: x64 (emulated)Logical processor count: 8Processor speed: 2.4GHzSqLite Version: 3.36.0Built-in memory: 16,384.0 MBReal memory available to Lightroom: 16,384.0 MBReal memory used by Lightroom: 1,563.2 MB (9.5%)Virtual memory used by Lightroom: 48,

Just since the most recent LrC update I have found that when doing my processing of images LR is NOT responding to image changes while in develop mode. It is "sticking" on a previous edited image and not advancing to the next image to be edited. Also when trying to crop an image it is going "back" to a previously cropped image and not to the one I actually want to crop. I am using Win10 and have 8gb RAM and working in LR has never before given me any major issues, until this latest update.     {Moved from Lightroom Cloud to Lightroom Classic Forum by Moderator} 

Bonjour,   J'ai 2 soucis avec Ligtroom un au sujet de la sauvegarde, elle commence et tout se bloque ,  et 'autre avec IA masque et retouche, il me demande des MAJ non stop et ne les mémorise pas, ce qui me fait utiliser des points inutilement. Je penses désinstaller et rinstaler mais si pas de suvegarde , j'ai peur de tout perdre et là, grosse colère lol..    Merci d'avance pour votre aide 🙂  Emilie   {Moved from Lightroom Cloud to Lightroom Classic Forum by Moderator} 

I discovered something strange    when i send a photo from lightroom to photoshop the lens correction applied are not thesame    I send a photo with this corrections from LR to PS      it comes back to lightroom with          corrections are different and the initial one can't be selected anymore    how can it be ?   Version is  13.5.1 Release Camera Raw 16.5   and MAC os Sequoia  so the latest the greatest versions     

I have one .cr2 picture with a xmp. When I import them, under the "Library" visualization the xmp is not read and i see the original picture, while under the "Develop" visualization the xmp is read correctly and I can see the picture in the correct way, with the settings applied. Do I have to set something specific to be able to see the xmp applied even on "Library"? LR Classic version: 13.5.1 - Camera Raw 16.5 - Windows 11 Pro 23H2 

I am wondereing how to reset all my Develop Presets back to the default set that comes with LrC and start over.  I have installed so many presets over the years of using Lightroom and I'd like to go back to a clean slate and install just the ones I use now.  Is that easy or just too much work?