mattiaswinbladh wrote:No IT or data analysis, electrician by trade.
I work mainly with sessions now. When I started using C1 I came from Lightroom so i initially used catalogs since that was sort of familiar, but I've come to appreciate sessions more. It's not as unwieldy as catalogs I find.
Interesting.
A useful and important trade.
I agree with you about sessions vs catalogs. However it is a personal choice entirely dependent on needs.
I'm not sure about catalogues bit in session there are the .cos files that contain the edit information and from which it should be possible to identify which tools have been used to edit the image. Of course some will always be used and so the challenge might then be to know whether the use of the tool was "standard default settings" or changed to something non-"standard".
If default one could ignore it (probably). If not standard one might assume it was an elective use.
That is quite a simple idea BUT made more complicated where the default process mapping is dependent on pre-defined defaults - like levels of sharpening for the lens/sensor combination, lens correction activity (if any and also potentially different for different settings, sharpening applied (different for different cameras and sensors) .... and a number of other preset values used to create a starting point image for us just as the camera's internal processing does for the production of a jpg file to provide a preview for the RAW file.
I think some form of analysis that might allow a heat map or tree map or something else with graphical content to be made available would be possible but I'm not sure it would really be very informative. Combined with a complete changes history it might add something but even then I'm not really sure it would be insightful - beyond what one can already work out based on the "normal" preferences one has for how one chooses to apply edits.
So something might be possible but I'm doubtful the effort could be justified.
That said, across a wide spectrum of users the information might be more valuable and I wonder if usage metrics (by program and routine for example) already provide very similar insight across the product for the C1 developers.
Just guessing.
Grant