Feature Requests

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.

Currently Lightroom uses the aspect ratio meta data in a raw file in a way which cannot be changed later on.It would be great, if Lightroom mapped the aspect ratio meta data, to the Crop tool in the Development section, so that the uncropped area of the sensor is available if needed.This has already been described in http://feedback.photoshop.com/photosh...

I'm working in Finland with native Finnish speaking people and don't want any English prepositions in titles when sharing the link to a Shared Collection, like "...by Anssi Kumpula". It's a bit tacky to have English in a middle of a title written in Finnish. I'd like one or the other: Default to Share without Author Default to Share with non-language spesific Author prefix, like glyphs – | ("Example Collection – Anssi Kumpula" or "Example Collection | Anssi Kumpula") When sharing a Collection without Author I can then write my Author information in native Finnish (like "Tapahtuma XXX kuvat Anssi Kumpula" or similar, avoiding mixing Finnish and English like in "Tapahtuma XXX by Anssi Kumpula").Currently any time I share a Collection with a public link I need to go and change the settings via Lightroom CC Links > Private Links: View on Web (which never takes me to the Collection, actually, and instead to Lightroom Web All Photos view – makes the workflow even worse), selec

Bug report submitted by Rob Cole on behalf of Soulflare007, who was having problems with login/AdobeID...Lightroom 5's export isn't resizing exactly to specified long edge. For example, when I restrict long edge to 1920, the exported files are 1919. Same with 1024, I get 1023px files instead. If I export from Adobe Bridge, then the long edges are calculated correctly. This problem didn't happen with LR4. Files being exported were DNG and TIF.More info here: http://forums.adobe.com/message/54380...

It would be great to choose whether or not the Crop Tool (R) recalls the previous aspect ratio. This way, users can set whether or not the previously used aspect ratio is automatically called up after activating the crop tool (pressing R) or if the crop tool defaults to the original, or any other, aspect ratio. I realize a Crop Ratio is available in the Quick Develop panel, but that's a bit cumbersome as the general crops need to be made before working through each photo. Some users like to crop as a last step after the bulk of other adjustments have been made. The option of utilizing the following workflow would be great: Make various exposure adjustmentsPress RMouse over to Crop dialogueSelect 8x10 ratio (for instance)Adjust new 8x10 framingPress RMove to next photoMake various exposure adjustmentsPress R8x10 ratio is already activated (because that was the previously used aspect ratio)Adjust new 8x10 framingPress RMove to next photo..

Please add layflat paper offered by Blurb in LR module. Thanks

In the latest update, full image preview has been added when hovering presets. While this is fantastic and really useful most of the time, when handling large files like stitched panoramas, my computer crawls to a stop as my 7700K is maxed out for each preset. Could it be possible to disable that in the settings for such case ?Thanks

When looking at the long list of my Collections, in Lightroom CC and Lightroom Mobile we have visual indicators which Collections are Shared (there's a text Shared under the name of the Collection), but LR Classic CC does not.Would be great to have a some kind of visual remark which Synced Collections are also Shared. It's a kind of hard to read that all my 500+ Collections look the same, whether they are Shared publicly or not. At least Synced Collections you can detect from the arrow symbol first on the row, but there's no indicator for Share.The only way to see which Collections are Shared publicly is to first click one Collection at a time and look at the upper right corner whether a button reads Make Public or Make Private. That's not good enough, we need to be able to see the state on the list as well.Please add that to make Collection list in LR Classic CC easier to read.Thanks!LR CC (Mac)LR Mobile (iPhone SE)LR Classic CC (Mac) – *NO* indicator which are Shared p

When I create an HDR and use the preview feature to preview 'High deghosting', I have to wait for the system generating the preview - this is expected, fine. However, if I then flick to Medium to compare, I can't go back to High again without it redrawing from scratch again.Can Lightroom keep a cached preview for each so I can quickly flick between each to compare without having to wait on the system re-generating it each time?

I use the Linear Gradient Tool and the Radial Gradient Tool all the time in Lightroom but I have quite different default preset for each tool. Would it be possible for Adobe to implement the ability to have a different default preset for each tool?

Ligthroom should slightly change the brush cursor when Auto-Mask is enabled. This would save time having to redo brushing or remembering to check what state the brush was left in.Thanks