Lightroom Classic

I purchased sever profile packs from Cobalt. These require base packs which I also purchased and installed (for my specific cameras).I installed the Cobalt profiles with no error message. I open a raw file taken with a camera I installed the base pack for. But the Cobal Film Emulation Profile do not show up in the profile browser.I checked via the manage profiles if it is hidden. It does not even appear in the list of profiles inside the manage profile window.Any tips on what to do? I checked the profile folders in LR and I can see the Cobalt Film emulation profile in the directory.

I am working with an Epson SC-P700, Windows 11, Photoshop & lightroom classic. The Epson drivers can show a preview of the image to be printed before committing ink to paper. I am trying to print grids of photos on A3 and A4 sized paper which will be folded into booklets - the folding process means alternate rows are inverted.In lightroom classic I start by selecting A3 borderless in Print Setup.  I can define a cell 419.8x297mm which is the full size of A3 without any border deductions. And in layout style I select custom package. I want an 8x4 grid, so I set a cell size of 52.475 (419.8/8) x 74.25 (297/4), having set the size I just keep clicking the cell size button under add to package, and I get all 32 cells without going to a new page. I put pictures in the cells and print. What the Epson preview (and print if I allow) shows me the lightroom image  been heavily clipped at two edges and lightly clipped at the the other two, but it does print right to the edge of he the paper. 

Hello, I need some help please.I can't import photos into Lightroom Classic. When I try to locate the folder, the thumbnails appear gray with no preview. When I try to quit the software, it crashes. I've tried everything: updates, creating another library, uninstalling and reinstalling Lightroom Classic, restarting—nothing works. Thanks

I'm running into an issue with Lightroom CC's Denoise feature and wondering if anyone else has experienced this.In the past, when I wanted to denoise an entire album, I would apply Denoise to the first image and then sync/paste the settings across the rest of the photos. Lightroom would take some time to process everything (sometimes several minutes or even hours), but it worked correctly.Today, I tried the same workflow and noticed that although Lightroom indicates the photos have Denoise applied, the images clearly have not actually been processed. The Denoise check mark appears to be there, but there's no visible noise reduction.So far I've tried:Restarting Lightroom Restarting my computer Checking that Lightroom is up to date Syncing settings from both Library and Develop views Reapplying settings multiple timesHas anyone seen this behavior before? Is there a known fix, or could this be a bug introduced in a recent update?I am using Lightroom Classic (15.3.1). Any suggestions would

When exporting a developed and saved closeup ,psd of a subject from Lightroom, the skin tones on the resulting .jpg are splotchy, exhibiting random areas of pink and yellow. It is doing that consistently. This morning, I also found a .psd with the same problem. I’m rendering the .psds in ProPhoto RGB and have tried, unsuccessfully, to see if the GPU might be causing the problem.        I also received suggestions to try to export the .psd from Photoshop, as well as adding a very low additional noise (.3%). They didn’t help.

When I use the crop tool on an image and select next image the crop lines remains but the only tool option is zoom. I then have to close and reopen the tool to do the next image. This cropped up a few months back in questions but thee was no apparrent resolution

Lightroom will not open the icon pops once then noting happens, it doesn’t even seem to try.

I'm bitten yet again by Lightroom Classic's inability to move image files to my system trash.  I've gone through all the solutions I could find:Turned off Full Disk Access for Lightroom, restarted, turned Full Disk Access back on.Created an empty folder on the affected disk and trashed it.Created a Trash folder on the affected disk.I've run Disk First Aid on the disk. I still cannot move image files to my Mac's trash. I'm only allowed to permanently delete them. Are there any new solutions? Thanks for any help. MacOS Sonoma 14.4.1Mac Studio with Apple M2 Max

Lors de l'export de mes photos, ça me demande une MAJ des suppressions genératives (alors que je viens de les faire) et lorsque je mets à jour ça n'exporte pas avec les suppressions génératives ! J'ai tout essayé avec et sans MAJ - ça ne veut pas exporter le fichier final avec mes retouches de suppressions et masques

My old laptop was set up to use OneDrive for the photos and catalog.  However, I want to set up my new laptop to use an external drive for the photos, put the catalog on the laptop SSD and let OneDrive hold the backups.After several attempts to make this happen, I am at a standstill.  I have copied the photos from OneDrive to the external drive, I have placed the catalog and backups as noted above.  However, Lightroom still goes to OneDrive.How do I get it to get the photos from the external drive and ignore OneDrive?

In the LrC Publish Module for Smugmug, I have galleries set up with smart collections.  I see that if a photo has status “Deleted Photos to Remove”, no keywords are shown in the “Keywords tags” panel on the right side.  If I examine photos in the “Modified Photos to Republish” or the “Published Photos” status, all their keywords show in the keywords panel.  If select one of the “Deleted Photos to Remove” and then right click to get “Go to Folder in Library”, there all the keywords are in the keywords panel.  If i select a photo in the “Modified to Republish” or “Published Photos” and then change it color tag so that it no longer meets the smart collection criteria to be published in the gallery, it pops up into the “Deleted Photos to Remove” and the keywords disappear in the keywords panel.  I believe this is a bug since before a click Publish to delete photos I want to check keywords to be sure they should be deleted.  

