This content has been marked as final.
Show 7 replies
-
1. Re: Stacking
micke-fi Dec 13, 2008 1:53 AM (in response to hrh gracie)I support this, especially point 2 and 3.
But I can easily think of situations where you want to have different keywords for files in a stack, so synchronizing them should not be the only option.
Mike -
2. Re: Stacking
(Daniel_Murdoch) Jan 2, 2009 8:31 AM (in response to hrh gracie)I can't express enough what a pain it is to NOT have these features (#1-3). These are at the top of my request list. I don't see what it couldn't be an option when working with stacks so the user can make the choice. -
3. Re: Stacking
Lee Jay-7OQGJF Jan 2, 2009 3:32 PM (in response to hrh gracie)Stacking across folders sounds problematic to me. If you have a stack that contains images from several folders, does that stack reside in all the folders represented by the images or just the one in which it was created? What if you drag-and-drop the stack to a new folder? Do all the images move from whatever folders they are in to the new folder, or just the ones from the folder from which you dragged? I think you get the idea - there could be several race-like or confusing conditions associated with this. Stacking in collections doesn't have these problems. -
4. Re: Stacking
dcrebelxt Jan 2, 2009 8:46 PM (in response to hrh gracie)If you try to move a stack that crosses folders, LR could always be programmed to be intelligent enough to ASK what to do, rather than always assume it knows best - and hose things in the process... no confusion that way.
[Hey you could even have an OPTION to always do it one way or the other... or always prompt for best course of action. There's a whole WORLD of possibilities with the inclusion of options. We don't need to lock ourselves into a rigid ONLY MY WAY IS RIGHT at the exclusion of all other methods point of view.] -
5. Re: Stacking
john beardsworth Jan 3, 2009 1:36 AM (in response to hrh gracie)I think Lee Jay makes a good point regarding potential problems if Adobe were simply to extend the current folder-limited stacking and go "cross-folder".
However, what I think is needed is not "cross-folder" stacking but stacking indexed at the catalogue level, not by folders. However you may have got a group of images into the grid, you should be able to select them and stack them. The key would be the unique ID of the images, not the combination of folder name and filename as now. It is not hard.
I agree about 3 too. There should be a preference which allows the user to choose the current half-baked behaviour, or to treat stacks as all selected for all purposes (export, metadata application, even adjustments)
I can see the point of 4, but "cross folder" functionality is going to be harder to implement in a browser context. And aren't a lot of folk using LR so they can avoid Bridge (much improved though it is in CS4)? The one Bridge feature the LR team must nick is the layered appearance of stacks - much less subtle but obvious, unlike in LR.
John -
6. Re: Stacking
micke-fi Jan 7, 2009 12:26 AM (in response to hrh gracie)Workaround for #1:
Stop caring about where LR puts the files. I used to fight LR and try to affect how files are stored, until I realized that it is a waste of time. Keywords, collections etc. are enough to find what you are looking for. Edit In... lets you edit in PS without caring about the file location. And when you need your shots outside LR, then you export.
OK OK, may not work for all. But it works for me.
Mike -
7. Re: Stacking
Bigchipmunk Jan 9, 2009 3:21 PM (in response to hrh gracie)I would also vote for #3 and would like to have it not just for keywords but also for all IPTC fields: location, title, .... with the following options:
global options:
* keep everything automatically in sync
* let me define the data individually
have an option (right click) on a stack to syncronize the data based on the
* selected image
* first image of the stack
An open question would be what should happen in the moment the stack is created, should the date by syncronized automatically? In case of a mistake (stack of wrong images), data could be lost.
Denny.



