Lightroom Classic

when using        photo:applyDevelopPreset(preset)​    with a preset containing AI Settings, this will trigger the calculating ai settings dialog in newer LrC versions most of the times.     Issue 1) When calling LrTasks.sleep(1) immediately after the call and keeping the withWriteAccess lock some time does prevent the dialog from showing up and seems to bring LrC in a state where it won't show the dialog anymore even without the LrTasks.sleep(1). This seems pretty random to me (maybe some race condition). But sometimes my LrC is in a state where it won't trigger the dialog. This is rather annoying and inconvinient, but the more serious issue is:   Issue 2) When LrC does show the dialog, it seems to show it for every photo separately, leading to many dialogs popping up and blocking each other as seen in my screenshot     One cannot cancel the below dialogs and when trying to cancel the frontmost it just sits in the "stopping" stat

Windows 10, Lightroom Classic 14.0.1, going from library Grid view to Full screen view (F key), the app displays a black screen (instead of the image) IF the previous state of the picture was zoomed in with loupe view.  Switching to loupe view (E key) displays the image in the zoomed state; then switching back to full screen then displays correctly.  This behavior is frequent, but not consistent.

Title says it. Ever since the latest update both cloud and classic have been running extremely slow and unstable. I was told yesterday by an adobe "engineer" that there was a technical outage on their end. Now I'm experiencing extremely long sync times.  On another note, can we all just talk about adobe has twilight zone levels of customer support? They are abysmal, no one knows what theyre talking about, you call and you can hardly hear them over the cacophony going on in their "offices". No one cares, they just transfer you and kick the can down the road. I'm waiting patiently for another company to end their monopoly so I end my 10 year toxic relationship with adobe. 

I just updated to version 14 of Lightroom Classic and now, when I try to export certain images from a collection, the export doesn't work.  I was also unable to edit those images in Photoshop.  It seems to be restricted to DNG files taken with my iPhone and doesn't occur with all DNGs.  I was able to export them using regular Lightroom going to Local and finding the files but not from LR Classic.  Anyone else have this problem?

Since said update, LR goes into "not responding" mode with CPU usage "very high" and does not come back. Killing the LR task and restarting does not help.    System: Ryzen 9 5900X, 64 GB, GeForce RTX 3060 with latest Studio Driver   Any ideas?

