Lightroom Classic

When I import images from an SD card into a subfolder LR CC puts the images into the subfolder and into the parent of that folder. If I try to delete one set of images LR CC deletes the images from both locations. Note: I did not check "Create a second copy" on Import. Please see my attached images.

I bought a new mac and new lightroom.Everything looks very different from my old lightroom on the previous mac.The module bar is missing and i can't even see what lightroom i have.Is anyone familiar with this problem ? 🤷

Before upgrading to LR CC Classic, my Canon Pixma Pro-100 printer worked as a plug-in. Now, after updating to LR CC Classic, I get this error message: The destination folder for this action is missing.(/Library/Cache/Canon/PrintStudioPro/PrintStudioPro-LR-TEMP).Anyone know how to solve this problem so this version of LRCC will still find this plug-in for my printer?Thanks!

HiWhenever I export a photo I've edited in Lightroom Classic, it adds it to the catalogue. I don't see the point in this as any edits in the future I would also do on the original and not the exported version. Is there a way to turn off this behaviour so that exported photos don't end up in the catalogue anymore? It's getting quite repetitive to remove them every time.

Hi. Please help me understand how to prevent the photos from showing Evoto when displaying in the collection that I shared online, or anywhere really. I'm not sure where it's pulling this data from. All the photos in the collection were, at one time, edited in evoto, but not all of them are stamped in such a way. What other data do you need from me so I can better ask the question and find resolution (if any)?   

When I place a mask in a photograph is place a yellow sheem over the masked aria.   it is not the overlay colour which is red in my case. There are no presets active on masking as far as I know. I work on an Apple Mac Book pro 16" M2 and Lightroom 13.3 as of today but this issue was there on previous updates as well. Anyone have a guess what's going on and how I can fix it?

Nach Upgrade auf Lightroom Classic V13.3 stürzt ständig der Katalog ab und wird dann repariert. Anschließend sind alle Bilder, die ich über das Smugmug-Plug-in auf auf meine Homepage hochgeladen habe, "erneut zu veröffentlichen". Sie wurden aber gar nicht geändert. Lightroom hat also diesbezüglich alles vergessen. Alle Bilder erneut hochzuladen, würde mich Tage, ja Wochen blockieren. Ich verwende Windows 10, aber das hat - glaube ich - nichts damit zu tun.

When the HDR function is turned on on the computer, the preview image appears greenish

This is going to take a while uploading everything from scratch and then babysitting multiple Android devices to download again. Why is this necessary? Did you increase the Smartpreview resolution?

Hi,  i have a windows 11 , Interl I5 2.3 GHZ, 8 GB RAMbut with an Nvidia Geforce GTX 1050 2GB I have raw files from Canon 6Dm2. When i try noise reduction with AI it calculates about 30  minutes per file.I have set preferences > performance so that it is forced to use GPU for displaying, processing and exporting, so to full usage.Still it says 30 minutes per file.Any tips are welcome 

I recently updated my Ligthroom Classic and since then Lightroom keeps crashing whenever I switch over to the Develop module.   [moved to the correct community and from bugs to discussions according to the community rules - Mod.]

Hi all, I've read the threads on this so am aware that viewing of the HDR changes in LR depends on your computer/phone capability (and whether you can use XL/AVIF etc). My question is slightly different. I need to save my HDR edited images on Google Drive for a client. If I export as JPEG it doesn't show the HDR change, XL/AVIF/TIF do show the HDR changes but aren't compatible with Google Drive preview so therefore not useful for the client. If I save as TIF and batch change to JPG the HDR changes are retained. However I'm guessing that there's a pretty obvious reason not to do this (such as loss of quality)? Is that the case, or is this a long-winded solution until HDR compatibility improves? Also weirdly when I batch save as JPG from TIF, half of the images come throught about 8mb, but the other half are 30+mb JPGs. All came from the same size TIFs and were consecutive shots on the day with the same settings. Any ideas why this might be happening? Thank you LR Communit

Great, that it is now possible to filter for exported images. But IMHO it needs some fine tuning to be useful (at least for me): In the SmartCollection we have the filter "is (not) exported" – and a date needs to be provided.  Dunno for what this date is good for, if you want to filter if the image is exported at all. In the Attributes filter, the exported yes/no condition works as expected. (So, I guess, it is a mistake in the case of the SmartCollection).The exported flag should be set to "not exported" when the image is re-edited: The exported flag is set if the image was exported sometime in the past. But: When you make further edits, the earlier exported image does not reflect the latest edits. So, when you make changes to the image, the exported flag should be set to "not exported".The same should hold true for Vitual Copies: The state of a new virtual copy should be set to "not exported".It would be helpful to save a list of filenames of the collection, e.g. for backup

I'm very new to trying to actually, legitimately learn to use Lr & Lrc. The ADHD has never allowed me to organize anything in my life. Now the meds are working pretty good and I'm motivated. However, Lrc and this whole catalog thing has me quite confused. I'm real big on using my iPad. It's the only way I get any work flow at all but tagging is like painting a wall with a toothpick. I love tagging in Lrc but then all of my keywords just remain on the desktop in my catalog. I read something about having to export each photo as a jpeg with the new keyword. That seems extreme. Is there a way to just tag and sync all of my Raw Nef files in the cloud from Lrc? 

