• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Are you using the cloud-based Lightroom apps for iOS, Android, Windows, Mac, and Web? Then you'll love my book, Adobe Lightroom - Edit on the Go!

    You'll learn how to use the Lightroom cloud ecosystem to organize, edit and share your photos. You'll also come to understand the thought processes used by professional photographers when they're editing their own photos, so you can transform your photos quickly and easily. And better still, the eBooks are updated for every release, so it's always up to date.
  • Dark mode now has a single preference for the whole site! It's a simple toggle switch in the bottom right-hand corner of any page. As it uses a cookie to store your preference, you may need to dismiss the cookie banner before you can see it. Any problems, please let us know!

Stacks, why bother?

Status
Not open for further replies.

tspear

Senior Member
Premium Cloud Member
Joined
Sep 23, 2014
Messages
2,247
Location
Waltham MA
Lightroom Experience
Beginner
Lightroom Version
Cloud Service
Lightroom Version Number
5.0
Operating System
  1. Windows 10
Question, after using Lr for a while and seeing the stacks auto created for merged images, I have come to the question. Why bother?
Basically, stacks are only useful in the unfiltered views for all photos or a specific album. So they only help when scrolling through images, not very useful when managing 20K images.

As a result I created this issue over on Adobe: https://community.adobe.com/t5/ligh...deas/p-search-filter-on-stacks/idi-p/12558985
However, now I wonder. Was I hasty? Am I missing something?

Tim
 
I agree that the current stack implementation is often (maybe mostly) more trouble than it is worth. I pretty much stopped doing it after screwing up changes (metadata especially) due to how they are applied differently whether selected stack collapsed or expanded. I now use them only temporarily, e.g. as a way to group players in team action shots so I can review how many of each, then I unstack before doing anything else.

I am not sure if your recommendations are adequate to make them fully useful, but I absolutely agree that stacks, as implemented, are badly done and more dangerous than useful.

The one area I might still use (and know I have some of) are things like HDR groups. Not that it works well there (again, metadata changes being a good example), but it seems the only good way to maintain that grouping especially if intermixed (over time say) with individual shots of the same subject.
 
I too have found little benefit from stacks. And often people come here complaining about missing photos only to discover with a little prompting that their missing photos are buried in a stack.

Stacks could be useful for focus stacks, Panoramas and HDR. I would like to see an option to auto-expand stacks with a mouse over. The present method for identifying stacks is not noticeable enough to recognizes the photo that you might be looking for is in a stack hidden behind the the cover photo.


Sent from my iPad using Tapatalk
 
If there were global stacks for HDR/pano elements, those would be useful for keeping all the "bits" together. But the current implementation... yeah, not ideal.
 
Stacks could be useful for focus stacks, Panoramas and HDR. I would like to see an option to auto-expand stacks with a mouse over. The present method for identifying stacks is not noticeable enough to recognizes the photo that you might be looking for is in a stack hidden behind the the cover photo.
My main complaints lie not in the UI, but in what happens when you are not specifically looking at a stack. A search to find something, control-A, a change in metadata, a mass delete, a move to a collection... almost all of these end up doing the wrong thing (I admit that doing the opposite thing could also be construed as wrong, but I think what it does now is more wrong [and if this phrase makes you think of a suspension bridge you watched the Big Bang theory too often]).
 
BBT rocks. :)

So it is not just me. Now, how do we get Adobe's attention to fix it!
 
BBT rocks. :)

So it is not just me. Now, how do we get Adobe's attention to fix it!
You stand a better chance of having Sheldon take up mud wrestling in a new BBT season. :oops:

I think stacks are baked into the paradigm, they would be very scared of changing it and breaking people's workflow (not to mention they are always reluctant to change anything that is not their own idea - they have 10 year old bugs they show no interest in addressing).
 
For Lr, not Classic. No one has baked workflows. I asked for months, even from our own @Victoria Bampton to have a solid workflow to use with Lr. I pestered multiple people at Adobe and on multiple forums. No one had one. I had to invent one, and at this point I consider it only parboiled and would gladly change things to fix the fricking stacks.
 
Ah... my apologies, I did not realize I was in Cloudy. I'm not even sure my comments applied (though I guess they rang true).

