Lightroom Classic

I'm having this issue after upgrading to 24.4.1 with Lightroom 12.3 on Windows 10.  The taskbar tab turns orange, but I have to click on it to get Photoshop to come forward.  Any idea what's going on?   Thanks, David  

[This bug still exists in LR 10.0. See here for sample images to test with: https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-preset-hover-preview-incorrect-for-incremental-temperature-tint/5f5f46154b561a3d4272bc43?commentId=5fc3e345ce4ce1357af23986]   The preview of a develop preset when hovering over it in the Presets panel is incorrect when the preset contains IncrementalTemperature and IncrementalTint values and the photo being edited is raw. To reproduce:1. Open a non-raw in Develop and change Temp and Tint to +20.2. Save a preset "Temp/Tint" with just White Balance checked.3. Open a raw in Develop.4. Hover the mouse over Temp/Tint and observe the change to the photo.5. Click on Temp/Tint and observe there isn't any additional change to the photo (as expected).6. Move the mouse pointer over the photo. Observe that the photo colors noticeably change.7. Repeatedly move the mouse pointer back to over the Temp/Tint preset and then back over the phot

I convert whole folders of raw files to lossy DNG on a regular basis, and since earlier this year (at least), I've noticed a problem that affects a very small percentage of the files (sometimes it doesn't happen at all), but it's starting to become a little annoying.The problem (when it happens) is that some of the resulting lossy DNG files look good in the Develop mode of LR Classic and in Camera Raw. Even the preview from Windows file explorer (and when using image viewers that display the embedded jpg preview) looks ok. But when displaying these problematic files from the Library module in Lightroom Classic, they show a strong purple cast. So, I think there is some problem with the preview generated by LR.Like I said, this problem happens very rarely, but it keeps happening every now and then. Most of the times I am able to fix the "pink preview" by re-building 1:1 previews, or just removing and reimporting the file. But there must be something going on with the preview generation f

Ever since LR 7.3 introduced the new develop preset format, it takes O(n^2) time for a plugin to access all of the develop presets. Some users have 5K, 10K, or 15K presets, and it can take minutes for a plugin to access all of the presets: for _, folder in ipairs (LrApplication.developPresetFolders ()) do     for _, preset in ipairs (folder:getDevelopPresets ()) do        ... Users think the plugin has crashed or hung! While having 10K presets may seem unusual, there's no excuse for LR to take minutes to return all the presets.Here's how fast my LR / Mac OS loads presets versus the total number of presets:Most likely, LR is storing all the presets in all the folders in a single flat list.  When the method folder:getDevelopPresets() is called, it scans the entire list for presets with a matching group.  The correct implementation is obvious: Use a hierarchical representation, with a list of folders, each folder with a list of presets.

This worked up until last week. I have verified the login credentials via filezilla, which works perfectly. I have also contacted my web host, and they have said that the error that they see on their end is that Lightroom is using an outdated sftp protocol, which is no longer considered secure, and is no longer supported on their server. The sftp requirements for my host are listed here:https://wpengine.com/support/sftp/ I am running the latest version of lightroom classic CC. I appreciate your help in getting this issue resolved quickly. I have also try deleting the preset and making a new one with no change. Thank you.

Create a Smart Collection that shows at least 20 pictures in grid view   View - Sort - Label Color View - Sort - Ascending   None of the cells must be colored   Use the scroll bar to show the 1st. row   Click a cell an press “9” to paint it blue.  Repeat this 5 more times to paint non consecutive random cells   Every colored cell must go to the first rows   Now: Click a non blue cell, drag it and drop it on it self   Result: the color order is lost   Note: This situation doesn’t happen if you repeat these steps in a folder, the problem arises just in smart collections

The fields in the Default, EXIF, IPTC Extension, Location, Quick Describe, and Video tagsets jump and down as you enter text in fields and tab to the next field.  When you hit tab, LR displays briefly shows an empty field at the top of the panel and then removes the field.  This is very distracting when you're trying to enter lots of data.Here's a screen recording: https://dl.dropboxusercontent.com/u/21811200/metadata-entry-bug.2017.07.1.movThis happens to me with new catalogs on CC 2015.10.1 / OS X 10.12.5, CC 2015.5 / OS X 10.12.5, and CC 2015.10.1 / Windows 10.  It doesn't happen with LR 5.7.1 / OS X 10.12.5.