Lightroom Classic version: 13.3 [ 202405092057-40441e28 ]License: Creative CloudLanguage setting: enOperating system: Windows 10 - Home Premium EditionVersion: 10.0.19045Application architecture: x64System architecture: x64Logical processor count: 8Processor speed: 3.6GHzSqLite Version: 3.36.0CPU Utilisation: 12.0%Power Source: Plugged In, 255%Built-in memory: 40863.5 MBDedicated GPU memory used by Lightroom: 689.1MB / 2007.3MB (34%)Real memory available to Lightroom: 40863.5 MBReal memory used by Lightroom: 4146.8 MB (10.1%)Virtual memory used by Lightroom: 5170.4 MBGDI objects count: 1043USER objects count: 3700Process handles count: 2461Memory cache size: 4718.7MBInternal Camera Raw version: 16.3 [ 1863 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 1927MB / 20431MB (9%)Camera Raw real memory: 1775MB / 40863MB (4%)Cache1:Preview1- RAM:40.0MB, VRAM:0.0MB, _V3A3343.CR3Preview2- RAM:22.0MB, VRAM:0.0MB, _V3A3340.CR3Final3

Galleries I deliver have some images showing up as grey boxes only.  When I attempt to make a minor edit on the image, it will then re-sync and show correctly, but another will disappear into grey.  This is extremely inconvenient for my schedule and business.

Não consigo usar "abrir como camadas no photoshop", aparece como inativo.

Using Windows 10 Pro 64 bit and latest version of LR Classic (12.3 release).  Installed PS Beta to try the new removal option.  Afterward every time I try to "edit in" from LR, it chooses PS Beta instead of PS 2023.  So I uninstalled PS Beta and now LR won't edit in PS at all.  Checked preferences and the box to select PS version is greyed out so nothing can be entered to tell LR to use PS!!!!  😞  I tried using backup catalog from before Beta and still greyed out.  I hope this isn't going to require registry editing but regardless, can anybody out there tell me how to get LR to allow PS 2023 to be in the "Photoshop version" box?

J'ai créé des mots-clés qui commencent avec cette lettre comme : Éric, Égypte, École, église, épeuré. Je n'utilise pas les autres accents de la langue française dans la création de mes mots-clés. Lorsque je veux donner ce mot-clé à une nouvelle photo, LrC ne le trouve pas dans ma liste, mais si j'écris gypte, il trouve Égypte. Par contre, si la lettre é se trouve dans le mot, LrC le trouve, comme : Dédain, Dérive, thé. Photoshop peut-il corriger ce bogue? (personal information removed)  

Changes to the LR 13.3 SDK compared to the LR 13.2 SDK: Lightroom Classic SDK Programmers Guide -- According to Adobe Acrobat, only one substantive change on page 8: "Lightroom Classic uses version 5.1.5 of the Lua language". Past versions said "5.1.4", and I'm assuming this was an intentional change. Lua 5.1.4 was released 8/22/2008, while 5.1.5 (the last version of 5.1) was released 2/17/2012. It appears at some point Adobe changed LR to use 5.1.5. Addendum: Externally Controlling Lightroom Classic -- this short guide was restored to the LR 13.3 SDK after having been missing for many years. Sample Plugins: The sample plugins accompanying Addendum: Externally Controlling Lightroom Classic have also been restored: midiMapper, remote_control, remote_control_sock, remove_control_socket_example, remote_slider_control API Reference LrCatalog - catalog:updateAISettings()New method LrDevelopController- New parameter names:  LensBlurActiv

My Windows 10 LRC catalog has 183,500 images imported over a 13-year period, starting in LR3. Since v12, when I initiate my LRC shutdown, my 12Tb WD Red (50% empty) hard drive spins for six and a half minutes before LR's Back-up dialog appears. After I click on Back-up, the PC stays on "backing up..." for about nine minutes, and the green progress bar stays about 2mm wide. Then, it takes about one minute to copy the catalog, about one-and-a-quarter minutes to optimize the catalog, and one-and-a-quarter minutes to compress the catalog, then shutdown completes. I back-up once a day and regularly delete back-ups that were more than two weeks old. LRC back-up never advises there are any database integrity or optimization issues. Error-checking the drive in Win10 reveals no issues and it is 0% fragmented. Can I get "back to normal" back-ups by:- creating a new LRC catalog; if I did, would I lose all my cataloged edits?- uninstalling/reinstalling LRC and co

The LR 13.2 SDK on Mac provides many new string methods: findx, gfind, gmatch, gmatchx, gsubx, ifind, ifindx, igmatch, igmatchx, igsub, igsubx, imatch, imatchx, matchx The "i" versions (e.g. ifind()) appear to ignore case, e.g. ifind() is the case-ignoring version of find(). But what do the "g" and "x" versions do? (E.g. findx() and gfind()?) Also, none of these are available in the Windows LR 13.2 SDK.  @Rikk Flohr: Photography, perhaps you could ask the developers about this? 

Is this a general thing or only happening whiles it's reuploading my shared images?

When I attempt to import photos from a sdhd card to the folder on external drive where I keep my photos I get the message-The destination folder /Volumes/XDrive4gb/Photos/LRCC  is not available. Using Pictures folder instead.Only the folder IS available. Its icon is on the desktop and it is listed as a drive on the left hand of the LRCC page. The drive is only 20% full.And- there is no choice but to click the "ok" button or force quit the program. I do not want mulitiple locations for my photos, as it has cost me hours of work and problems in the past.Anyone encountered and conquered this problem.Thanks,Charles

I had no issues exporting all images from a Collection, when it then stopped exporting at a given image. When I picked up where I left off, I could export one at a time, and sometimes three at a time, but then it would take forever at some point, so during that slow phase I'd go to the finder and see the icons for the new images being copied over displaying the temporary TIF icons, not the tumbs you get when the export is complete. I've not done anything to change directories or such, can locate the files just fine in the Directory, everything looks normal. What could be the problem?