Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: Nigelfrommanchester on March 04, 2007, 04:33:05 pm
-
Hi,
I've been playing with LR since receiving my 'free' RSP version. In general I'm happy with the apparent intent of the designers as much is intuitive but I'm still struggling with a few things. Sorting and stacking are my present problems.
In my Bridge workflow I had separate directories for raw files, converted raw files, prints and web. I'd assumed that all these files would come together when sorting against capture time but they still appear in clumps. Any ideas?
I thought stacking on capture time would sort this out as surely a stacking interval of 0 should find all the versionsof each individual shots? In practice my PC hangs for an eternity as soon as I try to do this and eventually announces that I have 0 stacks and 9714 unstacked.
I am a little frustrated
Nigel
-
I have half-solved my own problem. Apparently LR cannot stack images stored in different folders.
-
I have half-solved my own problem. Apparently LR cannot stack images stored in different folders.
[a href=\"index.php?act=findpost&pid=104853\"][{POST_SNAPBACK}][/a]
Hi
I was doing a search for stacking as i have a couple of qu's i am unsure about.
Re: Your above comment, does this mean that i can not stack in keywords?
I like to work in all data options given, and i find i use keywords a lot. However, all of the images i have stacked in the Folders part of the library don't appear stacked when i am in keywords or metadata. This is kind of frustrating especially when i want to filter my workflow according to the filters only to find 100 images i have to scroll thru that should only appear as 25 or so when stacked.
Also, when i create a virtual copy the images are not auto stacking. Is there a box i should have ticked to make this happen.
Thanks
Brad
-
I use stacking by capture time to stack my existing raw / PSD pairs. Fortunately I never take images within 1 second of each other, which I think is the minimum resolution of the function. If I recall I tried using 0 and couldn't make it work. This could be a problem for rapid shooters, but I shoot mostly rocks and trees which are slow movers ...