Lightroom Classic

On Windows, the method catalog:triggerImportUI (path) opens the Import window but doesn't set the initial source to "path". It works correctly on Mac.   To reproduce on LR 13.0.1 / Windows 11:   1. Save this script to the file "test-import.lua":   local path = import "LrPathUtils".getStandardFilePath ("home") import "LrDialogs".message (path) local catalog = import "LrApplication".activeCatalog() catalog:triggerImportUI (path)     2. In LR, do Scripts > Open User Scripts Folder and place "test-import.lua" in that folder.   3. Restart LR.   4. Do Scripts > test-import and observe that the Import window opens but no source is selected in the Source panel.  The Windows 11 result is on the left, Mac OS 14.1 on the right:         

I upgraded to 13.0.1 and now it crashes intermittently in development mode. It could be around the time of moving from one photo to another but I am not sure. In editing about 300 photos it has crashed around 20 times. There is a pause, then a blank screen and then it crashes. One time it prompted me to send a crash report and I did. It also did this when I updated my graphics driver. This is what I have tried. I can not remember LRC crashing on this system ever before upgrading to 13.0.1 Updating other apps in CC like the camera raw Running all Windows updates for Win10 Updating the Nvidia driver to the latest and also making sure I am on the studio driver Tried disabling the GPU acceleration.  Updated loop deck drivers  Rebooted at least 5 times Deleted the GPU file in app data  My system   Windows 10 Pro 64bit - latest updates AMD Ryzen 7 5800X 8-core Processor 32GB of RAM MS1-B550 A Pro Mother board MSI RTX 3060 Sudio driver 537.58 M2 SSD for OS and a se

