Lightroom Classic

would like Adobe Support to investigate this as an AI Edits Storage / .lrcat-data problem, rather than repeating the standard troubleshooting steps that I have already completed.In particular, I would like to know: Is there a known regression or bug in Lightroom Classic 15.5/15.5.1 affecting AI Edits Storage or .lrcat-data? Can Adobe Support analyze my existing .lrcat-data file for corruption or structural problems? Does Adobe have an official .lrcat-data recovery or repair tool that can preserve as much existing AI-edit information as possible? Can my current catalog and .lrcat-data be safely repaired without replacing the catalog and without unnecessarily losing existing AI edits? What is the officially recommended procedure for returning my current catalog to a fully functional state with AI editing? Should I remain on Lightroom Classic 15.4.1 until this issue has been resolved, rather than upgrading the working test environment back to 15.5.1? I have deliberately not dele

hello, I have a strange issue with the Print Module in Lightoom Classic - I select some photos in Library - I click on Print module when the layout style is first one (single photo) I see photos in main view, I can change number of rows or columns, etc   but when I change layout style to second or third option: - the main screen shows only blank paper - the page number is not refreshed (so for example it still shows page 1 / 13) - changing template on the left does nothing - it's not possible to drag photo from filmstrip into main view   I tried refreshing view, changing photos, restarting Lightroom and resetting LR preferences   any tips what is wrong?   LR 13.3.1, Windows 10

Description of issueI use a Develop preset that lowers the global Saturation slider and changes color values in the Color Mixer. On some photos, every preset adjustment is applied. On other photos, the preset appears to have been applied, but the global Saturation and the intended Color Mixer values do not change at all. This is easy to miss because the preset still looks applied. I have observed this on two different Macs running up-to-date Lightroom Classic. I am reporting my own observations, not claiming that every user or photo is affected.Steps to reproduce1. In Lightroom Classic, use a Develop preset that includes a reduction in global Saturation and changes to Color Mixer values.2. In the Import dialog, select that preset under Apply During Import and import a group of photos.3. After import, inspect the global Saturation slider and Color Mixer values for individual photos, including photos where the preset appears to be applied.4. Select an affected photo in Develop and apply

Hi there!The previous LR Classic version was snappy and responsive. The latest build is extremely slow, adding a mask takes 5-10 seconds and the image glitches alot. I have an Asus ROG Strix 18 laptop with a Nvidia 5070 ti graphics card and 32 gb ram & a nvme SSD, running Win 11 Pro. When lightroom is opened, everything on my computer slows down, even moving from a browser tab to another adds a 2-3 seconds lag. When LR is closed, everything is snappy and fast. I have the latest Nvidia studio driver, everything is updated, and i have setup Maximum performance in Nvidia App for Lightroom, disabled energy saving for pcie and gpu. I am on Performance mode and Ultima mode in Armory Crate. This laptop should fly, but the latest LR Classic is extremely unperformant.Another thing that happens lately - when i try to exit, it says Lightroom has not finished writing metadata to xmp. I left it over night, still the same message. I optimized my catalog, still the same.What can I do to fix this?

A simple proposition.We could given the ability to crete custom history steps. How would it work:Via a dialog we could enter a custom name for a step OR use the current date/time.UI dialog presentationCustom Name for history stepCurrent Date and Time for history stepWe could custom steps via a + icon in Develop panel akin to SnapshotsCustom history step name creation also doable in Library via an option.Creation of “Custom History Steps” should “AutoSync”Advantages:No need to change the edits in the photo to generate a step.Users can use this option to create critical events in history in ways LrC can’t or create steps if history is missing.Unlike snapshots nothing ends in XMP when saving. 

I have many video files imported into LrC that I want to modify the filename.  The video files were taken with the iPhone 17 Pro.  My usual method to edit the filename is to edit the filename entry in the metadata panel.  When I use the method I get an error message that the filename cannot be edited.  If I use the alternate method of using the F2 key, I get the same error message.  I have submitted another bug report about not being able to import video files into LrC 15.5.  That bug report has been “Acknowledged”.  In that case reverting to v15.4 allows imports. Unfortunately reverting to v15.4 does not fix this issue. 

