4 Messages
•
394 Points
Lightroom: When selecting a collapsed stack, provide option to apply changes to all photos in the stack
In Lightroom 5.4, if I select a collapsed stack of photos in the Library module, I would like the option to automatically apply changes (e.g. metadata) to all photos within that stack.
Background: as a first-time Lightroom user, I used the auto-stacking feature so that my 3-shot bracketed (i.e. HDR) photos would be stacked together. With the stacks collapsed, I went through my library, selected multiple stacks, and typed in a GPS location to be applied to those photos. I assumed that by selecting the (collapsed) stacks, the metadata would be applied to all photos within those stacks. However, the GPS locations were only applied to the first photo within each stack.
After the fact, I learned that stacks must be expanded in order to select all photos within the stack. From my perspective, this defeats the purpose of creating stacks - if one must expand the stack to apply changes to all photos within the stack, there doesn't seem to be much point of creating stacks in the first place.
Background: as a first-time Lightroom user, I used the auto-stacking feature so that my 3-shot bracketed (i.e. HDR) photos would be stacked together. With the stacks collapsed, I went through my library, selected multiple stacks, and typed in a GPS location to be applied to those photos. I assumed that by selecting the (collapsed) stacks, the metadata would be applied to all photos within those stacks. However, the GPS locations were only applied to the first photo within each stack.
After the fact, I learned that stacks must be expanded in order to select all photos within the stack. From my perspective, this defeats the purpose of creating stacks - if one must expand the stack to apply changes to all photos within the stack, there doesn't seem to be much point of creating stacks in the first place.
Responses
John_R_Ellis
Champion
•
5.6K Messages
•
98.3K Points
7 years ago
http://www.photographers-toolbox.com/...
0
0
rob_cole_2221866
4.5K Messages
•
76.3K Points
7 years ago
|>" It's been made a number of times before for several years, so I think it is unlikely that Adobe will act on it."
I thought you were going to say "..., so it must be getting near the top of the list by now" ;-}.
PS - RelativeAntics is another plugin which supports transferring develop settings and/or metadata to other stack members.
0
0
keith_cavey
4 Messages
•
394 Points
7 years ago
0
0
david_kol_chter
2 Messages
•
110 Points
5 years ago
When I select a collapsed stack of photos and enter some keywords, these kewords are only applied to the top (visible) picture. Seems as if only the top picture is selected, not the whole stack underneath.
The same behaviour can be observed when selecting the collapsed stack and convert to dng. Only the top picture gets converted.
Is this intended behaviour?
I think it's a bit awkward to first expand the stack, do something and then collapse it again...
0
john_barrett_3898748
4 Messages
•
134 Points
5 years ago
reject photos, stack them, collapse the stack & delete rejected photos. Rejected photos in the stack aren't removed.
0
0
dan_1844859
62 Messages
•
1.8K Points
5 years ago
When images are stacked, and the stack is collapsed; Provide a way to apply metadata changes to the enitire stack without having to expand the stack. Let's say I want to add a keyword to 3 stacked images. As it is now I need to expand the stack, then highlight all images in the stack (click on first, then shift-click on the last), then make the keyword change I want (say click the check box on a Keyword in the Keyword list) which will apply the change to the selected images. Now, I need to re-collapse the stack.
What I'd like to do is highlight image(s), some of which may be top of collapsed stacks, then in some way tell LR if I want my next change to apply to just the selected images or to the selected images and all images under them in collapsed stacks. Perhaps a toggle somewhere that affects this behaviour.
1
0
martijn_saly_5922019
223 Messages
•
3.5K Points
5 years ago
I always find myself going through my folders after culling&rating, finding stacks and re-applying flags/keywords/ratings/labels to pictures inside the stack, copying them from the topmost picture. It's cumbersome, time consuming, and from what I know an easy problem to solve without adding (much) overhead to either the program or other users.
2
josh_brennecke
6 Messages
•
250 Points
5 years ago
Please add a preference to treat changes to a stacked top image to cascade to the rest of the stack's images. I stack dozens of bracketed shots when scrubbing and cannot stand having to expand the set to apply keywords, delete the stack, etc. I realize people use stacks in various ways, but I use them mostly for bracketed shots and pano sets when every shot within the stack is essentially considered 1 'shot' for my purposes. I want to be able to treat a stack as a group--even when the stack remains collapsed--when working with it. For example, delete the entire stack (bracketed or pano shots), apply the same keyword(s) to every image in a stack, or move the entire stack (to a diff file location) when the action is performed on the top-most image in the stack. This would GREATLY improve workflow efficiency when people use stacks for sets intended to be output to a single image (HDR, pano, etc). Perhaps a preference of how to handle stacked images (i.e. Stacks: Cascade all non-develop changes and operations to all images in the stack--deleting, moving, keywording, rating, etc). But having hundreds of stacks and then having to expand them individually to do basic operations just considerably limits the usefulness of stacks. And as someone who may have 100's of single images as well as 100 bracketed sets of 5-7 images each tends to make me want to pull my hair out during basic workflow operations.
1
geoff_vane_7622168
13 Messages
•
226 Points
5 years ago
I got enormous amounts of images in my daily folders. The amount clutters the view so I'd like to be able to stack before I apply keywords. But then only the top image is tagged.
0
0
John_R_Ellis
Champion
•
5.6K Messages
•
98.3K Points
5 years ago
- Before making the change (e.g. applying a keyword), shift-click the stack-count badge in the upper-left corner of the thumbnail. That will expand the stack and select all the photos in it.
- Use the Syncomatic plugin.
2
geoff_vane_7622168
13 Messages
•
226 Points
5 years ago
0
0
roy_reed
3 Messages
•
102 Points
4 years ago
I would like to suggest the option for stacked images in Lightroom to have the option for adjustments to apply to all images in the stack instead of just the top one as now. The default could stay as it is currently, but a tick box could be applied to change this to 'all images in the stack'.
0
0
olivierhericord
2 Messages
•
102 Points
3 years ago
hi, i use stacks extensively to group RAW and jpegs from that raw file ... sometimes i just want to reject the whole stack and it's not possible. it's really cumbersome to do it with every iteration of an image i know i want to reject/
1
0
steve_gandy
238 Messages
•
4.7K Points
3 years ago
How about Alt/Option X, U, P for flags?
--Steve Gandy - stevegandy.com/photography
6
0
armin_staudt
73 Messages
•
2.1K Points
3 years ago
I'm working al lot with stacks. i.e after shot al lot of bracketing photos I choose "Auto Stack by capture time", collapse the stacks and have a first look on the shooting and set flags like "set as rejected" etc.
But every flag or tag is just valid for the first pic not for the pics in the stack.
It would be very helpful to have a button for "Sync Stack"-Mode, similar to the Sync-Button in Library-Mode, so that every tag, flag etc. means all the pics in a stack.
Also it would be cool, if you are in the "Auto-Stack by capture time" dialogue, you could scroll down the grid to look if the stacks are correct. Now you only can see the first screen...
PS: I know the trick to shift-click on a stack to open it and mark all the pics in it. If you work with a lot of pics it would be much better to do this with short-cuts and not thousand times with mouse-clicks...
0