I noticed in the print module when I unchecked the print resolution option that Lightroom would display different image resolutions based on the orientation the shot was taken in.  For example, I shot on two different cameras both 24MP (Nikon d7100 and Sony a7ii) and for portrait it would display an image of 2x3 at 1333ppi while for landscape it would display 3x2 at 1440ppi.  I think this is a bug for Lightroom only as Photoshop still reads both files as the same resolution and the file sizes are identical no matter the orientation. I don't know if this is just a calculation glitch or if Lightroom is actually reading these files as smaller.

I am unable to start / use Lightroom Classic since a week. The programm crashes at startup with error  <crash exception="EXCEPTION_UNKNOWN" exceptionCode="0xe06d7363" instruction="0x00007FFD5CF3CB69"> I am on Windows 10 with AMD Radeon Vega 8 Graphic Card. (VRAM 2048 GB).   All other Adobe CC applications are running fine. I am primarily using Lightroom, though. Hope anyone can help. Here is the full crash report.   <?xml version="1.0"?><!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd"><crashreport serviceVersion="4.8.0.6" clientVersion="4.8.0.6" applicationName="Adobe Lightroom Classic" applicationVersion="12.2.1" build="[202303011008-5bfbce17]" source="Windows-Client" crashType="n/a"><time year="2023" month="5" day="8" hour="8" minute="8" second="41" timeoffset="60" timezone="Mitteleuropäische Sommerzeit"/><user guid="ad8b2931-cfb0-45f9-bf97-ca5f3b7a0dfa"/><system platform="Windows 10 Pro" osversion="10.0" osbuild="19045

Today I imported some HEIF images (Camera: Sony Alpha 7 IV) into lightroom. Everything was fine until I opened the develop module. Whenever I did so it first showed a warning that there was an "error writing the metadata" and after deselecting the image the prompt "error reading the image" came up.       I already tried following: Re-importing the images (directly via Lightroom copying from the SD card to the MacBooks desktop), manually copying the images to desktop folder and then importing. Checking all the privacy settings (accessability  and full disk access), first-aid for the harddrive and restarting both LR and the MacBook. Also LR is running on the latest update. My catalouge is currently running from a 64GB USB Stick (formated for Mac OS Extended (Journaled)) and the images are in a folder on my desktop. So I don’t see a reason why or what is causing this errors.

Searching for ancestor keywords in the Keyword List panel shows incorrect results for descendant keywords.  The behavior broke somewhere between LR 10.4 and 12.2.1.   To reproduce on LR 12.2.1:   1. Assign the hierarchical keyword 1 > 2 > 3 to a photo.   2. In the Keyword List's Filter Keywords box, enter "1".   3. In LR 10.4, observe that all the keywords contained by keyword 1 are displayed, that a right arrow appears when you hover over 1, and the correct count is shown next to 3:   4. But in LR 12.2.1 observe that: a) keyword 3 is not shown, b) no right arrow appears when you hover over keyword 1, c) an incorrect count of 0 is shown for keyword 2 (the panel normally never shows counts for ancestor keywords, only for directly assigned keywords), and d) the triangle to the left of keyword 2 points down to indicate there are descendants displayed, but the descendants aren't shown:   See here for the original report: https://community.adobe.co

After you clear the GPS field of a DNG via the Metadata panel, Metadata > Save Metadata To File doesn't clear the GPS coordinates in the file's EXIF.  To reproduce:   1. Import this DNG and observe in the Metadata panel that it has GPS coordinates:   2. In the Metadata panel, clear the GPS coordinates.   3. Do Metadata > Save Metadata To File.   4. Use Exiftool to observe that the file still has GPS coordinates:     $ exiftool -a -G -gps:all APC_0851.dng [EXIF] GPS Version ID : 2.2.0.0 [EXIF] GPS Latitude Ref : North [EXIF] GPS Latitude : 38 deg 7' 51.64" [EXIF] GPS Longitude Ref : West [EXIF] GPS Longitude : 119 deg 26' 42.64" [EXIF] GPS Dilution Of Precision : 6.000906208 [EXIF] GPS Speed Ref : km/h [EXIF] GPS Speed : 1.770554817 [EXIF]

