GrahamWelland
Subscriber & Workshop Member
Jack,Agreed, as it sits the LCC storage protocol is borderline stupid. there is no good reason it should not be inside the sessions. Then we should have an option to store a GENERIC LCC library in the existing fashion.
It is absurd to open up the LCC you want to apply and have a list of several hundred to sort through. My current workaround is I leave the image name as the LCC name, and in this way, my most recent LCC is always at the bottom of the list.
I agree that a two tier approach to LCCs would work well. I have to do the same as you and gave up on labeling my LCCs in favor of just using the file name instead. With the file name approach I know that the LCC will be close to my original image vs sorted in the list. However, it would be useful to have a global set of LCCs available.
Let us store LCCs with the session only and then have the open of storing a global set for all sessions as well.
I don't shoot an LCC for every shot but I do shoot one for each setup (I.e. each rise/fall setting or stitch pairs). You very quickly end up with an LCC list with hundreds of images in it which becomes unmanageable and a poor user interface for such a fundamental step in technical camera workflow.
I need to create the feature request for this as well, along with an FR for the ability to have each digital back use a different filename prefix. (If you upgrade your PhaseOne back or have more than one then you run into filename overlaps and there's no clean way to fix it other than rename on import).