Connect with fellow editors in our Lr Classic community.
Recently active
I am currently using Lightroom Classic v14.0.1 on Windows 11. Flat Field Correction has been working previously on scanned negatives. However, when I try to use it now there appears to be no affect or alteration of the files. The "task bar" in the top left corner appears to finish, but there is no correction applied nor is the DNG file created. I have verified by checking the source folder for a DNG file, looking at photo in library and develop tab, tried various layouts (correction image first and last), correcting one photo to multiple, tried different locations, restarting PC, etc. Is this a recent bug? I am using the same workflow as before and it appears to be broken right now.
Lightroom Mobile – Unable to Save Presets (Error #20190613a) Device: iPhoneApp: Adobe Lightroom MobileError Code: #20190613a Description:When attempting to save a preset in Lightroom Mobile, the application fails and displays the message: “ERROR #20190613a”. The preset is not saved and the action cannot be completed.
Has anyone else experienced losing the colour labelling after Lr Updates? This has been going on for years, but because it was more annoying than "mission" critical, I've been ignoring it. It's finally reached the top of my Bug List. Nonetheless, what's with that? Please fix it, it's moved past annoying.
I’m currently stuck with macOS Monterey. Is there a way to install older version of Lightroom Classic?
I am trying to import phots from my camera into lightroom classic but keep getting a message saying either: “could not copy a file to the destination folder because it is not writable”or I am using a MacBook Pro with macOS Sequoia version 15.7.4I am using Adobe Lightroom Classic Release 15.2Destination Drive is an external Hard Drive which has all my Library PhotosCatalog is in the “Lightroom” folder inside the “Pictures” folder on my Mac I have already checked/done the following with no result:The destination drive is not full and has sufficient space still available for the photos being imported The folder into which I am trying to import the file has read and write permission in mac os Adobe Lightroom Classic has “Full Disk Access” under mac OS Settings/Privacy & Security Settings I have tried “Clear Recent Paths” in the Destination Folder I have tried unticking “Make a Second Copy To : ” in the File Handling section and then importing I have tried ticking “Make a Second Copy To
When I upload to Blurb from LRc 15.2, random photos will have horizontal blue-green lines running through them...if I upload again, different photos will have the lines...I’ve checked my fonts and padding (none) and can’t fine any apparent issues with any photos...how can I fix this?
My system info is included below.I am frequently in the position where I am happily using Lightroom and then suddenly everything in Develop starts to run at a snails pace. The Lightroom CPU load is constantly running at 20-30% even when I am doing nothing at all. Restarting Lightroom will return things to normal for a few minutes and then I am back where I started. I have even exported a subset of images to a new catalog and the same thing is happening.Application and catalog are both on an NVME SSD which is only 50% full. I have disabled the majority of plugins. Nvidia Studio drivers are up to date. Lightroom and Camera Raw are up to date.The system is clearly powerful enough to smoothly run Lightroom…..until it isn’t, which is driving me crazy. SYSTEM INFO <Attached by mod>
Invoking the Library Filter bar’s Restore Default Presets creates duplicates of the built-in filter presets. To reproduce in LR 15.2 / Mac OS 26.2: 1. Set the option Preferences > Presets > Store Presets With This Catalog. 2. Open the attached catalog “filter-presets-bug”. 3. In the Library Filter bar, click the drop-down menu and do Restore Default Presets. Observe that the built-in presets Default Columns, Filters Off, and Location Columns have been duplicated. Examining those presets’ .lrtemplate files, the contents of the duplicates are identical. Before and after of the drop-down menu:
My experience with LR sync has has been very disappointing. I have LR on my 13Pro set up to import every photo from the camera roll. I see the DNGs in the LR app on my phone. After a short time they will appear on my iPad. But to see them in LR Classic on my desktop (mac) can be any where from a few minutes (not usually) to a couple of hours (more likely). For instance I shot 3 images (DNG) at noon this morning and 9 hours later they are still not synced to Classic.In the past I've quit and reopened LR, paused and restarted Sync, and I've also deleted all Sync data. Sometimes these actions work, sometimes not.All I want is to have what I shoot on my phone apear on my desktop and I have no clue at this point how to have that consistently happen. MacOS 12.7.2/LR Classic 13.1
Every time I try to remove something using generative AI on Lightroom Classic, I suddenly now get “!Generative Remove Failed. Something went wrong. Please Try again”I have restarted Lightroom, and my computer. Logged out and back in.This worked before, and this suddenly started happening.
My latest photoshoot was a LipSync competition shot o my Nikon Z8 for some of the images as soon as i select to develop the image is covered in streaks of colour and I cannot remove them!!
The locked photo stops me from doing anything with LRC.
Is it possible that you can place 2 watermarks/logos in the watermark edit. So place a watermark at the top right and bottom right at the same time. Thanks, Roy Froma
I am having issues using the Generative AI features of both Lightroom Classic and Photoshop.When I try to remove anything from my image using the Remove tool with Generative AI box checked in the Lightroom Classic, it never works. This problem started to happen a few weeks ago. The error dialog does not show anything about internet (as many people had before and posted in this community). The error is the one attached.The same problem happens when I try to remove or generate anything in Photoshop. I also attached the snapshot of the photoshop problem.Something might be wrong with the server of Adobe, because another symptoms are appearing to me, for example, the Catalog stopped to sync. It shows the loading circle but it never finishes. Another example, I am unable to load my plans or public profile using Chrome. It shows "Unable to load data" for almost any tab of my Adobe Account.For more info on the system, I am using a Mac M1 with macOs Sonoma 14.7, the Lightroom Classic is 13.5.1
After upgrading Adobe Lightroom Classic to version 15.2, selecting or switching between photos in the Develop module is still laggy.When I move to the next photo (using arrow keys or clicking another image), there is a noticeable delay before the image loads. This makes editing slower than before.My system: Mac (Apple Silicon) M2 Max macOS Sequoia 15.7.3 Has this issue been fixed in version 15.2, or are there any recommended settings to improve performance in the Develop module?Any suggestions would be appreciated.
Just installed the opdate for LRC 14: Since then the slideshow does not work anymore. An Error Message Apears "Dynamic Link-Medienserver konnte nicht gestartet werden" (Dynamic linc media server could not be launched). Tried a full re-install fron scratch - even with empty catalogue. Problem persists.
Same Problme help me, please
Dear,I am really confused about this. I have made an export filter that modifies the size settings in the export dialog, waits the rendering and then makes some stuff. It works ok when I click on the photo and then use "Export..." button. The problem happens when I use "Export with previous", in that case it seems to not use the filterSettings function.This is a dummy code, it just modifies the rendering size and then do nothing. If I export with the "Export..." button, the export dialog appears and the photo is rendered to fit 100x100 pixels as stated in filterSettings. If after that I use "Export with previous" button, the dialog does not appear (this is ok), but the rendering is made without overriding the user settings for the image size; it works as if filterSettings function were empty. postProcessRenderedPhotos= function ( functionContext, filterContext ) local properties=filterContext.propertyTable local renditionOptions = { plugin = _PLUGIN, renditionsToS
Feature: allow users to provide criteria for name-space search (face-name matches) that exclude (prefer) according to user-specified criteria. Most important criteria for matching is capture time, but other criteria (keyword / keyword groups, for example) could be used. Fuzzy logic implementation would also be possible (e.g. heavily weight likely results by year of capture, presence in collections/collection sets, etc)This will GREATLY reduce the number of false-positive matches.Example using capture time:-User has large catalog containing many photographs, including images going many years.-Selects a group of photos (by collection set, folder years, search criteria, etc) that all have capture times of 2025.-In suggested matches, Lightroom currently displays potential matches for names that are only in images prior to 2005 (real world example). -Provide an option for user to specify capture-time periods (eg 2020-present), and the number of false matches drops dramatically. -All of this
Hi,I am unable to use denoiser on my Mac with M1. When I click denoise, I get progress bar which disappears after a while and then denoise is unticked. After that denoise instantly untick when I try to tick it. No usefull data is provided by CMD output of the lightroom. Systeminfo:Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: en-GBOperating system: Mac OS 26Version: 26.3.0 [25D125]Application architecture: arm64Logical processor count: 8Processor speed: NASqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171Power Source: Plugged In, 36%, ChargingBuilt-in memory: 16 384,0 MBDedicated GPU memory used by Lightroom: 7 365,1MB / 12 124,1MB (60%)Real memory available to Lightroom: 16 384,0 MBReal memory used by Lightroom: 496,1 MB (3,0%)Virtual memory used by Lightroom: 428 609,6 MBMemory cache size: 344,7MBInternal Camera Raw version: 18.2 [ 2482 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2Camera Raw virtual
After closing a LRC session I noticed that — totally out of the blue — the file modification dates of the jpeg files in a directory had been updated to more-or-less precisely the time I had moved (within LRC itself) some other images in that folder. Upon inspection (exiftool) it turns out that the metadata of the files has indeed been changed. Only the files that were already in that directory were changed, not the files I moved in. I moved around files also in many other directories, but only that one was randomly affected. As an example, the attached diff output shows the differences between the tags of one of the modified files and its original copy (of which I had a backup).
I have installed/activated some Adobe fonts. They show up in Photoshop, but why won’t they appear in the Slideshow module in Lightroom Classic? Shouldn’t the fonts work in all Adobe applications?
I upgraded to LR CC 15.2. The message "the file is not found" appears when I switch from Library to Develop module. The photos are recognized in the Library module as the “!” does not appear.. I am using Sequoia 15.7.4.
So in the import dialog I have set to import using Camera settings. My camera s set to its default standard picture control. After import, all the images have setting altered in the develop module. like exposre is set to +.33 contrast +9 highlights to -21 and these are greayed value to using the reset button restores to these values. Changing profile does not change any of these values so they are definely set at import.
seit dem gestrigen update startet LrC nicht mehr.es kommt die Fehlermeldung "mfc140u.dll" fehlt. Wie kann man das beheben?
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.