Lightroom Classic

It would be nice & very helpful if there would be an indicator, that there exists a synched collection under a stacked and collapsed collection. Here is an example for what I mean.  

For those unfamiliar, Median Stacking it is a process where you stack multiple images of the same scene, then a Median filter averages them out to retain only details that exist on all images.   It's commonly used to to eliminate high ISO noise in nightime photography or astrophotography while retaining stars and other details. ISO noise is random and easily filtered out with this method. It's a much better approach to standard noise reduction which adversly affects the whole image.   It's also used to remove crowds of people from a scene – you do a timelapse of the scene and then Median Stack the images remove anything that doesn't exist on multiple photos. Very nice.   It currently has to be done in Photoshop, which is a one way trip (there's a nice overview of how it's done here with some nice examples https://iwillbeyourphotoguide.com/reduce-noise-median-averaging-photos )   Instead, it should be an option inside of Lightroom Classic. A

I marked many photos to create previews and changed star rating of thousands of photos without noticing right away. Using the “edit/ go back one step” functionality wasnt too helpfull, because it didnt gave me enough info about the steps. A history menue like the one in the editing menue would be helpfull to go back a few steps when working in the library module. 

Quanto tempo si perde, dopo aver esportato le foto, nel raccoglierle e organizzarle in cartelle, suddividendole e raggruppandole per non disperderle in folder contenenti centinaia di file? Il modulo di esportazione di LrC permette di esportare contemporaneamente immagini da molte sorgenti. Usando le esportazioni batch anche in molti formati diversi, ma sempre e solo verso un unica destinazione. Non sarebbe utile poter applicare una logica di esportazione flessibile e articolata come quella d’importazione?Uso LrC dal 2007 e gestisco collezioni di centinaia di migliaia d’immagini, organizzate in cartelle e sottocartelle con molti livelli di profondità. Conservo i file originali (convertiti in DNG) e spesso li riprendo per rielaborarli per utilizzi e pubblicazioni sempre diverse. Per valorizzare l’ordine con cui sono suddivisi i file ho sempre trovato utilissimo un semplice plugin donationware sviluppato da Timothy Armes chiamato LR/TreeExporter.Con questo strumento posso esportare interi

The current AI Denoise implementation uses a static default value (50) and requires manual activation per image or batch. This is inefficient for professional workflows: Unnecessary Processing: Currently, Lightroom doesn't distinguish between a clean photo and a noisy one when syncing settings. It applies Denoise even if the image doesn't need it, wasting time and storage. One Size Doesn't Fit All: Every photographer has a different "noise tolerance." Some prefer a clinical, smooth look, while others want to preserve some natural grain for aesthetic reasons. I propose a smart and adaptive AI Denoise system with the following capabilities: Noise Detection: The AI should first analyze the image to determine if Denoise is even necessary. If the image is clean, it should skip the process or apply a 0% value. Intelligent Auto-Intensity: Instead of a fixed number, it should calculate the minimum intensity required to clean the specific grain of that file without washing out textures. U

Was going through bunch of photos I took at an event and using the tilde key (~) to check my picks for edit. Was more or less through all of the 1.2K pictures, when I accidentally hit ESC key located right above, and lost all progress. Is it really that hard to put in a "Do you really want to cancel?" pop up here? Lost like 30 minutes of work. This is UX 101 guys

Exposure Bias is not currently a searchable field, pleaseinclude it in the Metadata Library Filters. Multiple reasons why this is useful, from photographers who use bracketing, and want to sort through images at 0ev, using fixed exposure compensation on shoots and wanting to select and increase exposure in sets. The list goes on. As this is a Metadata field, and can be displayed in cells, please allow filtering by it too. Thank you.

I just updated to Lightroom Classic 14.4 and although I do like the fact that I can Denoise without creating a DNG file, I still would like the option to select a series of images and menu: Photo>Enhance... to let it create dngs in the background which enables me to work on other images while it;s doing those. Currently, in 14.4 it takes a long time, especially if I have multiple images that I am denoising and I cannot do anything elese while it's doing that process. Is there still a way possible to do it the old previous way of creating a DNG Denoised file? Seems like an oversight when implementing this new way and slows down my whole workflow.

Currently in the SDK we have LrApplicationView.getSecondaryViewName()We need to have the same BUT for the “main screen” view and thus be able to detect which view we are in the Library module.So Please implement an API to get the current “main view”Hypothetical API LrApplicationView.getMainViewName()Returns the name of the view currently showing on the main screenReturn valueviewName (string) The name of the main view being shown, one of: "loupe", "live_loupe", "locked_loupe", "grid", "compare", "survey", "slideshow", or nil. 

Just an ability to add different textures to an image.

I would appreciate if LR would support images with 65k x 65k pixels (i.e. drop the overall 512M-pixel limit). I have several stiched images, that I can not handle with Lightroom, and I do not want to use two different Applications to manage my images. P.S. and please make the limit 2^16 x 2^16 and not 65000x 56000.

I use a 13" Samsung laptop Windows-11 PC.When I open the preferences interface tab I cannot see the lower left corner button to restart Lightroom Classic after making changes to any options such as the Font Size option. Please allow user to proportionlly resize the window by grabbing a corner or top or bottom of window just like cropping an image in the Develop Module "Crop Overlay" panel.

Mouse Scroll wheel does not work on Lightroom sliders on mac. Comming from windows these function is missing a lot on Mac.

In Development module, color mixer or sharpening the idea is to press and hold with mouse, and move the slider left and right. This is not a very accurate way of changing the settings and I believe using the scroll (mouse or mousepad) would enhance this part of the edit process. For example: One could select the exposure setting, go in to ‘move slider by scrolling’ feature and scroll comfortably up and down, until a preferred lighting has been achieved. Can you understand my explanation, and what do you think?

I asked a question about the different defringe tools in masks vs. global, but no one knew the answer.  I am now requesting a new feature.  Please add the mask Defringe to the global edits.  It works much better than the current global Defringe and also is much easier to use without all the bad side-effects that the global one often has.  Currently the kludge is to create a linear gradient that covers the whole image and then use the mask Defringe, but it would be easier to just make the mask version of Defringe in the global edit controls.  Sure, keep the old one too for those who want to use that one.https://community.adobe.com/questions-675/defringe-mask-vs-global-1556459In a mask we can use the Defringe control and it works well.  Sometimes I create a mask over an area using a brush or gradient solely to use the Defringe tool.  Why is Defringe in a mask so easy to use, effective, and without the bad side effects of the complex Defringe in the global tools?The global Defringe tool r

Identifying people in a large collection can become kind of a mess, because then I might have lots of people identified and struggle to find the right people. I wish there would be the chance to create folders to group specific people, such as Family, Friends, Work colleagues, BTT Group, etc.

Following a discussion on the LR4 beta forum: Converting to CMYK and soft proofing in CMYK are two completely different things, so at least we need a CMYK softproofing. During the last years I ran into a lot of problems due to modern LED lightning on the scene, it is able to produce colors (especially in the blues) far away out of the CMYK color space. Converting pictures to CMYK later after my initial processing can change a picture dramatically, a bit similar to a conversion to b/w. So even if you have to deliver your material in RGB and someone else is doing a professional conversion later, you should be able to predict what can happen to your material! So if you deliver material that will be converted – earlier or later – to CMYK: You need at least a simple soft proof. Otherwise it can happen that you deliver material that simply can’t be published.

I would like too see the mask marked in red (my mask) in the list marked in blue (options) in attached screen shot. Better if LR can automatically (using AI like body parts in portrait pictures) create some luminance and color masks too.

Can we please get a client review system from Lightroom Classic or Lightroom Web for shared albums that allow the client to see, view, and sort their hearts and others hearts.  They need the ability to turn on and off all the other photos that have not been rated by them or others as well.    It’s impossible to use Lightroom and I need to switch from using the application and platform because there is no easy way to share an album that allows a client control over the review process.The client currently does not have the ability to sort images by my ratings, flags, or color labels.   They can’t see flags, color labels, or ratings no matter the access level given.  They can’t sort by their own hearts or comments.  They can’t see others hearts or comments.   The whole ecosystem only allows one person to do anything and no way to have a client satisfied with their control to review the images in a shared album.  This current ecosystem makes Lightroom non-professional and not fitting for a

Hi Could you please consider replacing the current jpeg export code used  by Lightroom / Camera raw with jpegli ?   I tested it and it's compression efficiency is much better than the one you currently use, resulting in smaller jpeg files for same quality or better quality files for same size   Thank you   https://opensource.googleblog.com/2024/04/introducing-jpegli-new-jpeg-coding-library.html   https://github.com/libjxl/libjxl/blob/main/lib/jpegli/README.md   https://github.com/google/jpegli  

Currently the Previous button is useful, PROVIDED you only want to apply those setttings on the next image you select. But what happens if you are scrolling past multiple frames of the same scene and then decide you want to apply those ‘previous’ settings, then you have to go back to that original edit and copy/paste it. It’s a total waste of time, especially if, like me, you use copy and paste to store your preset look adjustments to speed up workflow (so you don’t have to go up and click on the preset for each image for large volume event / product edits). Please modify the Previous button so it doesn't forget the last edit when you click on more than one other thumbnail (as happens now) and the workflow will be supercharged. Or at least make this AN OPTION YOU CAN TOGGLE on/off on the PREVIOUS BUTTON. I cannot tell you how much going back and forth this would eradicate - with Copy/Paste for your preset look together with previous for the last ‘entire’ edit (incl. crop / remove, etc)

Let me add text notes to photo, stacks of photos, and directories of photos so that I can record shot and processing details. I'd like to be able to print the notes along with an image thumbnail.

Dear Adobe Lightroom Support Team, I hope this message finds you well. I would like to formally request the addition of full Arabic language support in the Adobe Lightroom application. As one of the most widely used photo editing tools globally, Lightroom serves a large and growing user base in Arabic-speaking regions. Currently, the absence of Arabic language support creates usability challenges for many users, particularly those who prefer or rely on Arabic for navigation and workflow efficiency. Adding Arabic as a supported language would significantly enhance accessibility, user experience, and adoption across the Middle East and North Africa. Given the importance of inclusivity and localization in modern software, I believe this enhancement would provide substantial value to your platform and its diverse user community. Thank you for your time and consideration.I look forward to seeing future updates that support Arabic language integration. Kind regards,Hatem Alshammari.

Lightroom Classic already supports USB tethering for a wide range of Sony cameras. Adobe uses Sony's proprietary PTP extensions, which are documented in Sony’s “Camera Remote Command” documentation.Sony has released an updated version of its “Camera Remote Command” documentation, which explains how to add PTP-IP network support for cameras supporting Camera Control PTP 3 (models released from 2020 onwards: A1, A1 II, A9 II, A9 III, A7R IV, A7R IVA, A7R V, A7S III, A7C, A7C II, A7CR and A6700).Please add PTP-IP support to the current Lightroom Classic tethering code, so that users of modern Sony cameras can tether their cameras by Wi-Fi, built-in Ethernet or a USB-C-to-Ethernet adapter (depending on the networking support in their camera).Not only would network tethering support be a worthwhile feature enhancement, but adding network tethering will help to overcome user frustration and Adobe’s support burden from the USB driver clash between Sony Imaging Edge and Lightroom Classic on Wi

Please, oh please, add a simple liquify or warp tool to the Q panel! Wedding photographers adore Lightroom, but round-tripping 1500 photos over to CC just to give errant armpits and dress straps a five-second cleanup is an enormous bog. Lightroom, I love you. This is all I ask to make my world complete. Please, we beg of you, let us move some pixels!