[toni-a]

I'll later share the new tentative processing workflow I'm defining (the idea is a transition period in which I'll use both LR and C1, the former for the library things that miss C1, the latter for editing).


At the moment I'm reprocessing the last session (one day, the past week, in Bellinzona) to get into acquaintance with C1 and I'm pretty pretty pleased. The learning curve is easier than I expected.


What I fear is some apparently minor missing feature that then turns into a showstopper... For instance, the last thing I did yesterday was "recipes", that is the way to export stuff. Very similar to LR, but more effective for a couple of reasons. But... it seems C1 misses a simple checkbox to override the output file if it already exists... it always chooses to create a new copy. Fortunately in this case, if no other solution is found, I can solve with a custom made batch script that post-processes the output directory.


Next thing will be the creation and use of custom, ColorChecker Passport based camera profiles. While X-Rite has got a specific plugin for Lightroom, and it's able to create "dual illuminant" profiles that are good for various moments of the day, I see that C1 can't. With some work you can just create a single illuminant profile... Let's see what happens...


PS I knew it, but effectively the improved quality of the post-processed files in C1, in comparison to LR, is relevant, especially for things like sharpening - indeed it seems it's the RAW engine that does a better job since the beginning.

And here's another customer lost by Adobe with so many doing the same hope they change their attitude or the market will be dominated by others