Hey... Cloudy is for you kids with cell phones. They don't need no stinking workflow, it has the word "work" in it. :laugh:
 
Ah... my apologies, I did not realize I was in Cloudy. I'm not even sure my comments applied (though I guess they rang true).

Hey... Cloudy is for you kids with cell phones. They don't need no stinking workflow, it has the word "work" in it. :laugh:
lol, well i am still working and will not likely see anything I put in for the past 33 years or the next 15. Since my elders will have spent us into oblivion. So who would want to work with that incentive? :D

Tim
 
For Lr, not Classic. No one has baked workflows. I asked for months, even from our own @Victoria Bampton to have a solid workflow to use with Lr. I pestered multiple people at Adobe and on multiple forums. No one had one.

I think that's simply because there is no one-size-fits-all solution. Everyone's needs are different. What everyone wants to accomplish is different. And with the number of devices involved with the cloud, that has even more permutations than workflow ever did with Classic. That's why we aim to teach principles and methods rather than a fixed workflow.
 
@Victoria Bampton

I disagree. Image management is obviously an after thought in Lr. Even as much as I like your Edit Like A Pro book, you also only walk users through a very simplistic sequence, take photo, put in some meta-data, edit image, and post it somewhere.

The number of device types supported by Lr not only increase traditional UX issues, it also very likely broadens the reach of the application to a larger user base. The result is greater complexity, but this is just an excuse. Of the items I list below, only stacks (the subject of this thread) is actually is actually difficult from a UX perspective.

The reality is there are only a few functions in Classic that do not exist in Lr which are used for image management.
1. Color Labels
2. Smart Collections
3. Better stack/group management

Pretty much everything else is just noise.
 
I think that's simply because there is no one-size-fits-all solution. Everyone's needs are different. What everyone wants to accomplish is different. .....
If you have ever tried to teach a LR Classic course to a group of photographers, then this hits the nail on the head. I can just work on instructing on the library module, and your sentences are a perfect description of my experiences. And it is almost at its worst when an experienced photographer decides to transition to LR Classic, and he brings all his previous ways of doing things with him.
BTW, I primarily use stacks for my hdrs, panos, and focus stacks. They are useful to me, even with a shortcoming or two, and I want them to stay.
 
If there were global stacks for HDR/pano elements, those would be useful for keeping all the "bits" together. But the current implementation... yeah, not ideal.
I've been frustrated more than once (second time, shame on me ...) because a stack implemented in one collection does not carry over to any other collections or to the actual physical files on disk. Regular, "dumb" drag and drop collections, not smart collections.

I find stacks useful when photographing a baseball game, because there are plays and then pauses between plays. I might shoot the play at 9 fps in order not to miss a key moment, but I want to review all the photos of that play as a group.

It would also be nice if stacks could be named.
 
Even as much as I like your Edit Like A Pro book, you also only walk users through a very simplistic sequence, take photo, put in some meta-data, edit image, and post it somewhere.
I'll be honest, I'm still not quite clear on what other bits of workflow are you looking to include in this "ideal workflow", in addition to taking photos, adding metadata, editing and sharing?
Image management is obviously an after thought in Lr.
That is, of course, a different issue entirely. It's not so much as an after thought as much as simply different priorities. Not having to manage photos is one of their main sales points for the ecosystem.
 
That is, of course, a different issue entirely. It's not so much as an after thought as much as simply different priorities. Not having to manage photos is one of their main sales points for the ecosystem.
As you may know, there are other forums out there where a number of photographers vent their severe displeasure for Adobe and Lightroom Classic because they are "forced" to use a catalog. LR cloudy, in some way, is a response to that market segment.
 
As you may know, there are other forums out there where a number of photographers vent their severe displeasure for Adobe and Lightroom Classic because they are "forced" to use a catalog. LR cloudy, in some way, is a response to that market segment.
Are there any DAMs (as oppose to glorified file managers) that do not use a catalogue? C1 does have Sessions as well but still offers a catalogue.
 
IMO- File managers (file browsers) are not DAMs. (The computer operating system is the 'manager')
And DAM apps cannot operate without a Database (catalog) of some kind (that I can know!).
 
