Lightroom Classic

The new quickDevelopAdjustImage can use the parameters 'small' and 'large' which are aligned with some of the Quick Develop buttons. However, those are only for INCREASING the values. There are no parameters for the Quick Develop buttons that DECREASE the values. This severely limits usefulness of quickDevelopAdjustImage.Request: Add parameters that are aligned with the Quick Develop DECREASE buttons.

There needs to be some way in Lightroom Classic to identify photos containing Depth Map information. I notice that (Non-classic) Lightroom CC has a search "facet" for Depth Map - why not Lightroom Classic?  So unless I've missed them somewhere - please consider adding:1) Filter criteria - Depth Map:  Contains Depth Map, Does Not Contain Depth Map2) Grid Thumbnail Badge Icon:  Photo Contains Depth MapThanks!PS - I realize I could narrow things down a bit by searching for File Type = HEIC, but that still gives a superset of the desired results. Further, in the future I expect that other file formats besides HEIC could also contain depth maps. 

An annoying feature that I often run into is that when using the graduated filter, for instance, the setting for the adjustment brush last used is retained, not the last adjustment for the graduated filter. Can't these settings be retained independently of each other? The last setting used for each tool should be exclusive to that tool alone. The adjustment brush shouldn't be the 'dominant' setting. Feel me?

When working on a set of images (be it a collection or previous import or all photographs) I would like to be able to see how far I am.So a counter showing I'm working on photo 39 from 77 would give me a better clue of how much I have done and how much I still have to do, than looking at the position (and size) of the scroll bar underneath the film strip.

I would love to see my develop presets syncing through to Lightroom Mobile. So I can work faster with my known Lightroom presets.

When looking to streamline workflow there may be more than one effect to be applied with a given local adjustment tool. It would be very helpful from a workflow perspective to be able to select a tool with a specific effect with a shortcut - it would also be great to be able to do this with 3rd party peripherals via an SDK call. The ability to cycle through the effects menu would also be useful. I believe there may already be a request similar to this per LRD-4201731. Thanks!

Is there any way to have a new cell automatically created when a photo is dragged in. Most othet 'book' programs work that way.

As title say i would love to se any kind of devolopment in tethering capturing.I will not write what can be improved as i think from the competitors and recent market is obiusly that we need some chages in this part of program.Wish to see some changes in 2018

I am writing this Feature Request in accordance with Victoria's guidelines posted here: http://feedback.photoshop.com/photosh... and comes from use of the Trial version of DSLR Remote Pro from breezesys.com (hereafter referred to as DSLRRP) during a product photoshoot. THE FEATURE REQUEST: I'd like to see a LOT more Camera control in the Tethered shooting module, along the lines of the DSLRRP software, which allows control of most of, if not all of, your Canon or Nikon Cameras' setting from your Laptop, without touching the camera. And includes some other nice bells 'n' whistles. Below is a list of features I'd like to see integrated into Lightrooms' tethered shooting, taken from the features for Canon cameras in DSLRRP, I assume for the Nikon version also. So if it works there, I see no reason that Lightroom can't also integrate these features. Also, this is a personal preference, feel free to discuss/add/subtract features. Primary Features (in order of preference to be added): Shutte

Large or multiple smart collections can seriously impact performance.It would be useful to disable a smart collection or, even better, disable a set of smart collections, so they are no longer processed until re-enabled.As it is we can only delete the smart collections and recreate them when we need them again next month.A selective export and import option of smart collections would serve a similar purpose and would add functionality to LR but would not be as simple to use just for this disable/enable purpose.Whilst here I would also like to add my vote to the many people who have asked for a smart collection A only to select images from within smart collection B. Though I can see some concerns: how many levels down does it allow should B only select from smart collection C, etc. That is maybe why they have not implemented it. Also there would be a possibility of creating an infinite loop should smart collection A only select from B but B is set up to only select from A. Perhaps it co

