Skip to main content

Filter by idea status

10000+ Ideas

Hard CoderKnown Participant

P: Add collage/composite to LR COpen for Voting

There are already features that create new images in LR, so why not add collage, and perhaps compositing. There are a whole bunch of ways in which such a UI could work, but ... here's something fairly easy to visualize in the case of collage. User has a panel from which to select collage layouts. Let's say for now they're all rectangular.User selects a layout, along with color/gradient/photo to use as background, etc., then selects photos to drop into it.With photos in the layout, drag to swap them, click and hit delete to remove, etcResize with scroll wheel, also the usual "fit/fill" etcMove borders by grabbing the border and draggingWiden/narrow borders by grabbing border edge and draggingDraw new slots with right click-drag rectangle, or whateverOverlapping slots should be fineDelete slots in one of the obvious ways, right-click context menu, click-select delete key, whateverBorder changes have optional snapping to make it easy to keep things aligned Ideally the collage could be saved in a form that allows for future editing, updates when embedded photographs change, etc., but if not, hey, that's still 100x better than the current situation. Note that this is pretty similar to how print and book modules do or should work although they are creaky as h-ll and in desperate need of a good update. For composites, trickier, but the spiffy new masking tools would be awesome to have. Heck, just being able to create and export an alpha channel would be a start.

Simon Booker
Simon BookerParticipant

P: AI-Assisted Wildlife Burst Culling in LightroomOpen for Voting

As camera technology has advanced, wildlife photography has reached a tipping point.Modern cameras routinely shoot at 20, 30, 40 FPS and beyond. Capturing key moments requires bursts because photographers have only fractions of a second to capture motion behaviour a barn owl striking prey, a kingfisher entering water or an eagle flying close.The result is that a good morning in the field can easily generate 500–2,000 images, with hundreds of near-identical frames from burst sequences. Good fieldcraft and technique captures THE image. The challenge is finding it.The Last BottleneckI am an experienced wildlife photographer, speaker and Lightroom advocate. Every presentation I give and almost every wildlife photographer I meet asks the same question:"How do you deal with burst photos, and do you ever get tired of the editing process?"The answer is that editing is no longer the issue. Culling is.You guys have transformed image editing with an amazing suite of tools. However, wildlife photographers still spend countless hours manually reviewing burst sequences to identify the one frame with - Sharp eye focus | wing position | poseThis process is repetitive, time-consuming and largely mechanical. I work in IT and this is exactly the type of problem AI is built to solve.My Workflow In Lightroom TODAY Import images into Lightroom Cloud. First pass: remove obvious failures and assign ratings. 3★ = keeper 4★ = potential edit Tag species and behavioural information. Review burst sequences using Compare mode. Examine groups of 10–15 similar frames looking for: Sharp eyes Strong poses Clean composition Select finalists and mark them for editing. Perform detailed editing. Final keywording and publishing. Everything in this workflow works perfectly. The bottleneck is Step 4. On a productive day photographing, this step alone can consume hours.The Adobe OpportunityWildlife photographers may not be the largest photography segment, but they are very engaged Lightroom users.Some AI business model gymnastics assures me that the global market size for wedding is maybe 10:1 v Wildlife. However, with 41 million subscribers to Creative Cloud Photography Plan (at  $120 per year take 15% photographers and 1.5% Wildlife. Call it 500,000 and if just 5% of those are serious enough to subscribe that nets out to 25,000 x $120 = $3 Million.Enough for a developer or 2? 😎I invest in Lightroom because my workflows depends on:Big archives | Cloud sync | keywording | AI denoise | Smart AI masking | Mobile acces | Long-term storageAdmin v CreativeEditing is creative, but culling is “admin” and that makes a huge difference! Happy to spend time making a perfect final creation. But … what kills me is spending hours comparing 300 identical frames to find the one that is sharper than the rest (see below). Every hour saved is an hour back for shooting and most important of all … my wife :-)You know somethinsg wrong when you walk out the door and your partnder says - “Remember not to take too many pics and remember to select 10FPS every now and again”!A Perfect Storm for Adobe AIYou guys already have ALL the underlying tech: Subject detection Spatial analysis Eye detect Focus analysis The final piece of teh jigsaw is bringing it all together into a workflow to eliminate the repetitive work to find the strongest candidates. Indeed Lightroom is already awesome & this would make is THE goto for a growing genre that supports nature and educates people on teh planet.Sample below. 300 classic wilidlife images of a Harrier at distance. Cropped 1. Current Assisted Cull cannot see eyes in any of them so fails 100% 

.random..
.random..Inspiring

Customizable Save Format MenuOpen for Voting

Customizable Save As Menu Photoshop’s Save As workflow is currently based on a fixed, predefined list of file formats. An optional feature in Preferences could allow users to fully customize this menu to match their workflow while preserving the current behavior as the default.Proposed Features1. Custom Format VisibilityUsers could choose which formats appear in the Save As menu.Unused formats could either:be completely hidden, or remain visible but disabled/grayed out.This would significantly reduce menu clutter while still preserving discoverability.2. Custom Format OrderingUsers could drag and reorder formats according to their needs.For example:PSD TIFF PNG JPEG PDFinstead of scrolling through a long list of rarely used legacy formats.3. Keyboard SelectionUsers could assign number keys to formats.Example:1 = PSD2 = PNG3 = JPEG4 = TIFFWhen the Save As dialog opens, pressing a single number key would immediately select the desired format.4. Save PresetsUsers could assign one or more save presets to each format.Examples:1 = PSD (Layers ON)2 = PSD (Layers OFF)3 = PNG (Web)4 = TIFF (ZIP Compression)This would allow instant selection of common save configurations without creating Actions or navigating multiple dialogs. Why This MattersI understand that similar workflows can already be achieved through Export As, Quick Export, Actions, Scripts, or custom automation.However, that is not the point of this request.The goal is not automation. The goal is to make the most common daily operation—saving files—faster, cleaner, and more efficient directly inside the standard Save As workflow.Most users repeatedly save the same few formats every day. Allowing them to customize the Save As menu would reduce clicks, reduce visual clutter, and significantly improve workflow efficiency without changing the default experience for existing users.

brandon_4490Participant

P: (HDR) gain map single channel + scaling supportOpen for Voting

Exporting HDR images from Lightroom with HDR gain maps appears to embed a three channel gain map of equal size to the image. As someone who works with high resolution (60MP) images, the increase in file size from this is not manageable as it can nearly double the size of images that can themselves be 40MB+.   ISO 21496-1 accommodates for this by allowing the gain map to be smaller than the actual image by an integer scale factor, and allowing for a single channel version that is effectively a luminance map.    As an example, Apple uses a 1/4 size (scaled down by factor of 2 on each axis) single channel gain map for photos taken on iPhone. This minimizes the increase in file size. Putting aside image compression, you have 1/4 the number of pixels, and 1/3 the bits per pixel, so the parameters Apple uses may take up something like 1/12 the size of a 1:1 size three channel gain map.   In a use case like mine, a scale factor of 2 would still be a 15MP gain map which would have no perceivable loss of quality; you could potentially scale by a factor of 3 to 6.66MP and still get good results. In many cases when I view the gain map embedded in output from Lightroom it is so close to greyscale that there's clearly not much differentiation in the per-channel values, and in such cases a single channel gain map could be used for little loss of quality in exchange for significant size reduction.   It would be very useful if Lightroom added support for previewing and exporting with the option of a single channel gain map and the option of a scaled gain map.