Lightroom Classic

Seit dem Update auf 15.2 funktioniert die Maskierung von Personen nicht mehr, selbst auf Bildern im Katalog auf denen Personen zuvor erkannt worden sind. Es erscheint stattdessen "Keine Personen gefunden".

Is it possible to options to context menus with lightroom SDK? I can add menu entries in the menu bar, but it would be much satisfiyng if I can right click on a photo/collection and the my menu appears there.

I'm attaching a screenshot of what Spotlight shows under the Apps icon on the task bar.Adobe Creative Cloud installs ten (10) separate "helper apps" under Applications,  It's mess.Could Adobe at lease consider recoding these so they only appear under "Other"?  

My lrcat-lrdata folder is corrupted, online i read to delete it and lightroom would reacreate it but it did not fix the issue. Now if I open the pictures in the develop module i see an uknown error shown but my edits are loaded as the values are shown on the slider but they are greyed out. I contacted support but they told me to remove and reimport the pictures but it’s quite useless as I would lose all my work and all the settings since they are not saved as xmp. I cannot export the xmps now and it says I/O error if i try to do so.

Since the update to LR 15, I am having a frustrating problem with grid view, where tint grid cells with label colors is no longer working for items that were previously tinted. Instead in the upper left corner of each of the image grid windows, it will say “[Color label name]/[number of stars]” in the upper left corner. For example if I had it labeled red with 3 stars it will say “Red/3,” and if it is yellow with one star it will say “Yellow/1.”  The stars do show up with the image, as do the flags, but not the color tint. I can add the tint by selecting the image and tapping the associated color number. For example, I select images  that have Yellow in the upper corner and tap the 7 key and it adds the tint and changes the text to “Yellow_Published” which is a nice idea to include the word “Published” which is what Yellow signifies to me. The screenshot of grid view attached shows what all the images look like now (left) and what happens if I hit the 7 key (right). But I have tens of

There is zero activity on my machine while waiting for Lightroom to open,  When it did open I ran the diagnostics and found this of interest,  it correlates to the wait time,  in the middle it mentions the user id key ?2026-01-29T17:12:31Z: cloud model cache refresh failed: 2000072026-01-29T17:12:33Z: cloud model cache refresh failed: 2000072026-01-29T17:12:36Z: cloud model cache refresh failed: 2000072026-01-29T17:12:39Z: cloud model cache refresh failed: 2000072026-01-29T17:12:42Z: cloud model cache refresh failed: 2000072026-01-29T17:12:45Z: cloud model cache refresh failed: 2000072026-01-29T17:12:48Z: cloud model cache refresh failed: 2000072026-01-29T17:12:51Z: cloud model cache refresh failed: 2000072026-01-29T17:12:54Z: cloud model cache refresh failed: 2000072026-01-29T17:12:58Z: cloud model cache refresh failed: 2000072026-01-29T17:13:01Z: cloud model cache refresh failed: 2000072026-01-29T17:13:04Z: cloud model cache refresh failed: 2000072026-01-29T17:13:07Z: cloud model cac

Nikon Z8 Camera lens Nikon AF Nikkor 24-70mm F/4S is not listed in the supported lens list for Lightroom Classic 15.2 version. In LRc 15.2 in the Develop Module in the Len correction panel the Lens is not showing although we open a Nikon .nef file format. This specific lens was released on 23 August, 2018.

During export I want to rename my exported images to <uuid>.jpg.Is there a smarter way then my code below?exportPath = "D:/Temp"for i, rendition in exportSession:renditions(renditionParams) do -- Wait for the upstream task to finish its work on this photo. local success, pathOrMessage = rendition:waitForRender() if (success == true) then local newFileName = LrPathUtils.child(exportPath, rendition.photo:getRawMetadata("uuid") .. ".jpg") local result, message = LrFileUtils.move(pathOrMessage, newFileName) endend 

Example of the issue: ISO 250 EXPOSURE:+2.00 AI Denoise 50%When running denoise and raising exposure on my X-H2, I notice a pattern of colorful artifacts throughout the darker areas of the image. The above image was a screenshot taken at 300% zoom to visualise it more readily, but it is visible at 100% zoom (and persists after exporting to jpeg). The behavior is present on all photos I have tested. This does not occur when using the DxO demosaic/denoise algorithms, so I do not think it’s an inherent flaw of the photo. Is there a way to fix this? Software: Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Business EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 12Processor speed: 4.7GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171CPU Utilisation: 2.0%Power Source: Plugged InBuilt-in memory: 31814.8 MBDedicated GPU memory used by Lightroom: 5238.7

