Stuck stacks

Status
Not open for further replies.
L

leuallen

Member
Joined
Feb 26, 2009
Messages
28
I have some panorama images in a folder in which the panorama and its component images are stacked - panorama on top. On some of the stacks I am unable to expand a collapsed stack either by clicking on the image or by menu. Other stacks in the same folder act normally - can expand and collapse. On the problem stacks I checked and the component images show in Explorer.

No ?'s for the folder the image are in and so far limited to only this folder.

If I unstack a stuck stack, the component images do not show up in LR. Only the panorama which was on top.

I have optimized the catalog. No difference.

The panoramas are large - one over 2 GB.

Larry
 
Sort by date Sort by votes
Problem solved! I changed the sort order from Capture Time to Filename. Now all files are visible. Changing back to Capture Time does not bring back the problem. Probably some bug that changing the sort order squashes.

Larry
 
Upvote 0 Downvote
Well done Larry!
 
Upvote 0 Downvote
I have the same problem Larry reported, but his solution doesn't work for me.

I have now two folders that have multiple stacks from panoramas in it. The top photo is the panorama and the others are the components. In both folders there is a problem with the first stack, coincidence?

The problem is that it isn't a stack anymore, I cannot expand it. The panorama is still visible, but the components aren't visible in LR. They are there, and LR is even reporting the correct number of files in the folder. But you cannot see them. I can only see them in Finder.

I've tried Synchronizing the folder, changed the sort-order like Larry suggested, I've also made sure that there is no filtering on the folder. Optimizing the catalog didn't help either.

Maybe it has something to do with collections, because both panoramas are part of a collection. I've tried to add the first member of a stack to a collection to see if that causes the same problem, but that didn't trigger the stuck stack.

Any other suggestions for this problem?
Thanks, Jeroen
 
Upvote 0 Downvote
Can you post a screenshot Jeroen so we can see what you're looking at?
 
Upvote 0 Downvote
Here is a screenshot.
[img width=6'' height=65]http://akershoek.com/temp/LR2.6_filmstrip.png[/img]

There you can see that filtering is disabled. You can see that there are 31 photos in the folder, but only 27 show up in LR. The first photo is also a stack, but you can see that LR doesn't think so because it doesn't have the number on it like the others. The 4 files that are missing are part of this stack...
 
Upvote 0 Downvote
Yeah, that is a weird problem. Odd thoughts as I looked at the screenshot:

1. If you enlarge the filmstrip, does the stacking label reappear? Some things disappear when the thumbnails get too small.
2. What's the name of the folder? It looks like it may have a non-standard character in it?
3. What if you go to the Expand All Stacks command in the menu - does it reappear?
 
Upvote 0 Downvote
Thanks for you help. It is certainly weird...

To answer your questions:
1. Enlarging the filmstrip doesn't help, in grid view the stacking label isn't visible either.
2. The foldername is ''3 | Panorama Schiedam'. On windows you cannot use | in a file or directoryname. On the Mac this is not a problem. All my folders are named like this, I've been using LR since the beginning. It has never caused a problem.
3. Expand All only expands the other stacks :(
 
Upvote 0 Downvote
I'm pretty sure this is the same problem I saw when using stacks a few months ago. I had to select all the images in the folder (grid mode) and select un-stack. Then I auto stacked by time (mine were bracketed for HDR so this was easy as they were in small time groups) and it fixed the issue.

Although the | character is not illegal in a filename on a Mac it is not a good choice to use it. The | character is a 'pipe' redirection command in a unix shell (Mac is unix underneath) and this can cause some problems in applications if they don't enclose filenames with " ". It is always good practice to steer clear of these sorts of characters if possible as they can lead to issues when move data to other operating systems.
 
Upvote 0 Downvote
Jeroen, report it to Adobe too. The link's on the toolbar above. That's a weird bug, and I'm glad you've got it sorted.
 
Upvote 0 Downvote
Do you have a copy of the catalog (i.e. a backup) of before you fixed it? You could suggest sending it to them.
 
Upvote 0 Downvote
Status
Not open for further replies.
Back
Top