Hi folks,   I have these weird bugs that have been happening since the latest update and it is driving me crazy. It's a bit hard to explain but hopefully this is clear...   BUG 1 I'm in the develop module and I click to another photo and occasionally the develop settings from the first photo get applied to the new photo I just clicked on (I'll refer to this as the ghost settings). *BUT* it's not actually showing the develop settings being applied in the history. When I click on other actions in the history, it doesn't show the changes reflected on the image - it's still stuck on the developed settings it copied from the previously selected image (the ghost settings). Sometimes I have to leave it for a couple of minutes before it will revert to its own original develop settings. And if I edit while the ghost settings are applied then it's editing it with the ghost settings visible and I can't revert to the original develop settings. It's unbelievably frustrating.   BUG 2

Lightroom Classic 13.0, macOS Ventura 13.6 Lightroom 13 introduced new histogram style purportedly to accomodate HDR but the new style makes it difficult to actually use histogram to determine areas in gistogram free of data and settong white/black levels correctly.This all being discussed to death in this post https://community.adobe.com/t5/lightroom-classic-ideas/p-reinstate-version-12-histogram/idi-p/14157437 which was moved to ideas preseumably because it asks to reinstate v12 histogram. It is also being discussed here https://www.alex-kunz.com/new-features-in-lightroom-classic-13/ . I now rephrase the request for bugfix - fix the new histogram in v13 to make it show gaps in highlights and blacks clearly (similarly to the way v12 one did where it can be done with ease).The demonstration of the differences between old style and new style where 1-1.5 stop free part of histogram in highlights can clearly be seen in v12:   and not so clearly in v13  

I have seen many posts about this and then many lazy replies of 'this is now fixed in the update', but I have just purchased a Wacom Tablet, done everything which I've seen on YouTube ETC, and it is STILL not working.   The pressure DOES NOT WORK in Lightroom when trying to Dodge for example.   What is wrong with Adobe? Why isn't this fixed yet?   Windows Ink is disabled, and I've restarted several times and have the latest drivers.   What is the solution here? Or do I need to get a refund because Adobe have messed up with one of the most popular brands of tablet out there?

"An error occurred while saving the book: an error occurred adding text and fonts to the book."I am running Windows 10 (v10.0.17134); LR Classic CC v8.0 and v7.5 (to avoid yet another bug) both get the same error. i7-6700K with 16GB RAM, loads of free disk space, 15GB RAW cache, etc so no limitations that should cause problems. I have published around 15 books from LR on Blurb ever since the Book module first appeared; they all use the same layout standards and fonts so nothing new in this book. The book was producing a PDF and also uploading to Blurb until I edited some text fields and expanded one text box.  I have tried the community-selected workaround of selecting all text fields (Ctrl-Alt-A) and changing fonts to Arial then back to Myriad Pro (I have always used Myriad Pro except for Georgia on the cover) but still does not work.  Tried both v8.0 and v7.5 but neither work. No text or image boxes added so can't have any new empty boxes (and I am pretty sur

  I am a Jeffrey Friedl's “Export to Flickr” Plugin user since many years. Yesterday morning Lightroom Classic passed to V13 I used LR/Mogrify 2 and LR/Export to Flickr for many years now. With previous version of Lightroom Classic I used Mogifiy without problem with Export to flickr This is an example uploaded Oct 7th 2023 https://flic.kr/p/2p7NDVm This morning, after updating to LR V13 and Register Export to flickr the export of new pictures gave only the picture without its frame producef by Mogrify This is an example of the frame free picture uploaded this morning : https://flic.kr/p/2p8vNW9 I also tested exporting with LR/Mogrify 2 alone in a picture file, it worked just normallyLR/Export to Flickr alone also worked normally but not the mix of two!

In LR 13.0, the wrong keyboard shortcuts are shown for Range > Depth Range in the Masking panel for Spanish, French, Italian, and Portuguese.   In Spanish on Mac, "Alt" is shown instead of "Opción" or "Opc":   In French, Italian, and Portuguese on Windows, "Cmd+Opt" is shown instead of "Ctrl+Alt":                         

In Japanese, the keyboard shortcut shown for Create Virtual Copy in Library and Develop is "Shift + Command + y" but should be "Command + Shift + Y". (It looks sloppy to not follow LR's convention.)   Changing that on Mac will automatically change it for Windows to "Control + Shift + Y".    

Checking and unchecking Use Device Map in Lens Blur doesn't update the Focal Range histogram.   To reproduce in LR 13.0.1:   1. Import this HEIC with a camera depth map: https://www.dropbox.com/scl/fi/us562okxbc76t2q8gzxd7/depth-map.2023.11.01.heic?rlkey=182qxsw53lmpiqrvk1pwc1502&dl=0   2. Apply Lens Blur and click Visualize Depth.   3. Toggle .... > Use Device Map in the upper-right corner of the Lens Blur panel. Observe that the visualized depth map changes but the histogram remains the same:   The histogram should change to match the currently display depth map.                                                                    

When editing a photo with an embedded lens profile, the message "Built-in Lens Profile applied" often doesn't appear in the Lens Corrections panel.  To reproduce:   1. Download this catalog, which includes 32 raws from various Nikon Z cameras and lenses with embedded profiles: https://www.dropbox.com/s/sy42uni5okojm5j/lens-profile-bug.zip?dl=0   2. With another catalog open, do Preferences > Performance > Camera Raw > Purge Cache.   3. In the downloaded catalog folder, delete <catalog>Previews.lrdata and <catalog>Helper.lrdata if present.   4. Open the downloaded catalog.   5. Go to Library, select all photos, and do Library > Previews > Build 1:1 Previews.   6. Select the first photo and go to Develop. Observe that the message "Built-in Lens Profile applied" is missing from the Lens Correction panel.   7. Regardless of whether the message is missing, zoom to 100% and then zoom to Fit. Observe the message is n

Issue: Point colour does not clear when syncing from an image with no point color adjustments Lightroom Classic Version Number: 13.0.1 OS Version Number: 13.5.2 Steps to reproduce:  Image 1 has no point color adjustments  Image 2 has point color adjustments   Sync develop settings from image 1 to image 2 Expected result: Point color adjustments should be Nil, 0Actual result: Point color adjustments remain attached to image 2   Reversing the order and pointg color adjustments carry over from image 2 to image 1. Seemingly no way to clear the point color adjustment unless resetting image individually using the reset buttoin at the bottom of the develop module. Very time consuming for 1100 images.  

Hi...new here and not overlay technical in knowing how to describe but here goes:  in LR when I go to 'develop' and cropping...using the overlay tool and cropping the image makes it totally disappear from the 'proof preview'.  I then have to click on the original pic and back to the cropped picture where I can see it in the lower frame windows (small on the bottom) and it will reappaear in the proof preview for me.  This is new in the last month.  Previously when I would crop, it would simply do that in the proof area and be visible throughout the editing process for me.  I wondered if there is a glitch or if I have inadvertantly changed a setting (hoping not).  Anyone recognize this issue?  Help?

Mac OS Ventura 13.2.1 Lightroom Classic 12.2.1   In slideshow view, the text doesn't display properly (e.g. wrong filename from the previous image), which has been reported previously, but with no apparent fix.   But now the text also displays incorrectly in the exported pdf.   Some are fine, but some have the wrong filename text, and some have a weird shadow/outline thing going on with the text, like it's been duplicated. The positioning of the text also changes between the slideshow and the exported pdf.   The slideshow pdf is now basically useless.

Lightroom Version 11.1 11.0.1Operating System macOS 11 Big SurWhen viewing the slideshow in Preview the wrong captions are shown for some images. It is OK when exported to a PDF. 

I ran into a cericumstance where the RGB numbers displayed below the histogram in the develop module will not update to reflect the area below the cursor. If the cursor stays stationary, and you use the mouse scroll wheel to scrol the image beneath the cursor, the number does not update. To get an accurate reading, you have to move the mouse slightly to refesh the reading. 

Color picker does not work on reference view. Works on active view. W11, lr 12.5. Seems to work on Mc Os   Thierry

Long standig bug in LrC.   Steps to Reproduce:1. Select a Mask.2. Intersect to this Mask another Mask of you choice. (e.g. Sky)Actual Result: Whenever we use "Intersect" the History states "Subtract (type of Mask)"e.g. "Subtract Sky"        Expected Result: When we use "Intersect" History should state that we performed an Intersection.   E.g "Intersect Sky   .

I work on a small screen and the side panels have to be as small as possible most of the time. This means that I cannot always read the entire name of folders and collections. If I could just hold the cursor over to view the full name, it would be very helpful. But usually no tooltip is showing up, even if I hold the cursor there for a long time.    Sometimes it appear after a while, and then not only one, but two tooltips appear. First one that it hardly legible because of a shadow under the text, then – some seconds later – another tooltip appear. The last one is much clearer and easier to read. But I would prefer that only this last tooltip appeared, and that it always showed up, not only from time to time.   

Hello. Don't try it on your production catalog. If you try to export in the original folder using the original name without warning LrC display a error message telling you that export was not possible. This is normal and safe. But LrC delete the original. It is not even in the trash.    And if you press on OK your original will disapear from his folder.  Tested on Windows 10 Pro 22H2   Kind regards  

The tips should be "Sample Point Color", not "Sample Spot Color". And all the localization are wrong. And the the notes in Chinese is still English, it is not localized  This is LRC   This is PS CR. It is correct.

My setting: Ventura 13.0.1 (on M1 MacBook) and LR Classic 12.0.1   When I import *new* images from an iPhone, the import dialog shows *all* images (see separate bug report) and:    1. it shows images in an abritrary order despite the option "sort by date". It seems as the sort takes some other information, but not the true datetime. 2. when it come to organize the images into subfolders by date, the images are moved to the wrong folders!! For example, I have not taken any picutre today, but the dialog shows 48 images to be inserted to the folder 2022-11-27. Looks like random behavior....   The import works fine in 11.x and before. I did not change any settings.     Best regards, Erik      

Open Lightroom Classic 7.5 on MacOS 10.14 and click on green button to fo full-screen. Sometimes the title bar disappears (i.e. there is no "Lightroom Catalog.lrcat - Adobe Photoshop Lightroom Classic - Library" or red, orange, green buttons. To exit full screen you have to elect from the menu bar Window -> Exit Full Screen.This only started happening after upgrading to 10.14 on Monday.

If I make a gradient mask adjustment, then select subract using brush, the left and right bracket keys no longer manage the brush size but instead increase or decrease the star rating of the image.  The brush mask itself works fine with the bracket keys changing the brush size.  It seems only to happen when the brush is being used to modify an existing mask, although I did not test beyond the example cited.  Is there something I'm doing wrong or is this a true bug?

Broken: LrC 12.1 Working: LrC 12.0.1 OS: Win11 22H2 GPU driver: Nvidia gameready 527.56 (disabling GPU acceleration does not resolve the issue)   32bit TIFF files (such as 3D renders, astro stacks, HDRs from third party tools, etc) are not being rendered correctly in Lightroom Classic 12.1. The bug is new in 12.1, 12.0.1 handles them correctly/as previous versions did.   Here's how 12.0.1 handles this file:   Here's the same file, with the same develop settings and export settings, from 12.1:   The highlights and shadows adjustments simply flatten the contrast of the image. Additionally, in 12.1 the white balance slider is now relative(-100 to +100) instead of absolute (showing a kelvin temp). As if 32bit TIFFs are being treated as non-raw/non-linear files or something like that?   Here's a sample TIFF: https://drive.google.com/file/d/1WvqO09WhL3QtTVw4SEaCost6ChcwKJYX/view?usp=share_link   Steps to reproduce: Load any 32bit tiff, the sample file linked