Lightroom Classic

Ten years ago I started in LR and picked up bad catalog management habits which I finally want to get around to resolving.Current set up is Mac Studio M3 Ultra, 2 tb internal SSD and 256gb RAM. Running Lightroom Classic.I have two catalogs I switch between-- one with about 90,000 images and the newer catalog with 35,000 images. Virtually all images are Sony .ARW uncompressed or lossless compressed.The images are spread across 3 external high speed Thunderbolt 4 and Thunderbolt 5 SSD drives-- 1 8tb and 2 4tb. I often have to switch between catalogs depending upon the images I want to work with. Now with LR’s recent switching feature that it as simple as “Open Recent” and letting LR relaunch.I back up each SSD to a separate external spinning hard drive in OWC drive docks using CarbonCopyCloner and save my catalog backups on another external SSD I use for completed video short projects.I built smart previews of some imports but not of others.It seems more convenient to merge catalogs by o

so my Lightroom Classic 20gb is FULL. Im not sure I really need those images, do I?  when editing I use an ssd so raws and edited are all available to me.  the kind support at adobe, instead of explaining stuff just attempted to sell me firefly.  Im really trying to reduce my reliance on clouds as it simply costs   so the images I see on my cloud, I have all on a SSD? can they simply be deleted?

Lightroom Classiv v15.3 (on Mac OS Tahoe) has a problem importing photo files that have a pipe symbol - a | symbol - in the XMP field dc:subject.Lightroom apparently has a problem interpreting the pipe symbol, and then hangs, seemingly indefinitely until the import is cancelled, while showing a high level of CPU usage. This hanging seems to take place at the end of the import process for this photo.The pipe symbol is used by Lightroom to separate levels in the keyword hierarchy within the Hierarchical Subject XMP field.  Having pipe symbols also within the keywords doesn’t seem to be a problem with the Hierarchical Subject field - at least it doesn’t interfere with importing.  Also the pipe symbols in the Weighted Flat Subject field don’t seem to cause a problem with imports.Attached is a sample file that hangs when being imported into Lightroom.  Of course, a problem file causes a batch import of photos to fail, with some number of files correctly importing until Lightroom does to pro

When I export a batch of photos, each and every one has an “Exported <date>” entry added to its history. This adds nothing to the image. Is there a way I can suppress this auto-entry of non-”history”?

In the Develop module of Lightroom Classic (I have version 11.2 running on Windows 11), in the Lens Correction panel, if I select "Enable Profile Corrections", the entries are blank. So Lightroom isn't automatically detecting my camera (Nikon Z6 with the kit lens 24-70mm f4 S). I can manually set the Make to "Nikon", but the Model popup only has a few choices, and the Z series of cameras and lenses are not among them. In the Metadata panel of the Library module, all of the information is correctly recorded in the image file. (RAW, JPG, etc). This camera was released in 2018, and has since been replaced with the Z6II. The Z5, Z7, Z7II, Z50, Zfc, and Z9 are all missing as well. (Admitedly, the Z9 is very new.) All of the Z lenses are missing. The Z cameras are Nikon's flagship DSLR, so I'm not understanding why these lens correction profiles are absent in Lightroom. I was told by Adobe support to post this error on this forum.

Hello - I just used the new Duplicates finder tool.  And accidentally hid several files versus deleting the duplicate.  The interface shows the number of files hidden, but I’ve not found a way to “unhide” those files.Is there a way to “unhide” or view the hidden files in Duplicates tool? Thank you

I cannot find files after updating LRC

For a long time now, Lightroom has been using almost all of my VRAM. This problem has affected three different windows PCs.   My main editing PC has a 4090, and Lightroom will start using 22-23 gigs of VRAM in less than 10 minutes while editing just one photo! I have to restart the program frequently to dump the memory. I don’t want to disable GPU acceleration, but why is there no option to limit how much VRAM the software is allowed to use?   My previous PC had a 2080 with only 8 gigs of VRAM, and I was still able to edit R5 RAW photos without any major issues. other than needing to restart a lot to dump the vram.   Yes, I keep my drivers updated. This issue has affected me for possibly 1-2 years now across different PCs. From what a few people have told me, this is a Lightroom problem because the software by design is to use all the VRAM it can get its hands on. But how does no one see that as a problem? When you hit 90%+ VRAM capacity, the entire PC slows to a crawl!

Than I selected next photo with Crop Tool activated, Crop tool switched to Zoom Tool but crop marks remains visible and Crop tool panel turns grey. I need to turn off and on Crop Tool to make it work again.LrC 15.2, Intel Mac, the same issue was in previous version too 

I cannot update LR to a version which I have on m laptop. Laptop has 15.4, home computer has 15.3.1 and Creative Could is not capable to find the V15.4 and to update my main version. Thus a catalog exported with photography on the road cannot be imported to the main workstation. 

I have an LrC catalog with 20,000 images - mostly dng, with a few hundred jpg and heic files. Things looked normal in LrC and there was no major global operation done, but at some point I noticed that dozens of jpg and heic files showed only a preview image along with a “waiting for settings” message in LR Mobile. On the web, those images show “Error rendering”. LrC showed everything synced with no errors. I tried suspending and resuming sync on LrC - no change. I tried tweaking a develop slider on one of those files. In some cases that fixed the problem; in others nothing happened. I picked 5  of those images and removed them from “all synced images”. They were correctly removed from the cloud. When I re-added them to a synced collection, the sync of those files hung. Other files continue to sync normally. I took a diagnostic dump of the state with 5 files hung and the dozens of other files showing “Error Rendering” / “waiting for settings”. Even if tweaking settings would reliably co

test q