I recently updated my version of Lightroom and moved to the 15.4.1. since then I have a problem of AI storage. all the modifications I do (remove with AI, denoise...) do not work or are lost when I work on another photos. I tried to follow all the steps mentioned by adobe.com, but nothing works. what should I do. the message error I get is “AI Edits Storage Issue - Lightroom has encountered an issue updating AI edits. Future AI edits may not be saved and could be lost. Please contact Adobe Customer Support for troubleshooting”.Unfortunately I can not contact anyone, apart from posting a message here.What should I do? I am a professional photographer and need LRC to work. thanks a lot for your help Emilie

Re. lightroom classic.  Nothing has been changed by me.  Nothing wrong or changed with my computer or my camera.  Happened out of the blue. Have been using with no issues for the last few months. Sudden problem/ change happening.After importing images into lightroom classic, embedded picture preview is fine (same coloring as image viewed on camera and on computer prior to importing into lightroom). After going from library tab to develop tab lightroom is all of a sudden automatically drastically changing image colors/ exposure/ light balance (to be much brighter and yellow).  Histogram/ tone changes aren’t illustrated. When going back to library tab, it no longer shows the original embedded preview (that was the same on camera and on computer) but the change that was made automatically by lightroom. Why is this suddenly happening?(I know there are differences between jpg and raw, as per my attached; the issue is the changes automatically being made once moving to develop tab - vastly d

This issue affects Lightroom Classic version 15.4.1. I am using Windows 11 Home Premium Edition, version 11.0.26200. The camera model used here is a Fuji X-H2s but I would expect this to similarly affect the X-H2, X-T4, X-T5, and all other recent Fuji camera models. The “show clipping” feature does not work with Fuji RAW files when certain camera profiles are selected. Affected profiles include Nostalgic Negative, Bleach Bypass, Camera Sepia and Classic Neg. Here are some screenshots with exposure and whites deliberately raised to show some obvious example of the issues:   With ALL other Fuji profiles, e.g. Provia, Reala Ace, etc. the show clipping feature works as expected, as seen here:  This issue affects both highlight and shadow clipping. For example, here is Nostalgic Negative which is not showing any shadow clipping when exposure and blacks are reduced:   And here is the same image using the Astia profile, which is one of the unaffected profiles:  

I’ve been using Lightroom forever.   I have a large catalog.Over the last 6 months lightroom has become very unstable, crashing during every session, often multiple times.  Sometimes the crashes are the just closes, sometimes the bug report dialog pops up and sometime my computer blue screens.I have reinstalled my operation system clean.  and did a clean install on my creative cloud apps and tried a creating a new catalog (only importing a small number of files).I have run every manner of hardware diagnostics; memory, cpu, hard drive, search for driver conflicts, chkdsk, scannow - all come back clean.I’ve updated all my drivers; including my graphics drivers.And still Lightroom is crashing.I’ve tried turning off the gpu and everything else I can find online for troubleshooting and nothing works.I’ve not found a pattern to the crashes; I do a lot of basic editing of Raw files, export to jpg and export to Photoshop for more heavy editing. I would be grateful for any help you can offer. 

I tried the “convert to DNG” function and in INCREASED the file size. Settings were:Only convert Raw files (obviously) Delete originals after successful conversion Extension: dng Compatibility: CR 16.0 and later JPEG Preview: None Emebed fast load data: NO Use Lossy compression: NO Embed Original Raw File: NOWhile I do understand the benefit of DNG over proprietary raw, for long term support, I do not think it’s a good idea to allow an increase in file size without a warning.While the alleged open character of the dng format is a good selling point, I do not think it’s going to be an issue to open raw files in the future. Nevertheless, I appreciate that option. Therefore I think the main selling point of dng would be a higher compression yielding in smaller files.Note: I also know that a Lossy compression would obviously output smaller files, but that’s not the point. 

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

since updating to 15.3, I’m finding that Lightroom Classic is quickly hitting a memory leak and freezing or crashing.  I’m processing RAW Canon CR-3 files, often adding AI object removal, and synchronising my edits across groups of photos (including masks, AI object removals & colour grading).  I find that I can only run for approximately 30 - 60 minutes before I start to encounter memory issues and either the app pauses (and doesn’t come back to life) or crashes altogether.  I keep getting error messages telling me that my system has run out of memoryThis has only been a problem since updating to LrC 15.3 a few days ago.system tech specs: MacBook Pro (16-inch, 2021)Apple M1 Max64gb ramMac OSX 26.4.1  

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