Hi, I was wondering if there was a way to zoom up on the print layout in the Print Module? I am trying to create custom print templates and would like to be able to zoom in to see the layout in more detail. I know the other modules have the ability to zoom in. But I have not found anything in the print module. Looking at the forums, this idea has been asked for since 2007. Thanks atstein0303

I have discovered through experimentation that photos published to Facebook look best at 2048 pixels on the longest side (the maximum it supports) but images measuring 960 pixels on the longest side come a very close second so that's what I export at when Facebook. I also publish the images on my own website, which uses SmugMug as a backend and is capable of automatically displaying delivering higher resolution photos (than Facebook) to the browser depending on the viewport size, so I export at 1400px resolution to strike a balance between filesize and image quality. My problem is that it's not currently possible to export these two sets of images at the same time, I have to do them one after each other (because doing them in parallel is MORE than twice as slow due to LR's poor parallelisation of task execution), manually switching between different export resolutions and folders. Instead, I would like to be able to pick two (or more) resolutions to export at, set (sticky) subfolder na

There is a feature in Bridge that allows you to batch rename files while preserving the original filename as a new field in the metadata. This feature would be great to have in Lightroom as well, most likely as a checkbox option under "file renaming" of Export. When dealing with loads of files, it ensures that no matter what the file is renamed we will always be able to track back to the raw file. I saw someone posted about this 10 years ago in the adobe forum so I am guessing that it isn't super important...

In the LrDevelopController namespace, add to Localized Adjustments brush parameters: Size Feather Flow DensitySo that those parameters can be used in the following LrDevelopController calls:getRangegetValueincrementresetToDefaultrevealPanelCurrently have: "local_Temperature" "local_Tint" "local_Exposure" "local_Contrast" "local_Highlights" "local_Shadows" "local_Clarity" "local_Saturation" "local_Sharpness" "local_LuminanceNoise" "local_Moire" "local_Defringe" "local_Blacks" "local_Whites"This would allow users to manipulate brush parameters through a plugin just as they can already manipulate the other localized adjustment parameters. This is a common request from my plugin's users. (My plugin allows users to manipulate Lightroom through MIDI control surface knobs and switches).

Currently, you can find which Module is active (LrApplicationView.getCurrentModuleName()) and which Tool is selected (LrDevelopController.getSelectedTool()), but you can't find out which Panel (adjustPanel, tonePanel, mixerPanel, detailPanel, etc.) is open.While you can manually reveal a panel (LrDevelopController.revealPanel()) (and thus know for a second or two which panel is showing) you can't see what panel has been opened by a user action or by manipulating a develop parameter while LrDevelopController.revealAdjustedControls() is true.This creates a problem for plugins that want to present the user with different options depending upon what edit mode the user is currently in. My plugin, for example, allows users to map MIDI control surface knobs and switches to various Lightroom actions. When a user is in a different edit mode, the switches and knobs may be mapped to different actions (e.g., what's useful in the detail panel is different from what's useful in the transform panel,

Please add a warning dialog, if one tries to export from smart preview files.I learnt the hard way, that Lightroom exports files no matter what. Unnoticed I had lost my server connection, when I exported some files. The resulting files were a lot smaller than my usual photos and it seemed to me as if I had made some wrong settings. I spent literally the entire night looking for solutions online, until it dawned to me the next morning, that the culprit was the missing server connection. So please, please, please add a warning dialog to the export functions, once one tries to export from smart preview files.

As the topic says, Import from catalog sets both "filename" and "original filename" fields of each imported photo with its actual file name. Instead it should set the original filename field of the imported photos in destination catalog just like the corresponding field of the source catalog.My issue: Ihad many small catalogs, in each one I had renamed files with a custom preset "Date-Custom text-Original filename". When I decided to merge them injust one catalog I've lost all original file names (DSC_xxxx.NEF). Indeed after the"import from catalog" process the original filename has become like "Date-Custom text-DSC_xxxx.NEF". I'm importing new files (not from catalog, just the standard import of new photos). So if I should need renaming all the photos with a different structure (and I do), for example "date-original filename"(without any Custom text), I cannot do it anymore with the old ones imported from catalog, as I would have unexpected wrong result. I think it should be very easy

If you have hundreds of folders, it's burdensome to select and move images to a second folder which can be hard (and certainly time consuming) to find.   Would be great if you could select the images,  then click on the "Recent Sources" (or "Favorite Sources")  triangle in lower tool bar to bring it up, and then move your selected images to that folder.   What happens now is you lose the selection when you click the triangle.Or I'm open to some other clever method of getting the two folders easily that I don't know about.  It's much easier with Collections where you can make one a target and then move all images in with a simple "b".

In the new LR4 Book module, is it possible to also provide a jpg/tiff option instead of just pdf? Quite a few book printing companies do not accept pdfs, and we will have to us their inhouse software.

In Photoshop CC, Under Edit/Preferences/Interface/Experimental Features:Scale UI 200% for High Density Displays (Windows Only). Could you add an option for 150%. I have a 27" HD Display running 2560x1440. I am already running my display at 125% which is effective for all other Windows Applications that I use. But it has no effect for Adobe Elements, Lightroom or Photoshop CC. The option for 200% in PS CC makes everything too big again, but I think 150% should do the trick. Could you add this option in LR and Elements also? Thanks.

HDR works great inside lightroom.Panorama works mostly great inside lightroom....It‘s a pitty a always have to merge my bracketed shots to HDR images... and then to merge them again into a panoramic image. It would be great to have lightoom do this for me. Just select all the images and do a HDR-Panoramic-Photomerge. Done! Please add this feature!Oh... and don‘t forget to implement it into the mobile version as well! 😉

Currently it is not possible to invoke a re-indexing of facial recognition data at either the global or folder/collection level. For my purposes re-indexing at the folder and collection level would be sufficient. Reason: when a face is removed from a previously indexed image it is not possible to automatically recognize faces other than reviewing many images and manually applying a face region. See this forum discussion: https://forums.adobe.com/message/7472...

Keywords modified in Lightroom CC do not sync back to Lightroom Classic. This is a known limitation, and there don't appear to be plans to resolve it. That's disappointing. But what makes it especially frustrating is that the behavior is unexpected and thus reads like a bug. In my case, I spent an hour troubleshooting synchronization between Lightroom CC and Lightroom Classic before looking online, and discovering that it was "by design".Given that, at minimum, it'd be nice to see a warning given when users attempt to add or modify keywords in Lightroom CC for photos that are synchronized with Lightroom Classic. That way, they don't make the mistake of updating their keywords in Lightroom CC in anticipation that they will be available later in Lightroom Classic. This could even be a one-time warning. The goal is to ensure that the user is notified of the limitation since it's not otherwise intuitive or expected.Jeremy

[LR 8.1 now displays partially compatible presets in grey italics, which will avoid the confusion experienced by many users:https://feedback.photoshop.com/photoshop_family/topics/lightroom-presets-including-raw-profiles-are-...]Presets including raw profiles via Treatment & Profile are sometimes visible in the Presets panel when a non-raw is selected, sometimes not.  This is confusing.- Presets including DCP raw profiles are visible for non-raws (Adobe Standard and all Camera Matching profiles).- Presets including enhanced raw profiles are not visible for non-raws (Adobe Color, Monochrome, Landscape, Neutral, Portrait, Vivid).This is clearly inconsistent behavior, since none of these raw profiles can actually be applied to non-raws.  LR should either hide all such presets for non-raws or make them all available, ignoring the raw profile when the preset is applied to a non-raw.I think it should make them all available for non-raws, given this use case: People often click t

Two monitors is nice for Lightroom, but I could really use a third screen for added screen-space while I'm working on my photos. I frequently use a full screen for loupe view and a full screen for survey view, which leaves me with no place for development settings, keywords or other features. This would be great for a third monitor - having the ability to view more information and functions at once.