C1 21 - No History Tool
C1 needs a History Tool.
(We all agree on this, right?)
-
I agree, although I think this would be better requested through the Features Request section.
1 -
Good point! I'll make a new post...
0 -
I disagree.
I never got on with history tools in products I used that offered them.
Step back a few changes is useful but trees to navigate always seemed pointless.
Given an application that offered both a full history (until one started to ask a lot of branching or tried to work out which point 300 changes previously was where you wanted to be) and one that made it easy to create "snapshot" edit (something which C1 offers much more effectively through variants) I found the snap shot approach far more useful. And far more usable.
I have no problem with offering both approaches for those who simply must have a history in their process flows but make it optional and don't try to make me pay for the benefits of others using it. (If you see what I mean ...)
1 -
I suppose it depends on workflow SFA. I liken edition a photo to traveling a path, sometimes the edits made take me down a path I don't want to go, I find it good to be able to backtrack to a point and take a different route. Sometimes I find it difficult to unpick what I have done to get to where I am along the path and I am forever clicking CTRL+Z to go back to a point where I want to take that different path, I think it would be useful to be able to see where I am backtracking to, and having a history tool would allow me to do this.
Some people use and like history panels, others don't, it's a matter or taste and workflow I suppose.
I get the use of varients and I do use them, but this all supposes that the snapshots are created at the right points. Sometimes I use layers to partition different sets of edits...i suppose there are many ways to skin a cat (if you excuse the expression).
1 -
Hi SFA, I think we're essentially in agreement here - the point is is that a History Tool would be (it seems) a very simple addition, very useful for (I speculate) many of us - and no bother at all to anyone who didn't want to use it.
That first point is, as you indeed suggest, crucial, and I appreciate that dev time is a limited resource. However it just doesn't seem like something that would take an awful amount of engineering - all the undo states are already preserved anyway, it's just a matter of exposing them to the user.
Then again, what do I know? Very little. Just that in my preferred workflow, History functionality works much better than - and indeed differently to - variants :)
0 -
Personally, I find it shocking that at this stage of image editing software evolution, a supposedly "premium" editor like C1 lacks a history tool. Lightroom and ON1 have them. So should Capture One.
1
Post is closed for comments.
Comments
6 comments