Hardware:Mac Mini M4 Pro with 24 GB RAM and 16 GPU cores. The same issue also occurs on an M1 Pro. Lightroom Classic 15.2 macOS Tahoe 26.3 RAW ARW files from Sony A1, A9ii and A9i as well as compressed DNG converted files behave similarly. GPU acceleration is enabled in Preferences > PerformanceObserved behavior with AI Denoise Lightroom Classic Denoising a single image via the Detail panel is very fast: 5–7 seconds. When batch-processing even just 2 images, the first image processes quickly (normal speed), but the second image takes 38–40 seconds — about 5× slower. In larger batches (e.g., 100 images), the first image remains fast, but all subsequent images (the remaining 99) are consistently slow. Creating a preset that applies only Denoise and applying it to a single image results in the slow processing time (~40 seconds). Denoising one image quickly, then syncing that setting to another image, is also very slow.Workaround comparison: Manually scrolling through thumbnails and cli

Than I selected next photo with Crop Tool activated, Crop tool switched to Zoom Tool but crop marks remains visible and Crop tool panel turns grey. I need to turn off and on Crop Tool to make it work again.LrC 15.2, Intel Mac, the same issue was in previous version too 

Lightroom Classic version: 15.0.1 [ 202511041508-dddee541 ] License: Creative Cloud Language setting: en Operating system: Windows 11 - Home Premium Edition Version: 11.0.26200 Application architecture: x64 System architecture: x64 Logical processor count: 16 Processor speed: 3.6GHz SqLite Version: 3.36.0 Adobe GSDK Version: 1.4.0.171   CPU Utilisation: 1.0% Power Source: Plugged In Built-in memory: 32122.7 MB Dedicated GPU memory used by Lightroom: 1961.9MB / 128.0MB (1532%) Real memory available to Lightroom: 32122.7 MB Real memory used by Lightroom: 3739.5 MB (11.6%) Virtual memory used by Lightroom: 4036.5 MB GDI objects count: 831 USER objects count: 2940 Process handles count: 2528 Memory cache size: 530.6MB Internal Camera Raw version: 18.0 [ 2389 ] Maximum thread count used by Camera Raw: 5 Camera Raw SIMD optimization: SSE2,AVX,AVX2 Camera Raw virtual memory: 266MB / 16061MB (1%) Camera Raw real memory: 499MB / 32122MB (1%)   Cache1:  Final1- RAM:285.0MB, VRAM:8