I can´t import any files whatsoever into Lightroom. They just dont appear as if the folder was empty but the files are there. Please help!  

My normal work practice of taking all my photos as CR3, doing all the Develop work, then exporting as JPG and reimporting the JPG back into Lightroom has suddenly stopped working.I have just moved my catalogue to my G: Drive from being split between my D: and G: Drive and been through the problems that caused with the Capitalisation of different folder names. Got this resolved yesterday so I am back focusing on my normal processing.After earlier issues that I raised a question over about a month ago I modified my Export Script to output the JPG into the same folder as the CR3, whereas I had always exported to a different folder and dragged the JPG back to where it should have been.Suddenly now with my first export CR3 to to JPG since fixing the capitalisation things have gone awry.The export works and the JPG is created in the folder I expect. I have tried both my old and new export scripts, placing the JPG in an output folder and leaving the JPG where the CR3 is.Now when I go to impor

 When I'm using the heal tool in a cropped image, trying to move the handles for the heal area selection or target area selection causes the image to revert to completely uncropped, but still shows the heal UI in the place on the screen where it was (NOT the same place on the image). When I release the UI, the image pops back to cropped. This makes it very difficult to fine-tune where I'm trying to move the heal UI.

The Reflection Removal Tool is not working for me.  I am running LrC on an iMac.  I always start with a DNG image of a shop window and use the tool as the first action in my Develop workflow.  The attached file is representative of the results I get consistently no matter the image.Please share your insights on how to fix. Thanks, R

Lightroom Classic masking tools have a 5–6 second activation delay when selected by mouse, but activate instantly when selected using keyboard shortcuts.Steps to reproduce:Open a RAW image in the Develop module. Open Masking. Click Linear Gradient with the mouse and draw a gradient. The first mask may activate immediately or after a short delay. Create another mask and click Linear Gradient again with the mouse. Lightroom takes approximately 5–6 seconds before the Linear Gradient tool becomes active. Once active, drawing/applying the gradient is immediate. Instead, use the keyboard shortcut M to create/activate a Linear Gradient. The tool becomes available immediately, even on the same image with the same existing masks. Alternating between the two methods consistently reproduces the behavior: mouse click = ~5–6 second delay; keyboard shortcut = immediate activation.Additional testing:Reproduced on Lightroom Classic 15.3, 15.4.1, 15.5, and 15.5.1. Reproduced with RAW and 16-bit TIFF fi

As the title says, if I go to the develop module in lightroom, click on the removal tool then go down to distractions and click apply on the reflections section I can’t then send the photo to photoshop. If I send it to photoshop it opens up the photoshop app but just gives me the home screen as shown and doesn’t open the photo.   

I have version 15.5.1, the latest version.  When I mask the sky on a photo like this it will mask the white park of the horses blaze as part of the sky.  I then have to subtract the object or subject.  The subject masking sometimes makes a similar error and skips the blaze.   

Hi there,just realized the lens correction profile for Ricoh GR IV in LR version 15.0.1 is wrong in terms of vignette correction. It leads to significantly oberbright edges. Applying the GR III profile seams correct.

I’ve been wanting to reactivate LR Classic on my account after several months, but I can’t find LR Classic on my current account.  It’s been there for years, what’s up?

 When my long-established Lightroom Classic catalogue (~183,000 images) is opened with the drive containing the original photographs online, Lightroom automatically begins a large background image-analysis/culling operation. I am not deliberately starting Assisted Culling.During this operation Lightroom systematically reads original image files and its committed/private memory grows continuously. I have observed Lightroom reach approximately 148 GB Private Bytes, at which point Windows becomes extremely difficult to use.If the originals drive is disconnected, the same catalogue remains stable at approximately 2 GB PB.Clean Lightroom catalogues using photographs from the same physical drive and same original files behave normally: processing completes and memory stabilises. The problem reproduces in Lightroom Classic 15.4.1 and 15.5.1, and also with GPU acceleration disabled.SystemWindows 10 Pro 22H2Intel Core i9-1090064 GB RAMNVIDIA RTX 2060 6 GBCatalogue/previews on dedicated SSDOrigi

