Lightroom Classic

function ConfigDialogs.CameraFilm(f, propertyTable) return f:group_box { title = 'Adding Camera and Film', fill_horizontal = 1, --------- Camera -------- f:row { f:static_text { title = "Camera Name:", alignment = "left", }, f:edit_field { alignment = "left", width_in_chars = 20, immediate = true, value = bind "CameraName", },…. width_in_chars = "11",This works on MacOSX (and it should not) and fails on Windows (correct)  

The Adobe Stock publishing service uploads a keyword even if Include On Export is unchecked. To reproduce:   1. Create the keyword "Test", unchecking the attribute Include On Export.   2. Apply Test to a photo.   3. With the photo selected, select Will Export and observe that Test is not displayed.   4. Drag the photo to Submit To Adobe Stock under the Adobe Stock publishing service, select Submit To Adobe Stock, and click Publish.   5. When asked, click Yes to Go To Adobe Stock To Complete Your Submission And Start Selling.   6. Observe that Test appears in the Keywords for the photo on Adobe Stock: See the attached screen recording.   This bug doesn't occur with other publish services, pointing the finger at the Adobe Stock plugin.   Tested with LR 11.0.1 / Mac OS 11.6. 

When Will Export or Keywords & Containing Keywords is selected in the Keywording panel, LR sorts the keywords case-sensitively, whereas it should sort ignoring case.   Tested in LR 13.0.1. To reproduce:   1. Add these keywords to a photo: apples, Bananas, cats, Dogs   2. Observe the keywords are correctly ordered case-insensitively with Enter Keywords and in the Keyword List panel:   3. Observe the keywords are incorrectly ordered case-sensitively in Will Export and Keywords & Containing Keywords:        

The Help for Library and Develop keyboard shortcuts shows "Shift" instead of "Umschalt":     These two lines in TranslatedStrings_Lr_de_DE.txt should be corrected:   "$$$/AgLibrary/Help/Shortcuts/SetColorLabelsShiftKey=Shift + 6-9""$$$/AgLibrary/Help/Shortcuts/SetRatingsShiftKey=Shift + 1-5"    

[Updated 2024-01-03 to include the problem with transform().] In Mac LR 13.1, plugins cannot set or change the selected items in a simple_list() control; when they try, the operation() and transform() callbacks of the binding also stop working. This worked up through LR 13.0.1, and it continues to work in Windows LR 13.1. The bug impacts several of my plugins, including the popular Any Filter.To reproduce: 1. Download and install this plugin:https://www.dropbox.com/scl/fi/ti1rgaf4v43arshtncuus/simple_list-bug.lrdevplugin.2024.01.03.zip?rlkey=au86pe5yb7ynaoiqfmjlkqr51&dl=0 2. Do File > Plug-in Extras > simple_list-bug. 3. Observe that no item in the simple_list() control is selected (incorrect, "2" should be selected): 4. Click item "2" and observe that the operation() and transform() callbacks of the binding are invoked: 5. Click the Set Selection button, which tries to set the selection of the simple_list() to "1", and observe that the sele

Just aquired newly released Canon RF24-105mm F2.8 IS USM Z lens. A profile for correction for this lens is on the list of lenses added in December 2023.  Applying the Distortion Correction profile in LR Classic and Photoshop Camera Raw produces edge artifact instead of improving distortion. At the edges, the image shows a pattern of stripes perpendicular to the edge and extending about 5% inward. This artifact occurs in LR 13.1 and Photoshop 25.3.1 with Camera Raw 16.1. It disappears if I deselect Profile Corrections. It is not present when I view the image with other software like the Windows photo viewer FastPictureViewer or in Canon's Digital Photo Professional, so it's specific to LR Classic or Camera Raw 16.1 with Distortion Correction turned on and not due to a problem with the CR3 raw files. If I force use of a profile for a different lens, the artifact disappears. That is perhaps a useful verification that the native profile is bad, but using a mismatched profile isn't goi

  Hello. What exactly is "Debug Capture Time"?

There appears to be a bug affecting all recent versions of Lightroom on high-DPI Windows devices. It affects both CC and standalone versions, up to and including the current version (2015.6.1).The issue is that when using the white balance dropper tool in the Develop module, the target location Lightroom uses does not correspond exactly to where the point of the dropper is located. Specifically, it seems to reference a position about 5 or 6 millimetres above the point of the tool.The issue also affects the manual defringe dropper in the Lens Corrections panel. Other local develop tools seem not to be affected (brush, spot healing, HSL/Color/B&W picker, etc.).To be clear: the issue affects Lightroom when the device is used in standard desktop mode with a regular mouse as the pointing device. It is not an issue with the touch screen, the pen or Lightroom's touch mode.The problem is described in detail with screenshots here (in the original post and in my reply):https:/

I would like to get some feedback on  the follwing issue.   USed H/W: HP Z6 G4, 2 CPUs Intel 6136 Xeon3.0 12C 128 Gb of RAM GPU Nvidia RTX 4070 ti Super Primary disk 500Gb SSD and 2TB SSD gen 5. Windows 11.  64 WKST Plus   Issue: DeNoise , "Lightroom not responding"   Example: Denoising a Nikon RAW file from Z9.  (Size ~55Mb) Lightroom Denoise estimates a 7 s process time. This fits well with the time the GPU is active and staying at about 90% usage. Once the GPU stops after 7s the systems seem to be idling for time of 2 minutes before it has completed the task and returned a DNG file to my disk. During these 2 min the message the message "Lightroom Framkalla Not responding" apperas at the top of the Lightroom window.Have also run a test by selecting 16 RAWfiles and recorded times. Result The GPU runs for 4 min and 36 s ( It seems to run one RAW-file at the time at a similar GPU time of operation (7 sek) but also a short paus between each  RAW files p

The tone curve is broken in Lightroom Classic 13.0. You can move the black point vertically and horiziontally at the same time, this however is no longer true for the white point. The white point only allows you to go in one direction at a time. So if you were hoping to bring down the highlights while also bringing up the brightness, it's no longer possible.

In the latest version of Lightroom Classic in the watermark panel. Click Italic and you get bold and visa versa. Noticed this after the update to the new version. My water mark had gone from Italic to bold. (Windows)

I have a 13-inch M1 2020 macbook pro. It's fully up to date with venture and lightroom classic is fully up to date. When I go to tether capture, before the camera is even plugged in, lightroom completely crashes when i hit "okay"  I restarted the computer, restarted LR, restarted creative cloud, updated permissions, gave full disk access, uninstalled and reinstalled LR, all of it. It still does the same thing.   It's not the camera because I don't even have it connected when I'm launching tethering. I've tried using my hard drive and external hard drive as the location, but there's always the same end result.

When clicking on a lightroom://plugin.identifier/link when lightroom classic is running, it will call the registered url handler of plugin.identifier. But when lightroom classic is not running and one clicks on the link, lightroom will start up, but not call the url handler.   How to reproduce:   Create a simple plugin:Info.lua:   -- lightroom://com.example.urlhandler/test return { LrPluginName = "URL Handler", VERSION = { major = 1, minor = 0, revision = 0, build = "1" }, LrSdkVersion = 11.0, platforms = {"Windows", "Mac"}, LrToolkitIdentifier = "com.example.urlhandler", LrForceInitPlugin = true, URLHandler = "URLHandler.lua" }     URLHandler.lua:   local LrDialogs = import "LrDialogs" return { URLHandler = function(url) LrDialogs.message("URL Handler", tostring(url), "info") end }     Make a simple index.html with     <a href="lightroom://com.example.u

On Windows, when the user has set Preferences > Interface > Font Size to Large, Larger, or Largest, it's impossible for plugins to properly size large controls and dialogs.  This is because LrSystemInfo.displayInfo() and .appWindowSize() incorrectly return width and height in units of physical pixels, rather than scaled pixels.     On Mac, those functions correctly return scaled pixels, allowing plugins to properly size controls and dialogs.   Most recently tested on LR 11.1 / Mac OS 11.6.2 and Windows 10.   [This bug report is an updated version of the original posted in 2018, which never got copied to this forum: https://feedback-readonly.photoshop.com/conversations/lightroom-classic/lightroom-lrsysteminfodisplayinfo-returns-wrong-units-of-pixels-on-windows/5f5f45ea4b561a3d426790a5    It has been edited somewhat to reflect changes in LR in the past four years.] Details On Mac, you can set a scaling factor for Retina displays via System Pr

When using the keyboard shortcuts "=" or "-" to adjust a Develop slider, an adjustment to another slider with the mouse is incorrectly included in the history step for the first slider.  This doesn't happen when you make the adjustments solely with the mouse.    In a related bug, if you adjust a Develop slider with the shortcut and then quickly click Reset, "Reset" appears as a history step before the slider.   To reproduce in LR 13.0.1 / Mac OS 14.1:   In screen recording tracking1.mp4:   1. Reset the settings on a photo and clear the history.   2. Click on the "Exposure" label to select that slider.   3. Quickly type "=" three times and then immediately use the mouse to click on the right end of the Contrast slider.   4. Observe that there is just one history step, "Exposure +0.30 0.30", even though Contrast is now +65 (or whatever value you clicked).   5. Set Contrast to -100, and observe there is now (correctly) a second histor

On MacOS 14.2.1, with Canon R3 and CR3 RAW files.   I don't use catalogs at all, just drag and drop raw files into Library, then edit in Develop. Just loading a directory of RAW files in this version just automatically generates XMP files for no reason, an old bug I haven't seen for many many versons.    As usual, XMP files should only be created when there are changes done to the RAW file, not just upon loading them in lightroom. It's a good system so I can edit galleries as needed, and then I can look in the directory and see if there are any photos I might have accidentally skipped over deleting by seeing there is no XMP associated with it. 

Okay, so just noticed recently that both my work laptop (Win10) and home laptop (Win11) have started crashing when jumping in/out of Library/Develop modules. I tend to end up with a grey screen in the main image area first before LrC either crashes completely or just hangs with the grey screen for ages.   Work laptop crash report attached (got deleted on upload). System setup info also attached for both.   Weird its just started. I'm using SSDs for both external catalogues too - only common factor?  

Lightroom Classic version: 13.1 [ 202312111226-41a494e8 ] MacOS Ventura 13.6.3 on iMac Pro 1. Import a TIFF into LR (mine was the result of focus blending in PS). 2. Do some editing, including some changes within an AI mask (select subject, in my case). 3. Rotate or flip the image, using the menu commands (not using the crop tool). 4. Re-edit in PS, using the “edit original” option. Save.   The result is that the image remains rotated but the mask doesn’t, and a weird crop is applied.

This was originally posted under "Bugs" but I really want this to be answered as a question. I will be happy to delete whichever post doesn't fit under the best category however! Thank you.   When using Lightroom Classic 12.2.1 with MacOS Ventura 13.3 (on a Retina 5K, 27-inch, 2020 iMac with the AMD Radeon Pro 5700 XT 16 GB and 72 GB of memory)... I am getting the entire image selected when I try to use the "Select People" then choosing "Entire Person." Lightroom Classic allows me to individually select the hair, teeth, eyes, etc. as usual but when trying to select the entire body, the whole screen gets turned pink to indicate that the Lightroom thinks that the whole picture is the person. I've attached two (redacted for privacy) screenshots of the "Subject" masking that still works as it should and the "Entire Person" mask that shows where the entire photo area has been selected incorrectly by the AI. Anybody have any thoughts? Thanks!

Since upgrading to v13, the export of images doesn´t work anymore. I always get this message:$$$/CRaw/Error/Unknown=There was an unknown error. (1)   I´ve tried reinstalling it, but its also couldn´t solve my problem. My system is Windows 11, 64-Bit version . All Drivers are up to date

Customer takes a picture on IOS device and makes Develop Adjustment edits on the IOS device in an Album that syncs with Lightroom Mobile.  That image appears in the collection in Lightroom Classic with a “Metadata Change icon. This is incorrect since no Metadata changes were made using Lightroom mobile or Lightroom Classic.  GPS on device has been disabled. Issue: When customer clicks on the metadata icon in Lightroom mobile and selects “Save” the develop adjustments are removed from the image in BOTH lightroom classic and the IOS device. The same behavior occurs when the develop adjustments are made in Lightroom mobile to an image taken on the IOS device

Why no one writes about the fact that in develop mode, after any manipulation with a photo, it is impossible to go to the next photo in the feed? You go, but the photo remains the same as it was, you have to go back and only then go to the next photo. This is a global problem!!  Anyway, I did some research and I realized why many people are silent about it, because this problem occurs only when using the +\- buttons on any keyboard, even on macbook !!!!. If you use only mouse or touchpad, there is no problem with photo transition. That's why many photographers don't pay attention to it, because they don't use the keyboard. Therefore, ADOBE does not react in any way.

Hi I recently updated my Lightroom Classic and now every time I try to launch it I get the error 'Adobe Lightroom Classic quit unexpectedl'   Below is the crash report. Does anyone know a fix to this? <Apple Crash report removed so Pinned Post is visible>

Since the latest version of Lightroom I can no longer edit an image in full screen. After pressing F to enter the full screen mode then pressing the > key to move to an adjustment the full screen image only displays a small rectangular part of the image in the top right hand corner.  Seeing this on both my Imac Pro and MacbookPro.   Also since the previous version of Lightroom pressing the I key there is a discernable delay before the information is displayed when the catalog is first opened. It used to be instantaneous. Again on both my Imac Pro and MacBook Pro.   Lightroom Classic 12.3 Mac OS Ventura 13.2.1

Hello,   Anyone experienced this issue? Upgrading to Ligtroom classic 12.1, RGB color readouts were completly off on masks. Visually you could see the expected changes in contrast, brightness, etc while mouse over readouts showed the same numbers as before. So completly off. Like you could see that black areas were getting toward complete black, but the readout was still at around 14% in all 3 channels.   I downgraded my Lightroom to previous 12.0.1. which works just fine.   iMac (Retina 5K, 27-inch, 2020) 3,8 GHz 8-Core Intel Core i7 40 GB 2667 MHz DDR4 AMD Radeon Pro 5500 XT 8 GB Osx Big Sur 11.6.4   Boris GG