Lightroom Classic 15.11:It appears that when I clicked “update” to move from 15.1 to 15.11 somethig went wromg. All of a dden it would not launch Lightroom Classic, independantly or fromAdobe CC. The logs for the crash are in the attachments.Re-installed everything, cleared everything I can think of clearing, restarted 50 times. PS launches just fine. ( can’t attach, this is the Lightroom Console from today:-Lightroom Console Tue Jan 27 17:26:23 2026Registered console log with WER: C:\Users\Bob\AppData\Roaming\Adobe\Lightroom\lrc_console.logDBGHELP: Symbol Search Path: .DBGHELP: .\ntdll.pdb - file not foundDBGHELP: .\dll\ntdll.pdb - file not foundDBGHELP: .\symbols\dll\ntdll.pdb - file not foundDBGHELP: ntdll.pdb - file not foundDBGHELP: ntdll - export symbolsDBGHELP: .\kernelbase.pdb - file not foundDBGHELP: .\dll\kernelbase.pdb - file not foundDBGHELP: .\symbols\dll\kernelbase.pdb - file not foundDBGHELP: kernelbase.pdb - file not foundDBGHELP: KERNELBASE - export symbolsDBGHELP: .\m

My problem is described in an previous,elaborate post (Lightroom Classic automatically restores all changes done on "develop" module) although I am using a Mac M5 OS 15.1.Library module does not automatically read and implement edits made and recorded in history until manual click on history thus I must navigate to Develop module and navigate to left-most panel in history, which is inevitably at the bottom, then scroll up to historyThis is time consuming, frustrating and maddening.Even if the LR tecs can’t fix this problem, which I believe is shared by many judging from the past, perhaps they could add a toggle in library that automatically updates history in the Library module. 

This is the lamest community bulletin board software ever implemented.  Way too hard to just give Adobe a rarely deserved compliment.  Adobe is so lame at all but a few things.

LR 15.2 introduced inconsistent names for the Backspace and Delete keys in the French in-program shortcut help. WindowsLibrary Help:Map Help:“Supprimer” is French for the Delete key. But on Windows, the Backspace key is called “Retour arrière”. MacLibrary HelpMap Help: On Mac, the Delete key is called “Supprimer”. So the two instances of “Arrière” should be replaced by “Supprimer”. 

I have a query about being unable to 'Vote' for a post in 'Questions'.In the previous version of the forum we could vote on a discussion (now 'Questions').  Some discussions had many, many votes, showing that a lot of users had the same problem as the initial poster.  The number of votes was an indication that it should probably be investigated by Adobe or could even potentially be a bug.As I understand it, a discussion is not moved to bugs until it can be reproduced by Adobe (see a couple of posts by ​@Rikk Flohr_Photography at the top of the 'All posts' page).  It can take a very long time for Adobe to acknowledge an issue as a bug, so how do we now indicate in 'Questions' that we also have the same problem?  If the answer is to click 'Like', then to my mind this is not really the same as upvoting to indicate that you have the same problem.  It just means that you like the post!  Can the option to ‘Vote’ be reinstated in ‘Questions’?

Navigation highlighting anomaly | Adobe DME

With the latest updates to LrC/Lr (Generative Video from still/Generative Edit in Firefly/Generative Upscale with Topaz Gigapixel), it seems Adobe is focused more on Adding Gen Ai features (some that no one seems to want - based on Adobe forum and YouTube review comments).Wouldn’t it be better to focus more on actually improving both the stability and performance of their software?My personal observation - the more Ai features they add, the slower their software (including Photoshop) becomes, and the more resources it demands.

LRC becomes very slow, unresponsive, and laggy shortly after launching. This problem was discussed on the previous forum extensively, where many users from Mac and Windows platforms reported it. Apparently, there were several different causes for the problem, as some users were able to fix it by following diverse suggestions, which did not work for other users. I am one of the unlucky users who tried all suggested fixes and could not solve the problem or find its cause. Unfortunately, a couple of the threads were marked as Resolved (or Answered) and the discussions stopped. I have been trying every new version of LRC as they become available, but in my case the problem persists and actually becomes worse with versions 15.2 or the previous one, 15.1.1. So, I am back to version 15.1, which at least lets me work for about 30 minutes before the program becomes essentially  unresponsive. My question is, will this problem ever be fixed by Adobe? 

The menu item  Map > Tracklog > Auto-Tag Photos is always greyed out, even though the toolbar's Lightning Bolt > Auto-Tag n Selected Photos is not.  This bug has been present since at least LR 9.1. To reproduce:   1. In the Map module, load this tracklog: https://www.dropbox.com/scl/fi/c4mtos3k945v3z8kcamgi/Big-Lake-2023-Tracks.GPX?rlkey=18dxvhr56v0i45ib1amitgylx&dl=0   2. Select one or more photos in the filmstrip.   3. Observe that Map > Tracklog > Auto-Tag Photos is greyed out.   4. Observe that the toolbar's Lightning Bolt > Auto-Tag n Selected Photos is not greyed out.   Tested on LR 12.5 Mac OS 13.5.1 and Windows 11; LR 9.1 Mac OS 13.5.1.    

I wanted to create previews to speed up Lightoom loading images in Library and now all my pictures are ruined by some smudges that were applied to the images. Se attached screen shot. I did not do anything. It happened after generating previews. What happened and how do I restore my original images?Viewing a single image I see this in the history. I repeat, I did not do that.What happened and why?All 2500+ pictures have been ruined by this...It drives me insane…. UPDATE:I see that Develop Settings from one photo that I edited were applied to all my pictures. How do I revert that?

Seriously Adobe, do we need to delay updates until someone tells us no core features have been broken/removed? What is going on with quality assurance.Since the update I can’t drag and drop to move photos or ad them to collection, this is a really serious usability impact.And don’t even start on telling me this is by design…How do I even add a photo to an existing collection without drag and drop?