Connect with fellow editors in our Lr Classic community.
Recently active
I would like to request that we add to the export options. Currently I have been using "Export to: Same folder as original photo" and then moving the sub-folder it creates in Library View, but it would be great to just have the following option: "Export to: Parent folder of original photo" Here's my use-case... My photography drive structure looks like this: Working Drive Pictures Clients YYYY-MM-DD-ShootName RAW Edited-JPEGs High-Resolution Low-Resolution Rejects When I am editing a shoot, I begin with the RAW files. After culling, I move over all 0-star images to Rejects folder. Next, I perform all basic edits in Lightroom and I then export full-resolution full-quality JPEGs to a folder named Edited-JPEGs which currently goes under the RAW folder, then I manually move it to the parent folder in Library view. Then I do any retouching to the Edited-JPEGs in Photoshop. Once I've completed any retouching I then go back into Lightroom and export H
None of my edits are showing up in the Library View (Loupe or Filmstrip). When I am in Develop, the pictures do include any edits I've made, however, when I switch to the Library Module, it only shows the original image without any edits. Another thing I did notice is while I am in Develop, and the edits are shown, if I hit F and view in Fullscreen, the edits are not there. When I Esc out of fullscreen and back into Develop, the edits are there. I haved already tried:1. Deleting the entire Previews.lrdata folder to force Lightroom to rebuild the previews. It does rebuild as I scroll in Library, but it still shows them without any edits.2. Zooming in and out in Library.3. Discarding and Rebuilding 1:1 previews.4. Optimizing Catalog.5. Signing out of Lightroom and signing back in.6. Restarting Lightroom.7. Restarting Computer. System Info:Lightroom Classic version: 13.0.1 [ 202310121438-d2af310c ]Licens
I’m hoping you might have a suggestion regarding Lightroom Classic metadata behavior.I’m running Lightroom Classic on a Mac and testing LR/Transporter to import keywords from a CSV file.What’s puzzling is that:A single-image import works. A small batch of 5 images works. Larger batches (10+ images) appear to do nothing. No error message is displayed. The images are selected before running the import. The CSV format and field mapping are the same as the tests that worked.While researching, I came across your comments regarding Helper.lrdata and metadata caching issues. It made me wonder whether Lightroom might be accepting metadata changes but not displaying them correctly, or whether a cache issue could make an import appear to fail.Have you ever seen Lightroom Classic behave this way with metadata imported by a plugin, or do you have any suggestions on what to investigate next?Thank you for your time.
Hi everyone, I have a question.I’m using a MacBook Pro M3 Max 16" and recently got an Apple Studio Display. I now work with a dual-screen setup.The problem is that I always use Lightroom, and its window keeps jumping back to the MacBook screen several times a day — even though it's set to full screen on the Studio Display.In System Settings, the Apple Studio Display is selected as the primary monitor.macOS version: 15.5Is anyone else experiencing this issue? Or does anyone know how to fix it?
I am using a Macbook Pro with Lightroom Classic (LRC) 15.5 (latest update). When I originally installed LRC on this Mac, the masking worked fine. However, for the past few weeks, when I go into develop mode and try to use a brush tool (either as a stand alone brush tool or as an add / subtract modification of another mask) i have a problem - when i initially press the mouse button, a circular overlay is displayed as expected. Keeping the mouse button pressed, I then try to extend the mask; the cursor moves but the overlay does not change until I release the mouse button when the overlay is then correctly displayed (reflecting the cursor movement that I made). The overlay function does work correctly on other Macs and Windows versions of LRC and indeed, did work on this particular Macbook.I have tried installing an older version of LRC, clearing the LR preferences, installing LRC with a new catalogue and installing the latest Macos. Also tried disabling the GPU and checked the mask togg
hello,the export in Lightroom Classic 15.3.1 on Mac OS 26.5.1 doesn’t work, and don’t even start. Any suggestion ?
When I’m in the develop module and clicking back and forth through photos, LRC will randomly paste the settings from a previous photo onto the next one. Sometimes it will only change the values (exposure, WB, etc) in the basic settings on the develop panel without actually changing the photo itself. Other times, it will change the photo as well, at which point it will say “multiple settings” in the history. I’m only clicking through them, not applying any changes to them. I’ve also experienced it where I’ll crop one photo and then when I click to the next photo, it will show that same crop on the next photo as if I applied it when I didn’t. When I click into the crop tool, it will show the crop but when I close the crop tool, the crop isn’t actually applied. The sync feature is not on, it happens in multiple catalogs, everything is up to date. It’s hard to replicate and it happens randomly. It will work for a while and then it will start glitching like this randomly. There doesn
foto’s gemaakt op mijn gsm synchroniseren met LR. De synchronisatie met LRC vanuit LR werkt niet meer. hoe kan ik dit oplossen
in Color Mixer, when i click on the drag tool (target adjustment tool?) to enable it, then move the cursor to the image and scroll my mouse wheel, it adjusts the Luminance sliders, but very, very slowly. this started happening a few updates agoi use Windows 11 and and it’s up to date, and i don’t notice this problem anywhere else
Under OS X Sonoma, I was working on some catalogs. Everything was fine until I opened one catalog and it would not let me import new images or close properly (had to force quit). I tried optimizing it unsuccessfully. I tried moving it locally with no success. I tried importing JPGs instead of DNGs. Didn’t work. I went so far as to do complete computer OS reinstall, upgrading to Tahoe. Didn’t work.I eventually completely rebuilt the photo catalog using JPGs. The DNGs seemed to be the problem, but I’m not 100% convinced. I moved on, but I am now realizing that as I work on more catalogs, the same problem is showing up on other catalogs. The big problem is that the catalogs are not fixable. I cannot optimize them. I have tried using the “check for integrity” on load, but it never finishes. It can go for hours trying with no success.Having to completely rebuild catalogs is incredibly time consuming. This was never a problem before. I can open the source files just fine in Photoshop or othe
After updating to LHR classic 14.1.1 LHR stops shwoing metadat in the lybrary module as well as in the developement module (loupe info). Closing LHR and deleting the files: ...Helper.Lrdata, ....Previews.Lrdata as well as ....Sync.Lrdata helps, as they are created each time new when starting LHR. But after working for about 10min all the metadata disapears again. I have installed LRH fresh and reset all settings. Nothings seems to help. I have a attached a screenshot but I wonder if that helps - there is just that spinning wheel. Any suggestions? P.S. I have a large catalog with about 200.000 photos in it but have had no issues so far. Big Windows PC with plenty of power.
I have used Lightroom Classic for nearly 20 years and have a large catalog (about 70,000 images). As you would expect, I’ve also spent countless hours organizing the photos, editing and assigning keywords.A few months ago, I suddenly began to experience a new problem. Suddenly, the “Exif and IPTC” fields on the right side of my screen were all blank (no keywords visible, no location info, no copyright info, etc.). The small “spinning wheel” could be seen but it never stopped spinning.I searched these forums extensively and also many other sites. There were recommendations that included resetting preferences, deleting the metadata helper file, and more. Ultimately, nothing has fixed the problem.I note that deleting the metadata helper.db file does help for a short period. In order words, if I delete it and then start Lightroom Classic, the IPTC and EXIF data reappears, however, after anywhere from 5 to 20 minutes, it disappears again and the spinning wheel returns.In addition, eve
It can take 5 minutes or more for these functions to operate. FYI, I have my files on a 12 TB RAID connected to my iMac.
I have been using Lightroom 5 for some time and just recently my photos are importing out of chronological order. It will import photos from all over the card. They appear in chronological order but they are numbered according to which one was imported first. I can see them in chronological order on my computer but when I hit import through Lightroom the photos are imported and numbered in a non chronological order. This only started happening recently so I think it has to do with a recent update. I've tried formatting my card, using another card, and importing to another catalog, but nothing has changed yet.
Hello Adobe team, I am posting here because I am unable to resolve a persistent Lightroom Classic ↔ Lightroom (cloud) synchronization issue after multiple troubleshooting attempts, and I would appreciate guidance from an engineer or someone who can escalate this if needed. ## Subscription contextI have been an Adobe photography subscriber continuously since approximately 2017, originally through the standalone Lightroom mobile subscription purchased via Google Play. In June 2023, I deliberately migrated to the **Creative Cloud Photography plan with 1 TB** specifically to gain the bidirectional synchronization between Lightroom (cloud) and Lightroom Classic - that capability was the entire reason for the migration, since I wanted to keep editing on a desktop in Classic while having all assets and edits accessible on mobile and on the web. Reliable two-way sync is, for my workflow, the core value of the plan. ## Why I am only now setting up the full Classic ↔ Cloud bridgeI want to addres
When I export a file to jpg with imaging sizing such as 1920 x 1440 px and select include all metadata selected, the resulting file seems not to include some of the brand’s proprietary metadata. I only look at a couple of things, so I don’t know if it is all or just some items.When I export the original, the metadata is available.When I resize in Apple’s Preview, the resulting file also is missing the proprietary metadata.Classic Lightroom v 15.3.1IOS Tahoe 26.5.1 (released last week)Pentax K3-iiiWill all proprietary data be available in future releases?
When I try to print from LR Classic on my up-to-date Mac M4 Mini, the “Roll paper” option is no longer available in the Print Module. Borderless options remain. But when I print with a borderless setting, the images come out only 10” wide, despite being set up larger. I uninstalled/reinstalled the printer (Epson P5300), no luck. I can print from Epson Print Layout fine but want to print from LRC as usual. Any thoughts?
I just upgraded my Mac Air M3 2024 from Sonoma to Sequoia. I have LR 15.3 and PS 27.6. When I try “Edit in..”I get the message The file could not be edited because Adobe Photoshop 2026 could not be launched.I have had this issue before and managed to fix it but not this time. I have read all the suggestions here and in Reddit and tried them outUninstall Lr ; Uninstall PSReinstall Ps first then reinstall Lr - doesn't workI’ve tried uninstalling and reinstalling the other way round - doesn’t workI’ve tried the above combinations with or without saving preferences in Lr and/or PS - doesn't workThe Lr preferences are correct.I dont have any other PS installed and no Betas.Can someone please help - as this is driving me crazy
I am working on an old file from a Nikon D810, and when I use either AI Denoise or Generative Remove, the white balance changes starkly over the whole image. See screenshots below, the only change is that I did a generative remove of the top left blurry section. The same happens with Denoise, though not with Super Resolution. When I try to modify the white balance, it has a clear threshold where adding a single digit to e.g. the tint completely changes the image. This is on Lightroom Classic 15.3.1 on macOS on Apple Silicon. I reimported the image to a clean catalog in case the AI info had somehow been corrupted, but the issue persisted.
Interesting problem:MacOs 26.2, LRC 15.1.1Backup catalog fails if I assign it to a network-NAS-volume. All my photos are on the same NAS-volume and I can read/write without any problem.If I change the backup-location to the internal drive, no problem. Don’t want that, because the LR-catalog itself is on the same drive.I noticed the backup process starting with much enthusiasm, then at about 40% it slows down, but does proceed till the end (compress). And then it gives up with an error message and tells me to check the rights and space (both fine).I recently upgraded LRC from v12 (on older macbook, no upgrade possible due to old MacOS) to this version (on new macbook). The old setup did work with the same NAS without any problem (other than very slow). I did not try a backup v12 on the new macbook.Working around now, backup to the same local internal drive as the catalog itself and copy the backup by hand to the NAS. Anyone has a clue? Thanks for your response!Ernst
Lorsque l’on veut supprimer un élément dans une photo par la suppression générative par exemple, plusieurs variantes sont proposées. Il est difficile de choisir celle-ci dès lors qu’il y a un contour blanc épais autour de la zone à supprimer.
The AI function interferes with my ability to get an answer. It only provides data on unrelated issues.I have been using Lightroom classic for more than a decade. I uploaded about 50 photo files into Lightroom classic a week ago and worked on some of them.Today, they are not listed in the collections panel by date on the left like all of the other files I have uploaded over the years. The newer files are always listed at on the bottom of that panel. I can only find them in the section of files without key words. When I pull them up I get a (File can not be found.) on all of them. I did not move them, at least I did not intend to move them, but thy are not accessible to someone with my limited skill set. Of course, I had to delete them to use my only memory card to update the camera firmware.Is it possible to recover these files? Or am I screwed? Can someone blessed with natural stupidity provide and answer? Thanks
If a plugin calls catalog:updateAISettings() immediately after photo:applyDevelopPreset(), the application of the preset is ignored. This bug was introduced in LR 15.3, likely with the background processing of AI commands. To reproduce on LR 15.3 / Mac OS 26.4.1: 1. Import the attached preset “_Update Bug.xmp”. 2. Put the attached file “updateaisettings-bug.txt” into the LR Scripts folder. 3. Go to Develop with a test photo. 4. Do Scripts > updateaisettings-bug. Observe that Exposure is not changed (incorrect -- it should change to 4). 5. Apply the preset “_Update Bug”. Observe that Exposure changes to 4 (correct). A workaround is to call LrTasks.sleep (0.1) before calling catalog:updateAISettings().
The Lightroom Catalog now has a sidecar file called 'lrcat-data', which I understand stores data calculated from AI operations such as masking and denoise. Since the denoise feature was updated to store the resulting data in the catalog instead of a DNG file, the size of lrcat-data has ballooned to unreasonable size for many users, myself included. Given we can only expect this to grow, Adobe needs to give us options to better manage this, such as manually or automatically deleting this data from the catalog similar to how previews are handled. If the data is needed again it can be recalculated or loaded from sidecar files (storing it in sidecar files is already supported). I expect this is already in the works. But there is another issue which I don't think has been raised, which is that the lrcat-data files is structured as some sort of blob archive and, at least for me, is very very slow to copy. You can reproduce this by copying the file on to a fast external SSD, and
In LRC and ACR can’t apply Adaptive Color profile. In LRC nothing happened in preview (no image change, but when copying settings form earlier images that used this setting you get error information “Failed to apply adjustment to following photos. An unexpected error occurred while processing. (1)” then name of image.In ACR I got “Could not update all AI Settings” error.It worked on v.14.x version and older ARC. Also if Adaptive Profile was applied it is still possible to edit this image correctly.Strangely didn’t found problems with other AI features (masking, de-noise, depth blur, etc), that seem more AI heavy. My config:Lightroom Classic version: 15.3.1 [ 202605261338-e36f8566 ]License: Creative CloudLanguage setting: en-PLOperating system: Mac OS 15Version: 15.7.7 [24G720]Application architecture: x64Logical processor count: 8Processor speed: 2,0GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.213Power Source: Plugged In, 100%Built-in memory: 16 384,0 MBDedicated GPU memory used
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.