Lightroom Classic

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

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?

HiIf I import an image into LrC from my iPad Photos (the iPad is plugged into my Mac) it has a filename, call it filenameA, which differs from if I Import the same image into LrM on my iPad, call it filenameB?If I export the same image as an unmodified original from Photos on my Mac it has filenameB.If I import the same file into Lr on my Mac from my plugged in iPad it has filenameA.So my question is can anyone explain why LrC and Lr, on my Mac, is seeing a different image filename when importing from a plugged in Apple device?Thank you for your help. 

When closing LightRoom Classic, this application creates a bakckup file. Sometimes, it does work ...Two cases1) backup stored on internal disk (APFS format) : OKThe zip file contains 2 elements : the catalog, a file named Photos 2022 et +.lrcat, a folder Photos 2022 et +. lrcat-data 2) backup stored on an external disk ‘SSD disk as Sandisk Extrem Pro or hard disk as La Cie USB 3) (ExFAT format) : WRONGThe zip file contains 4 elements : a catalog file named Photos 2022 et +.lrcat, a folder Photos 2022 et +. lrcat-data 2 additional fles (temp files) Photos 2022 et +.lrcat-shm et Photos 2022 et +.lrcat-wal  At end of closure operation, catalog folder is correct : a file named Photos 2022 et + Helper.lrdata, a file named Photos 2022 et + Previews.lrdata, a catalog file named Photos 2022 et +.lrcat, a folder Photos 2022 et +. lrcat-data  Informations systèmeNom du modèle : Mac miniPuce : Apple M4  - Mémoire : 24 Go Informations sur le logiciel LightRoom ClassicVersion Lightroom 

I have many .mp4 videos in Lightroom Classic. But they are not syncing to Lightroom. What codec or format do I need to convert for them to sync ? 

This started after the update.

Request for additional feature, or update of current feature, as Auto (Automatically straighten the photo) is not aligning angle for each of selected photos even if Auto sync option is enabled. Auto sync option apply same angle to all photos. Solutions Within Transformation (like Level) never return as good results.Alternative - offer a keyboard shortcut for this feature.This would drastically change work flow for many of action photographers with fast changing scenes. 

I used LR Classic three weeks ago and changed nothing on my computer since then, except that I stupidly agreed to letting Adobe mess with my stored photos when I opened LRC just now.  After they messed around ("upgrading" they call it in fine Orwellian fashion), I find that most of my folders have little question marks (see attachment) on them and while the photos seem ok in Library mode, they show the warning "File could not be found" in the Develop mode.  What's going on?  running: Mac OS Big Sur 

Bug DescriptionSummaryCatalog conversion from Lightroom Classic v14 to v15 consistently fails when the keyword hierarchy contains keywords starting with Scandinavian characters (ä, ö).If all such keywords are removed in v14 prior to conversion, the catalog converts successfully to v15.This strongly indicates a Unicode normalization or unique-index conflict during schema migration.Environment Lightroom Classic v14 (latest build) Lightroom Classic v15 (latest build) Windows 11 NTFS file system Catalog size: ~2.2 GB ~162,000 images Large hierarchical keyword structure Face recognition enabled Exact Error MessageDuring conversion:"Lightroom encountered problems when trying to update the format of the catalog file and cannot use this catalog in this version of Lightroom."No error code is provided.Observed Behavior The v14 catalog works perfectly. Integrity test and Optimize report no issues. All backups behave identically. Conversion to v15 always fails. Removing keywo

LR fails to normalize the Unicode text of keyword names and allows the creation of two keywords that are canonically equivalent, with the same appearance and meaning under the Unicode standard. To reproduce on LR 15.2 / Mac OS 26.2: 1. Open the attached file “keywords.txt” in a Unicode-compliant text editor (e.g. Textedit or Notepad). 2. In LR’s Keyword List panel, click + to create a keyword, and copy/paste the first line from the file into the keyword’s name. 3. Repeat for the second line of the file. 4. Observe there are two keywords with the same name, as defined by the Unicode standard: The two lines of the text file use different canonically equivalent Unicode representations for the same letter: U+00F6 (LATIN SMALL LETTER O WITH DIAERESIS)U+006F (LATIN SMALL LETTER O) + U+0308 (COMBINING DIAERESIS) Such keywords tripped up this user’s catalog upgrade from LR 14 to LR 15:In that case, we were unable to construct a test case that failed other than on his computer. There is a simil

So, I’ve been down this rabbit hold before (starting in Mid-Dec 2025) but Adobe stopped responding and now my original post has been deleted.I’ve been through several people and tried all of their suggestions but still see the attached. Help!   

So, I have used AI masking to detect the clothes on a subject, and I am using Point Color to change some of the colors on those clothes. I want to turn up the saturation on the green spots on a military suit.   Now, as a test, just to make sure the change is noticeable, I turned the hue all the way to the left, basically the military green is now cherry red. This is only to make sure I am not going blind and that I have actually found a bug.I am NOT using global point color because I have tested global point color with the military green and if I am using global point color then half the image becomes red. When I am using just the chothes mask then only the green spots become red.   If I then export as JPG then the point color is fully ignored. If I export as PNG things behave as expected (with minor color differences)I also tested this with saturation. I turned the saturation of the military green to 0 in the point color, making it gray, exported as JPG, camo spots are green

‘compare’ has a lock, which(unlocked) allows independent movement of each image.  Is there a shortcut key to toggle to lock on/off?

Ich nutze die neuste Version von Lightroom Classic und musste mir eine neue Bibliothek anlegen.Beim Importieren der Nikon NEF-Dateien mit XMP-Dateien musste ich feststellen, dass in der neuen Bibliothek die dazumal (ab 2022) getätigte Bildbearbeitung inkl. Bewertung nicht übernommen wurde.Auch ein nachträgliches Einlesen der Metadaten über (Metadaten / Metadaten aus Datei lesen) hat nicht weitergeholfen.Ich wäre froh, wenn man dieses Problem lösen könnte. Ansonsten habe ich seit 2022 all meine Bildbearbeitungen und Bewertungen verloren.

Still randomly receiving error messages when re-ordering a small batch of photos within a collection. LR tells me that it can’t (paraphrasing) move photos from disk in a collection...This has been an error I’ve encountered for many different versions of LR Classic over the years and have posted several times about it already.   Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.4GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171CPU Utilisation: 2.0%Power Source: Plugged InBuilt-in memory: 65292.0 MBDedicated GPU memory used by Lightroom: 203.7MB / 15995.0MB (1%)Real memory available to Lightroom: 65292.0 MBReal memory used by Lightroom: 1364.7 MB (2.0%)Virtual memory used by Lightroom: 1633.4 MBGDI objects count: 787USER objects count: 2771Process handles count: 3129M