On Mac OS, after completing an import LR will sometimes display the message "Ejected card after import" but fail to actually eject the device.  This affects users importing from Cfexpress cards.   To reproduce on LR 12.3 / Mac OS 13.3:   1. Connect an external USB disk drive or a Cfexpress card reader containing a Cfexpress card with at least one photo on it.   2. Verify that Mac OS considers the drive non-removable by running this command in Terminal:   diskutil info "<volume>" | grep -i removable   The output should be:   Removable Media: Fixed     3. If you connected a USB disk drive in step 1, copy to it the DCIM folder from any camera memory card containing at least one photo.   4. In LR, do Import, selecting the option Eject After Import. In the Files section select the volume from step 1 and select one photo.  Click Import.   5. When the Import completes, observe that LR displays "Ejected card after impo

Exporting a photo with a brush mask and overlapping red-eye correction fails with "unknown error" when Use GPU For Export is enabled.     Tested on LR 12.1 with Mac OS  12.6.1, 12.6.2, and Mac OS 13.1 on two different machines. To reproduce:   1. Import the attached JPEG.   2. Enable the option Settings > Performance > Use GPU For Export.   3. Export the photo to the desktop as a JPEG (see the attached screenshot for precise export settings).   4. Observe the following "unknown error":   The photo has a brush mask applied around the right eye socket, with Whites = 22 and Noise = 18, and a red-eye correction on the right eye.     See here for the original report: https://community.adobe.com/t5/lightroom-classic-discussions/error-using-the-publishing-service-in-lightroom-classic-12/m-p/13457922#M305285        

Applying Denoise to a photo and its virtual copy fails with the error, "Failed to import the enhanced photo". To reproduce on LR 12.3 / Mac OS 13.3:   1. In LR, make a new folder and move a raw file into it.   2. Create a virtual copy of the raw.   3. Select the raw and the virtual copy and do Photo > Enhance > Denoise (doesn't matter whether Create Stack is checked).   4. Observe the error "Failed to import the enhanced photo":   5. Select the newly added DNG and observe that Copy Name is blank, indicating it was created from the original raw, not the VC.   6. Select the virtual copy only and do Denoise, observing that it succeeds.    

When i go Full screen preview in develop module with F key and give a photo red flag rationg which is keyboard shortcut 6 the photo disapeers 😞 I work on MacBook 14 M1Pro and I checket this on other M2 Max MacBook and its the same.   Here you have this bug on video 😉https://youtube.com/shorts/pMbe0p2fWVc   Pozdrowienia z Polski i dziękuję za pomoc / Thanks for help Paweł Słowik www.slowik.eu

iMac 27" 3.6 GHz 10-Core Intel Core i AMD Radeon Pro 5500 XT 8 GB 32 GB 2667 MHz DDR4 macOS Ventura 13.3.1 The function works fine if processing is completed and a DNG file is created. Works fine if the preview window is closed using the Cancel button. If the ai denoise preview window is closed using the red dot in the top left then LRC freezes and requires a forced quit.  

Lightroom Classic Version Number: 12.2.1 Edition Windows 11 Pro Version 22H2 OS build 22621.1413Experience Windows Feature Experience Pack 1000.22639.1000.0   Steps to reproduce: 1)  Open notepad, enter a text with a linebreak, copy & paste into the keywords field. This creates a keyword with a linebreak. Practical usage case: I am copy-pasting animal species names from nature kindle books to the respective animal pictures. Since the line breaks don't show as a special carachter, they are not obvious in case the copied line break matches the display linebreak in the keywords field 2) Export the keywords (CSV method) 3) Try to import the keywords into lightroom. This returns an error about invalid data.   Expected behavior: a) Either lightroom should filter special characters or b) properly use quotes in CSV export and respect them on import c) Alert then special carachters are used.