IMO- File managers (file browsers) are not DAMs. (The computer operating system is the 'manager')
And DAM apps cannot operate without a Database (catalog) of some kind (that I can know!).
That is exactly man point! I said DAMs "as oppose to"
 
IMO- File managers (file browsers) are not DAMs. (The computer operating system is the 'manager')
And DAM apps cannot operate without a Database (catalog) of some kind (that I can know!).
Before I started using Lightroom, I used Bibble as a non destructive Image editor. IIRC it has some collection capabilities but used the filesystem for main organization the Bible work including collection membership was kept in sidecar files. Corel bought Bubble in 2009 and turned it into AfterShot.
 
Are there any DAMs ...... that do not use a catalogue? C1 does have Sessions as well but still offers a catalogue.
A catalog is a DAM . It is a Digital Asset Manager. It does not necessarily have the ability to process the files that it manages.
I am guessing that you meant - are there any photo processing applications that do not require a catalog or DAM in order to open and find a photo which it will then post process. There are lots of them. In the Adobe world, Photoshop Elements and Photoshop can directly open a file without having it pass through a catalog. Photoshop Elements has a catalog as part of its over system. C1 needs to have a file incorporated into a session (at a minimum) in order to open it. Other software like ACDSee can, as I recall, also open a file directly for post processing. It also has DAM capabilities using a file manager as its basic engine.
 
A catalog is a DAM . It is a Digital Asset Manager. It does not necessarily have the ability to process the files that it manages.
I am guessing that you meant - are there any photo processing applications that do not require a catalog or DAM in order to open and find a photo which it will then post process. There are lots of them. In the Adobe world, Photoshop Elements and Photoshop can directly open a file without having it pass through a catalog. Photoshop Elements has a catalog as part of its over system. C1 needs to have a file incorporated into a session (at a minimum) in order to open it. Other software like ACDSee can, as I recall, also open a file directly for post processing. It also has DAM capabilities using a file manager as its basic engine.
No I am saying a DAM needs a catalogue. I am saying that if you want the searching capability of the likes of PhotoMechanic, Lr, C1 et al then there will be a catalogue. Even ON1 needs a catalogue if you are going to use the more advanced feature of the Library, the same applies to DxO PhotoLab. The likes of Luminar of course do not have a dam they just have an image browser attached. Now, whether there is any sense in the likes of Lr giving the user the option to turn off the catalogue and related functionality is probably a question not worth asking as it will never happen.
 
I'll be honest, I'm still not quite clear on what other bits of workflow are you looking to include in this "ideal workflow", in addition to taking photos, adding metadata, editing and sharing?

That is, of course, a different issue entirely. It's not so much as an after thought as much as simply different priorities. Not having to manage photos is one of their main sales points for the ecosystem.
Go on a trip where you cannot readily connect to the net. Take a thousand or more images; and load them in Lr.
Go to the next location, and start taking photos.
How do you manage the photos? How do you know which you have added, which you have posted online....
The take pic, meta-data, edit, post, file flow works in a cell phone with just a few images, or for someone super aggressive about editing and posting on the fly with a connection always or every night when you get back to the hotel.
But for most of us, I doubt many of us actually manage to get through all the images we take every single day.

It's the same basis for John Beardswoth smart workflow.
 
Go on a trip where you cannot readily connect to the net. Take a thousand or more images; ......
Go to the next location, and start taking photos.
How do you manage the photos? ....
Adobe has provided me the solution to this - I bring a laptop with me, and use Lightroom Classic.
 
Adobe has provided me the solution to this - I bring a laptop with me, and use Lightroom Classic.
lmao. Well played.
I have designed a flow that works in the cloud version. I had to effectively go old school and base it around folders (oops, I mean albums). I have used it for a few months now (ok, I did it in parallel with Classic for a few months first), and it works well. Makes swapping between devices very easy, I even occasionally manage to work on images on my phone while traveling and waiting in lines. I recently had started to make some minor tweaks to it, my original version was really geared more to working the images post trip. now I eliminated a couple steps, and I think I will eliminate a few more over the next year as I get better about working images on the fly no matter where I am.
 
Status
Not open for further replies.
Back
Top