TERRIBLE UPDATE. LR Classic auto-updated with the latest version 15.4.1. I did not ask for that. And since the update, my exports look like a disaster. Completely washed out.I understand color space - I know they won’t look identical to the original file -- but generally LR did a good job - it was very close. Never had an issue in all the years of using this app. Suddenly now the exports are a disaster.I immediately downgraded to 15.3.1, and luckily was able to restore my last Catalog as well. (did not update other catalogs, thank goodness)Well, all that for naught because my exports are now still terrible. I have no idea what is going on. I’m making the edits extreme, in order to somewhat compensate and nothing is changing its he exports. Just absolute dreadful color. And it’s hard to show this considering anything on the web converts to sRGB anyway… so it won’t be true representations. This is the best I can do - a screenshot: http://hnydsn.com/i/6jEPf3LEFT is the export preview. RIG

Importing from a catalog is approximately ten times slower than importing directly from a memory card. I just imported a catalog of 259 photos from another catalog and it took as long as importing 2500 photos from a memory card would take. The ssd is plugged into a very fast USB port and has a transfer rate of over 1000 mb/s. Is this bug common?

Here is a case of not being careful and dumb! Wondering if there is an well defined way for recovery instead of doing this manually for recovering 12K photos. The following steps got me into problem: I am using a Macbook Pro M5 with LRC. I import the raw files from the Compact Flash card into a local catalog on the internal SSD. Process them. In this case, I had 51 files after processing a day of birding. Then I open the large 47K files catalog on my external 4TB SSD and import all the files from the “local” catalog. Then I switch back to the “local” catalog and delete all the files, keeping it ready for next set of raw image imports. However, this time, I accidentally opened the 47K catalog, flagged all the files “Rejected” and then deleted the files from the drive. I realized the blunder in a few seconds and force closed the app. By that time, the Trash folder had 12K files and all those images have an “!” sign indicating missing files.I have made a second copy of the 330GB of files

I'm using Lightroom Classic 14.1 on macOS Sonoma 14.7.2  I'm trying to import photos and videos from my iPhone 14 Pro/iOS 18.0.  The import process never ends.  What happens is:Start the import process to import ~1000 items from my iPhone attached directly via USB-C Lightning cable.  The destination folder is one which Lightroom has successfully imported photos from my SD card.At the start of the import process, previews for a few photos are displayed initially and then none until I cancel the import.After a few minutes, the progress bar shows no progress.If I cancel the import process, an error is displayed. "The following files were not imported because they could not be read or the destination is not writable (1)"The error shows a number of video files that could not be imported.  In this example, these files are 452,659,828MB. Over several imports, videos over 1GB in size have been imported from the iPhone, so sizeof the .MOV files doesn't seem to be t

Lorsque je sélectionne l’une des trois propositions pour remplacer l’image dans le cadre d’une suppression, in fine, le résultat après validation est différent des trois propositions. What did I do wrong ?

I recently had to move my photos folder from one place to another (old drive died, copied files from a backup to a new drive). At the same time I updated to the latest Adobe, that now has assisted culling for example. Main catalog updated fine, was able to view photos etc. Then I tried to import. Since it's a new version of adobe it's now showing me the new fetaures.. in this case assisted culling. No problem, click on the X to close the dialog.. nope.. hmm.. I can't click anywhere to get rid of the dialog. Thought maybe adobe crashed, so i clicked on another window and low and behold there's another dialog behind the culling sample one.. it's showing that the old destination folder no longer exists, which is true. Ok, click on Ok. Nope.. instantly the culling dialog is back.. so now I'm stuck. I can't close the culling dialog, and I can't close the missing destination folder dialog. I can only kill the process.. Anyone have a solution for this crazy one?

I’ve successfully been using denoise since it came out in LR Classic, but now it has stopped working. I use 14.5.2. I tick the Denoise box and it produces a progress bar but then stops. I asked Chat GBT and it tried lots of things (I reinstalled LR) but it eventually said ask Adobe. Here is the Chat GBT chat: https://chatgpt.com/share/6a3d7c65-5564-83eb-ba38-ecdfef8e9588 Any human ideas?

The update to the Generative Remove AI model in Lightroom Classic 14.5 has ruined it, as it now changes elements outside the painted mask, making it more or less unusable in many situations.

HI EVERYONE!  Im having a problem where i dont know how to remove the wave looking thing on this guys tuxedo all answers help if you know what you are doing ! (on his rigth shoulder ) 

Previously I used LrC 12 (and other versions). Recently I installed LR 14.1.1 on a new system. Now the suggested names on recognized face regions look bad. I attached screenshots to show the issue, unfortunatly the screenshots do not show the whole extent of the problem; They look a little bit softer than the original LR interface on the monitor.    System Details: Windows 10 22H2 nVidia GeForce RTX 4070 S GPU driver version: 566.36 (studio driver) DirectX 12 24" LCD with 1920 x 1200 px resolution / 22" LCD with 1680 x 1050 px resolution (both 8bit, 60Hz) Issue happens when Windows UI scaling is set to 100% (default) as well as when it is set to 110%.   Manually added person tag – a bit blurry but ok:   Suggested person tags – double letter edges or something, seemingly on some backgrounds more than on others (but sometimes more on dark and sometimes more on bright backgrounds), mostly on letters with straight lines:  after accepting a suggestion it looks a

I have applied Auto in the develop module then selected denoise and this error occurs.

I logged into LR Classic this morning and a message popped up with an update and that I should back-up my catalogue, which I did, however, all my photos have disappeared!  When I open LRC now it is empty!  What have I done?  I chose to back-up to Google Drive rather than Cloud, is that why?  Can I reverse it?