Photo Merge > Panorama / Perspective sometimes crashes LR -- I've submitted two crash reports under my Adobe Id.   It occurs repeatedly:   1. Do a successful Photo Merge > Panorama of two overlapping photos with Perspective, Boundary Warp set to 0, and the other options unchecked.  This will set those options as the current default.   2. Import these two photos: https://www.dropbox.com/s/or051jcumfsn8pj/panorama-crash.2023.05.10.ARW.zip?dl=0    3. Do Photo Merge > Panorama and set Boundary Warp to 100. Observe that Cancel and Merge don't do anything.   4. Click Cylindrical and observe the warning "Unable to merge the photos. Not enough matching photos for merging."   6. Click Perspective.  LR crashes.   Tested on LR 12.3 / Mac OS 13.3 / Macbook Pro (2023, 16", Apple M2 Max).  See the attached System Info.  The problem doesn't occur on my Windows ARM 11.  

Hi,   I have LrC version 12.2.1 installed. LrC is syncing about 100 pictures before it craches and need a restart. I need to sync the 40 k pictures that I have in the cloud, so it is going to be a long day before all are synced to my local drive.

Issue: If I filter the unflagged images and then activate the cropping tool, while still in cropping mode, if I flag the image, rather than it advancing me to the next unflagged image, the develop window goes blank.   Lightroom Classis Versio: 12.3 OS Version Number: Ventura 13.0   Step 1. Filter unflagged images using the filter bar Step 2. Activate Cropping mode Step 3. With the cropping mode active, flag the current image Step 4. The develpp window goes blank rather then advancing to the next unflagged image

Hallo zusammen, seit der Version 12 (auch 12.01) scheint Lightroom den Programmspeicher immer weiter zu füllen, bis dieser überläuft.   Dabei arbeite ich nicht mal in Lightroom, sondern Lightroom läuft im Hintergrund und lädt lediglich die in der Cloud liegenden Fotos runter.   Technische Daten:   Lightroom: V12.01 Computer: MacBook Pro Chip: Apple M1 RAM: 16GB macOS: Ventura (13.0)

Issue: LrC 12.2  macOS Ventura 13.2.1   Steps to reproduce: Create a Smart Collection with one rule: "Label Color" = red (or any other color given to any photos in the Catalog). The Smart Collection gets populated immediately with all photos labeled "red" in the Catalog. No Filters are applied. Exit Lightroom Classic. Re-open Lightroom Classic. The Smart Collection shows 0 photos and displays the following message: "No photos in selected Smart Collection." Switch between Grid and Loupe View, or switch Filters On/Off. All photos previously present in the Smart Collection re-appear.   Expected result: After re-opening LrC the Smart Collection should show all photos labeled "red" (or any other color chosen in the Rule dialog). Actual result: No photos are shown.

I am using LrC on Mac (v12.3). When viewing images in LrMobile on my iOS devices (both iPhone and iPad), many of my images display "Waiting for settings". This has been reported elsewhere in these discussions. It was asserted recently that the April 2023 software update fixed the problem. It has not, or at least not for me. All my devices are running the latest OSes and latest Lr apps.   Help would be appreciated.

This bug is driving me crazy. Upgraded to the newest lightroom today (from 8.4) expecting this would be fixed by now. I'm doing a lot of product photography, sometimes retouching in lightroom isn't enough so I switch to editing the original JPEG file. When saving the image and returning to lightroom the aspet ratio of the image is all wrong and all the edits are upside down (I would like to keep the lightroom edits). This only happens with portrait photos, not landscape. I have deleted my user profile settings in Photoshop as suggested somewhere, tried the "Automatically write changes to XMP" but nothing is working. Please help..   on a Mac, Monterey 12.6.1, Lightroom 12.3, Photoshop 24.5   Video of the workflow: https://www.dropbox.com/s/mll45wxvhj0lx7n/Aspect%20ration%20rotation%20bug.mov?dl=0