Hello, I try to use a combo_box with a binding for the items:     local function main() LrFunctionContext.callWithContext('showDialog', function(context) local props = LrBinding.makePropertyTable( context ) props.items = { '1', '2', '3'} props.value = '' logDebug('main', '#Items = ' .. #props.items ) local f = LrView.osFactory() local view = f:column { bind_to_object = props, f:row{ f:combo_box{ items = LrView.bind('items'), value = LrView.bind('value'), width = 50 }, f:push_button{ title = 'Remove', action = function() if #props.items > 1 then table.remove(props.items, #props.items ) end logDebug('main', 'After remove #Items = ' .. #props.items ) end, }, }, } status = LrDialogs.presentModalDialog { title = 'test combo box', contents = view, } end ) end     Initially all three items are

Every time I start LR classic 14.1 on my M1 Mac (macOS 15.1) the colured spinning ball starts ~ 1 minute after loading & LR is thereafter non-responsive.   I have uninstalled & re-installed LR I have spoken to Adobe twice for 2 hours each time. Turning off everything in the start up menu and sequentially reinstalling and rebooting each time did work initally Setting up a new profile is to no avail. As soon as I am asked to log in to Adobe it crashes.   Does anybody have any idea what is going on. LRC works on my Macbook Pro?   This started on 20th October and is driving me mad.   Apple have tested the system integrity and cannot find any problems

Sorry if this is a known Issue, I've tried to find a Bug Report related to Sync Issues and IPTC Metadata being overwritten but...   This issue started with the August release of Lightroom desktop 13.5   What I have found is that if you have a file that is synced to the Cloud and you change the IPTC Metadata in LR Desktop, when the file is re-sync with Creative Cloud. The metadata will be over written by the old Creative Cloud data.   i’m not sure if it’s every field that has been this issue but I do know for sure that:   Copy Name Title   Are definitely being over written.   (When sink is enabled on the collection; I will change one of those fields and 5-10 seconds later, The old metadata repopulates the field)   In addition to this issue sink is corrupting some of my Photoshop files.   in recent days, I have found a half a dozen files that have been corrupted by sink when I reopen them in Photoshop I get this error message.   “This file c

I can open Lightroom Classic and use the Library module, but as soon as i select a pic (CR2 format) and click on the Develop tab... the app crashes. How do I fix this?

[I've verified this bug still exists in LR 10.0. See this post. -- John Ellis] After a while of custom sorting the order of photos and stacks within a collection (using Grid View), Lightroom starts to unpredictably refuse to sort photos. Some will get positioned where I drop them, others won't move at all and yet others will get positioned somewhere close by (eg. 4 or 5 photos before or after).After digging into the catalog file I've come across what I think is the problem, but don't know how to fix it. In the attached file you'll see a screenshot of the database table for the collection, you'll see I've hilited the images that are part of the same collection, but their positionId is identical (which should never happen I'm assuming), probably due to the field size reaching it's maximum length. This is what I believe is causing the problem. Tested this on both Lightroom 5.7 and CC 2015.8.This is a major bug and effectively stops user sorting from being functional, as well as now h

Did a job yesterday and got home to edit the photos.. Immediately after importing the images (.CR2 Raw files from Canon 5DS) Lightroom started struggling to perform ANY action..  even going to the next frame in the film strip took several seconds, with a few short appearances of the spinning beach ball.. Editing was practically impossible - trying to crop an image and move the crop rectangle was taking about 15 seconds to update the frame position..   I looked what 'activity' was happening behind the identity plate at the top left and it was "saving xmp for xx photos" (xx was a number between 25-80 something)..  but then if I moved to the next frame, it repeated - "saving xmp for xx photos"...Everytime I perform ANY action, it's saving XMP to multiple photos - even though I only have one photo selected in the strip. If I switch from library to develop, it again saves XMP to multiple photos - without me changing ANYTHING...   Why is Lightroom constantly writing

Tested in 14.0 - and 14.0.1... - Macbook Pro M1 Max, 64gb RAM, OS Sonoma 14.6.1   When using a second display (in Loupe Normal, FULL SCREEN mode), making any edits such as those in the basic panel for example, or local brush adjustments, mask adjustments etc aren't reflected in the secondary display - the edits just aren't applied to the image on the second screen. Moving to another image and back will update the secondary display and show the edits, or if you remain on the image - enabling the crop tool and making a slight change to the crop area will also force the second display to update with the edits - otherwise the image shown on the second display remains unchanged (although the changes are applied to the actual image).   Note: Only applies when secondary display is in full screen mode. If you disable full screen mode so the secondary display is in a window, then the edits are reflected live. 

Issue(s):- Impossible to backup => seems to corrupt the catalog at every attempt- Catalog getting unstable + Very lenghty (over 30mn...) to repair * (with the msg : updating catalog file format ! )   Environment :Lightroom Classic Version Number: V14.01OS Version Number: Windows 11 23H2Computer: Intel i7-12700KF - 64Go - Nvidia RTX-3090 24Go   Steps to reproduce: backup catalog... (voluntarily or automated) Expected result: more stability and the ability to backup safelyActual result: losing confidence and fear to lose all my catalog

I noticed this a few days ago but didn't realize the scale of the issue until I played around with the Exposure values and tested them to the limit.   I've attached two screenshots of the Develop module. The control image is an RAF photo with Exposure boosted to +5. The experiment is a DNG derived from the RAF, with a Denoise amount of 30. The effect manifests at all amounts from 1 to 100. However, the banding is not present in the Enhance Preview window. I have also attached the original Fujifilm RAF from my X-H2s camera (lossless compressed) and an affected DNG with Denoise.   I can't detect this phenomenon in NR conversions before LrC 13.3.    The significance should be self-evident. The banding artifacts appear in images with lifted shadows or underexposed photos with boosted brightness.   Lightroom Classic version: 13.3.1 [ 202405311538-6d7c0308 ]License: Creative CloudLanguage setting: en-CAOperating system: Mac OS 14Version: 14.5.0 [23F79]Application arc

photo:getDevelopSettings() sometimes returns nil for Temperature and Tint.   There was a previous bug report filed for LR 12.2 (also observed in 10.4).    The original bug recipe didn't reproduce the behavior in LR 13.0.1, so we closed the bug.  But now we're observing the misbehavior again in LR 13.5.1, with a slightly different bug recipe.    1. Download and unzip this small catalog: https://www.dropbox.com/scl/fi/nmh89jdu83e34vyhdgcj9/Temperature.2024.09.20.zip?rlkey=iib53zohs7ugef...    2. Copy the file "get-temperature.lua" from the catalog folder to the User Scripts folder.   3. Open the catalog.   4. In the Folders panel, right click the folder Temperature and do Synchronize Folder and import the one photo.   5. Select the one photo and do Scripts > get-temperature and observe the correct output:   6. Do Quick Develop > Reset All.   7. Do Scripts > get-temperature and observe the incorrect outp

Hi, Since the Lightroom Classic 13.4 update I can no longer trigger the Show Loupe Overlay using the keyboard shortcut CTRL + ALT + O. It still works using the menu (View > Loupe Overlay > Show). Another update, another new bug I guess 😜

LR 13.5 has many errors in the in-app help and tool tips for keyboard shortcuts.  There are many instances where the wrong shortcut is given, e.g.    DE: "Umschalt + D" instead of "Strg + Alt + Umschalt + U" for New Depth Range Mask.   There are instances where an inconsistent or wrong localization of a key modifier is given, e.g.    ES: "Ctrl + Maj + Entrée" insead of "Contrôle + Maj + Entrée"   And instances of inconsistent capitalization or spacing:   SV: "Ta bort" instead of "Ta Bort"   See the attached file for the complete list.    Nearly every release fixes previous such errors and introduces new ones. They could be easily avoided by running the Any Shortcut plugin's Analyze command.    

In German, the shortcut Cmd+Option+g (Mac) / Ctrl+Alt+g (Win) is assigned to two different commands, Preferences and Toggle Generative Remove:   "$$$/AgDevelop/Menu/Photo/ToggleGenerativeRemove/Key=Cmd+Option+g" "$$$/Application/Menu/Edit/Preferences/Key=Cmd+Option+g" "$$$/Application/Menu/File/Preferences/Key=Cmd+Option+g"     On Windows, Ctrl+Alt+g invokes Preferences in both Library and Develop, and there's no working shortcut to invoke Toggle Generative Remove.   On Mac, Cmd+Option+o invokes Preferences in Library and Toggle Generative Remove in Develop, and there's no working shortcut to invoke Preferences in Develop. Prior to LR 13.4, Cmd+Option+o invoked Preferences in Develop.   Tested in LR 13.5 / Mac OS 14.6.1 and Windows 11.    

The in-program help for Remove shortcuts incorrectly reverses the shortcuts for Increase/Decrease Brush Size and Increase/Decrease Brush Feather:     The relevant lines from TranslatedStrings:     "$$$/AgDevelop/Dust/BrushSize/Increment/Shortcut=[" "$$$/AgDevelop/Dust/BrushSize/Decrement/Shortcut=]" "$$$/AgDevelop/Dust/BrushFeather/Increment/Shortcut=Shift + [" "$$$/AgDevelop/Dust/BrushFeather/Decrement/Shortcut=Shift + ]"       Other languages with the same problem: IT, JP, KO, NL, PL, PT, RU, TH, ZH_CN, ZH_TW.   Tested with LR 14.0 / Mac OS 14.6.1.  

Lightroom Classic version 12.0.1 macOS 12.6.1 (21G217)   Upon quitting, Lr Classic asks to save a backup. If the backup is saved to a local drive, it succeeds. If it is set to save to a network drive (NAS) it fails. 1. Open Lightroom Classic 2. Quit Lightroom Classic, click Yes to really Quit 3. In the Back Up Catalog dialog select a network drive, Test integrity and Optimize can be checked or unchecked, click "Back up" button 4. Backup Up Catalog window appears with "Copying catalog" progress bar, it changes to "Compressing catalog backup" 5. Errror message appears, "Lightroom was unable to back up the catalog named "CatalogFilename". Please check your folder permissions, and make sure that you have available space on your backup drive and main catalog's drive. 6. Choose a local backup drive and it works   This was working in version 12.0, but would sometimes crash after saving. Now it doesn't crash, but it won't write. I tried unchecking and rechecking Full Disk Access

Starting with Lightroom Classic 13.5, Panel End Marks will disappear if the side panels are very long. This issue did not occur with 13.4 and earlier. OS version: macOS Sonoma 14.6.1 Hardware: 14-inch MacBook Pro with M3 Max processor Steps to reproduce: Enable Panel End Marks from Preferences > Interface. In any module (Library, Develop, etc.), right-click on any panel and select Collapse All. Note that the Panel End Marks do appear. Expand panels until the panel is sufficiently long and requires a notable amount of scrolling to see the bottom. Note that the Panel End Marks no longer appear, and an empty space appears instead.

Strange behaviour in the latest release of LR Classic 13.3 (Win). I've imported a shoot and used the embedded previews as I always do.   As I move through the filmstrip in develop every time I click on an image that still has the embedded preview icon showing LR is adding a new White Balance - As Shot to the history for the image. If I undo this step so the history is empty switch to another image and then back again LR doesn't add the WB setting again.   It seems it only happens to images using the embedded preview the first time they are opened in Develop.It's very annoying as I can no longer use the unedited filter to see if there's any images in my final selection that haven't been edited.  

Hallo Zusammen, seit dem Firmware-Update 2.0 auf die Z8 ist kein USB Tethering mit Lightroom mehr möglich.  In LR 13.2 Windows bekomme ich keine Verbindung zu stande.  Im Windows Explorer habe ich Zugriff, und auch mit Camera Control Pro klappt das Tethering. Aktuell forogr. mit Cam. Control Pro in einen von Lightroom automatisch überwachten Ordner – das geht, jedoch ist die Übertragung gefühlt viel langsammer als vor dem Firmware Update und mit LR Tethering Steuerung. Wer hat ähnliche Erfahrungen / kann mir helfen ! Vielen Dank. !System:Windows 10 Pro 22H2Lightroom 13.2

Adobe Lightroom 4 is annoyingly creating a directory in ~/Documents on Mac OS X. For example: /Users/smith/Documents/Adobe. Contained within this Adobe directory is an empty directory named "dynamiclinkmediaserver". This is an inappropriate place to create files or directories of this nature. OS X has other directories that can and should be used for settings, preferences, temporary files, and others of similar nature.These two directories are created every time that Lightroom 4 is launched, even after deletion. Please avoid creating these directories in ~/Documents and put them somewhere else in future patches and versions of Lightroom. I look forward to this annoyance being squashed. Thanks, and keep up the good work otherwise.

Snapshots don't record Lens Blur brush refinements. To reproduce on LR 13.5 / Mac OS 14.6.1:   1. Download and open this tiny catalog: https://www.dropbox.com/scl/fi/i8vynvlmbidsyexsackaf/lens-blur-copy-bug.2024.06.29.zip?rlkey=nyedxcdz0vo29067nj0n7d4qx&dl=0   2. Open the photo test1.jpg in Develop. Observe that it has Lens Blur enabled with Blur brush refinements.   3. Create a snapshot.   4. Click Reset.   5. Select the snapshot. Observe that the Blur brush refinements have been lost.