I created a number of stacks, quit Bridge (CS6), opened it again and all the stacks were there. I used Bridge a little more and then it crashed. Upon reloading, some of my stacks were gone. Some were still there, some were missing images, some showed a stack and indicated only one image was in the stack.
Where is the information about stacks stored? Is this a safe way to permanently retain grouping of images within a single folder? Is there a better way? What the heck happened to my stacks?
What version of Bridge?
CS 6 was the most stable when it came to holding stacks but before it could lose them out of the blue. Never did get to know why, usually when switching to fast between window or something other to fast. I came to live with it and when it happened I started at the bottom o f the screen working my way up to restack them because normal they where left in the same order as before but only ungrouped from stacks.
To my knowledge there is no (at least no easy way to find) location where this info is stored in a visible way or to redo them, just bite the bullet and say a few nasty words to let the steam flow… :-)
I have to say that in the CS6 I have not had it very often so there seems to be a small improvement.
Like I mentioned in the post, I'm using CS6. I was hoping there would be a permanent way of grouping things in stacks, stack and pray doesn't really appeal to me as a professional way of managing assets, given that Adobe markets itself as software for professional use. Other than folders, is there another method (or tagging / grouping app) that you guys use?
Could be a difference in how the stacks are recorded on OSX vs Win7, but I'd be surprised if it was. It didn't seem to be in the cache sqlite database file Bridge makes, nor does grouping photos update their timestamps. I think the stack info must be in some sidecar somewhere.
I think the stack info must be in some sidecar somewhere.
If that would be the case then try to check the option to show hidden files in the menu view and check if making a stack adds info to one of those files by selecting the sort order on modification date.
And if it comes down to professional asset management I fully agree with you that Stack and Pray is not the goal we should wish. But I also often state that Bridge is not a real DAM and for good asset management on a long term base you should use a dedicated DAM application.
Bridge has changed its cache format for almost every new cycle, some people never have trouble with Stacks, like Curt, and some on a regular base.
Deleting prefs and every now and the dump the complete cache seems to help a bit but there are still a lot of mysterious things happening under the hood of Bridge.
Personally I have Canto Cumulus single user for storing files in my archive, lightning fast search and highly customizable. But the things Bridge is good at (all that needs to be done before the files are finally processed) Cumulus is not so good, or even very bad.