When decoding Panasonic S1M2 RW2 RAW files in Adobe Camera Raw, the Camera Matching V-Log profile is severely inaccurate.Additionally, after applying the Camera Matching profile in ACR, it is not possible to apply a LUT on top of it. This is a critical limitation for the RAW → V-Log → color grading workflow.（All Bug and issues above do not exist in Lumix Lab which is offical APP of Panasonic, I think you can fix these issues according to their latest offical APP）

My lightroom classic 15.0.1 catalog is behaving strangely for some time and I cannot solve it. All photos seem to revert to their original (pre-edit) state. In Development History, I see entries after the last edit of the following kind (from bottom to top)From Lr mobileMultiple settingsCamera Raw settings.I synch a few albums but not all. When I return to the history element of my last edit the photo displays correctly (i.e. with my edits), and if I make another change of any kind, the above mentioned entries all disappear.My catalog is >100'000 pictures and it seems to affect all of them - initially I thought only the synched albums but I also see it in non-synched ones.I have tried searching the forums for a solution to this and whilst I found similar errors, no solution yet. All help appreciated.

I am in the terrible situation, where my dumb a** unintentionally deleted Mobile Downloads file, when trying to clear out space on my macbook. Now my LrC cannot find the files… I am looking for a way to restore/fix this mistake. Does any one have any tips or ideas? I am not very familiar with the lightroom eco system, as you might’ve guessed already…Hope any of you know anything of thisThanks in advance, and kind regardsAnders, a very stressed creative...

I am using Lightroom Classic 15.5.1 on an iMac. I have approximately 40,228 photographs already successfully synced over then years.I created a new synced collection containing 803 JPEG photographs. Syncing stopped with 364 photographs remaining and stayed there indefinitely.Lightroom Sync Activity shows the first affected photographs as “Uploading — [file path] — Image.”View Sync Status on Web reports no sync problems, and there is no “All Sync Errors” collection in Lightroom Classic.I tried removing individual photographs at the head of the stuck queue. This allowed syncing to progress temporarily from 364 to 362 and subsequently to 356, but it then stopped again on another photograph. A newly created synced collection also remains queued behind these photographs.I have generated the Lightroom Classic Sync Diagnostic Report.I have not used Rebuild Sync Data or reset the cloud library.Anyone out there having this problem?

For all the years I have used Lightroom I have used a User Preset to Import my photos. This is pointed at the current month in my Folder Structure and creates folders in that month according to the day of the month the photos are taken. Each month I edit the preset to move the output to the next month. I have recently mover my entire Catalogue from being split between my D: Drive and my external G: Drive so the entire catalogue is on the G: Drive. The Import User Preset has gone “wrong” and I cannot find a fix. Refer the following screens. Import using User Script - everything is as it should be with a couple of days straggling to be moved back to AugustLightroom structure after Import Nothing has added to September. Going through Previous Import - Photo - Go to Folder In Library takes me here. Which is outside my Master CatalogueThen I cannot Drag any of these new folders into their correct location within the Master Catalogue.I cannot find any way of either rectifying the problem wit

When backing up it states that it only backs up the catalog and not the photographs. How do you back up the RAW photographs from LRC to a hard-drive, especially if they’re already in Collections. 

J'ai des problèmes de synchros sur LRC sur des photos avec beaucoup de calques. Il n'envoie pas tout dans le cloud (ce alors que je suis en vert la liste est vide), quand je récupère sur Lightroom mobile il en manque régulièrement je dois jouer avec l'historique des versions pour retrouver la dernière.Tout est en dernière version et je n’ai pas de problème signalé dans Lightroom web.

QED: Updating Adobe CC apps can ruin the whole thing. This time it is to me the very essential Web module, which does allow saving the album at all. Nope: You do not save! So the Web module allows to  compose album normally, but without any reason the saving is disabled and the whole Web module thus useless.Macbook Pro M1 Max, MacOS Golden Gate 27.0 and Lightroom Classic 15.5.1