Skip to main content

History Panel

Not currently planned

Comments

42 comments

  • Official comment
    Mathieu B
    Product Manager

    Hi everyone, 
    Thank you for the suggestion - this is not something we are currently working on.

    This does not mean this is a bad suggestion or that it will never be adressed, but in an effort of transparency we want you to know that we are not currently allocating resources to solving this issue.

    We will revisit the status of this thread if and when it changes.

  • Denis Huk
    Admin

    Your post has been hidden for moderation. Please read the pinned post and use the template provided.

    You can edit your post by clicking the "gear" icon on your post and then selecting "edit".

    I understand that rules and guidelines are annoying, but it has to be this way in order to make the requests and feedback usable by our Product Management team, and to ensure that you get the response you deserve.

    Thank you for your time and for directly contributing towards the development of Capture One. We greatly appreciate it.

    0
  • Dickon Whitehead

    yes I agree with this post! also see my post that I am about to make re locked versions covering similar but not identical requirements

    7
  • Tony Newlin

    Completely agree.  When making image adjustments for physical prints, I have to write on the prints what I change between each test print.  So much easier in lightroom.  In fact, I've started exporting images to lightroom and doing final edits there so I can keep track of what is changes.  The lack of edit history really diminishes C1 for anyone who makes prints.....

    5
  • brucemherman

    I agree that CO (C1?) should record editing history. 

    6
  • john hardiman

    Big thumbs up from me on this request too.  Checking a tick box for adjustments which have been made is definitely not the same function as a history panel.

    What problem do you see this solving?

    I need to step back several steps to a specific point in time (not just undo).

    Usage:   I am currently working on art reproductions and I had correctly set the white balance of an image.  Later,  I came back to the image in Capture One to trial some adjustments to white balance to trouble shoot an issue.  Forgetting that Capture One does not have a history panel (Like Photoshop/Lightroom for example), I made ad hoc adjustments to the white balance and was unable to find my previous correct setting.  Resetting white balance would not help.  I could only fix it by searching for a previous image of a colour checker card and making a copy of the correct white balance settings.  History is a fundamental part of Photoshop and Lightroom and should be in Capture One also.

    When was the last time you were affected by this lack of functionality, or specific tool?

    Often.

    Are you using any workarounds or other solutions to achieve your goals in Capture One?

    The point of a history panel is often to fix something that went wrong, there is no work around for making a mistake, since it's a mistake. Only a history panel can fix things that went wrong if a specific set of settings is required or if you don't quite know what was changed and you need to find a previous state.  Using Undo is not the same as you can not see the steps and work out where you were.

    Are you happy to be contacted further about this suggestion or request?

    Yes.

    4
  • SFA
    Top Commenter

    Have people considered using variants in order to be able to retain each set of differences for instant comparison and future use?

    -3
  • Dickon Whitehead

    Re variants. Yes and that does not achieve the same result. You would have to know exactly when to make the variant in advance of the need for it. And then remember at what point you made that variant. Which without the history being available is not quickly achieved. Variants are still be useful though just not to solve the task of history info. If the variants were lockable they would be even more useful. I have a separate feature request on that!

    1
  • Chris Anson

    I concur. Please add a history panel to Capture One Pro.

    2
  • Raymond Harrison

    I support this request and honestly didn't think I ever would (never used it even with Lr) but someone else's comments above on printing was a good use, I feel. I use different variants for that purpose today. I'd rather have a better experience though than just a list of what I've done. Like variants, which are a physical representation of a set of changes, a history panel on a single variant with the ability to group a sequence of changes and annotate that group might be interesting, and then be able to select and compare the group (or probably make a variant off the group and then compare would be the way might see it). 

    I rarely want Capture One to lift-and-shift some capability. They have a very interesting POV on things (they've been at it for almost 25 years, in one way, shape or form) and I'd like that to be reflected in any implementation. After all, if I wanted C1 to be just like Lr, I'd just use Lr. 

    0
  • Peter Fuchs

    Please add a history panel to Capture One Pro - it really is basic functionality! Thank you!

    3
  • Raymond Harrison

    It definitely seems important for Lr folks moving over. Like dehaze, which also seemed really important to ex-Lr folks, I’m not sure I’d use it much, but for those who want or need it, I can imagine it could be a reasonably straight-forward thing to do. I personally don’t need a history panel most of the time, but would like the “adjustments used” indicators from the mobile app brought over to the desktop (the orange dot indicating a particular adjustment slider/control was used). That + the existing variants paradigm would be super-useful.

    1
  • Andrew Filipowicz

    I agree 💯

    0
  • BeO
    Top Commenter

    What? There is an “adjustments used” indicator in the mobile app? I have been requesting this for C1 desktop since years and just again recently and it has been set to "we have no interest in this" 

    https://support.captureone.com/hc/en-us/community/posts/4406797006737--Identify-tools-which-have-been-used-changed

     

    1
  • Benjamin Kim

    One of the reason why C1P sucks.

    -1
  • Raymond Harrison

    I’m curious as to why you’d use a tool you think sucks?

    2
  • Brica Wilcox

    A history panel would be a great addition. I used LR for a project recently and was reminded what a helpful feature it is! It would be awesome to have in Capture One.

    The other feature that is far more user friendly in LR is the copy adjustments feature where in LR, a box pops up where you can check or uncheck the settings you do or do not want to copy. SO much easier.

    1
  • BeO
    Top Commenter

    Copy adjustments:

    What is it exactly which is easier in LR, the box popping up?

    In C1 you have the Adjustments Clipboard tool. Select your target image, click the one-way copy icon, then the clipboard tool is filled with checkmarks, then select the target images and click the one-way apply icon. This is  one way of doing it, there are slight variations too.

    I suggest to keep this thread dedicated to "History panel" though.

    https://support.captureone.com/hc/en-us/articles/360002485038-The-Adjustments-Clipboard-overview

     

    0
  • Rani Joensen

    I 100% agree with you Graham, this is one of the main things I miss so much that light room has always had. Hope this will come as soon as possible

    2
  • Ben Dearnley

    One more vote from me for a history panel. Can a C1 rep please explain WHY it is not planned at the moment? Seems like a very useful tool, often requested, and probably not that hard to implement. Not to mention LR and other processing software has it already and it is so so useful. 

    1
  • Noob with a Nikon

    and probably not that hard to implement.

    I assume it's quite difficult to implement, that's why they don't plan to do it. Just like with other very popular requests like "locked variants" or "named variants" - I get the impression that C1's code architecture might not be very flexible, requiring extensive re-work for seemingly small adjustments.

    -1
  • Thomas Kyhn
    Top Commenter

    I assume it's quite difficult to implement, that's why they don't plan to do it. Just like with other very popular requests like "locked variants" or "named variants" - I get the impression that C1's code architecture might not be very flexible, requiring extensive re-work for seemingly small adjustments.

    That's very likely. Presumably the same goes for countless other issues and limitations. Perhaps it's time to take a break from introducing new features and finally do something about the fundamental parts of the software.

    0
  • SFA
    Top Commenter

    Such things are very often the case in Software development.

    Tacking a new field onto a database is easy enough. If it only existing in one place for a single purpose, giving access is easy.

    If it used for reporting ... it's actually less work to defer all reporting to a report generator than to embed dedicated reporting programs in the application.

    So Locked variants and "named variants" not only mean adding a field to indicate the lock and the name, they also require changes to just about every sub-program and screen in the system. 

    That's a lot of work for programmers and user guide writers as well as a lot of changes for user to get used to.

    Having a truly effective, all-encompassing and unconfusing History Panel function that can in fact offer what most requesters seem to be asking for, seems to me to be a lot of work requiring a lot of consultation and changes throughout the application to keep "changes" recorded and then be able to successfully revert to the place one thinks one might want to go back to. How complicated might the web of changes become?

    At what point does it become necessary to start an entirely new set of edit instructions on a new branch of the edit for a specific variant?   

    It would be very easy to spend a lot of time creating something that is only a partial solution to people's expectations and becomes something that absorbs a company's energies for very little ultimate user appreciation.

    I think it would be necessary to provide the option for users to identify "branch points" for an edit and to me (and some others)  they already exist in the form of Variants. 

    That opinion was one I formed nearly 2 decades ago using an application that offered both approaches - continuous edit history and a "branch out where you have got to" option. In effect, the continuous history became unusable without the option to break out a new branch with its own history AND then keep the changes as simple as possible before branching again. 

    To me, the History just suggested that by playing with all the tools available I would eventually find out what I wanted to do with an image and yet be able make a quick step back to a previous state when I took a wrong direction. It tempted me to try everything on every image. Variants suggested it would be better to work out what one wanted to do with an image and then seek a way to get there with, maybe 2 or 3 different approaches that could be instantly compared side-by-side.

    It seemed to be a better way to work then and I still think so today.

    0
  • BeO
    Top Commenter

    If using many brush strokes, or one is fine tuning a tool setting using the arrow keys in the numerical input fields or using the mouse wheel over the slider, how many / which historic states should be shown in the panel? 

    -1
  • Ben Dearnley

    If using many brush strokes, or one is fine tuning a tool setting using the arrow keys in the numerical input fields or using the mouse wheel over the slider, how many / which historic states should be shown in the panel? 

     

    Yes OK, fair point. How does Lightroom handle it? And how does C1's existing "undo" feature decide these things? I assumed there was already a log of recorded steps somewhere in the memory. 

    I guess when a slider is fine tuned in the way you mention, maybe the final figure can be recorded in the history when the user moves on to another tool or image.  

    1
  • BeO
    Top Commenter

    I guess when a slider is fine tuned in the way you mention, maybe the final figure can be recorded in the history when the user moves on to another tool or image.  

    That is the only reasonable way I can currently imagine, plus maybe a keyboard shortcut to explicitly make a snap.

    Each brush stroke is recorded in the undo list (though the list is sometimes emptied suddenly, with my old 15.2 at least). Don't have LR so I don't know.

    0
  • Ben Dearnley

    Yes, even a keyboard shortcut to record a snapshot of current settings would be better than nothing. This is what Hasselblad's Phocus software has. Very useful. Much better than multiple variants bloating and complicating the filmstrip, which is the only way I can see C1 having anything comparable. LR has snapshots as well. 

    0
  • SFA
    Top Commenter

    BeO wrote;

    "If using many brush strokes, or one is fine tuning a tool setting using the arrow keys in the numerical input fields or using the mouse wheel over the slider, how many / which historic states should be shown in the panel? "

    Exactly.

    Then consider how to deal with, say, the 1000 selected images that were actively being edited when  changes were being made using, say, style applications or speed-edits.

    If synchronizing metadata from external sources would that also need to be recorded in the history? 

    It could all get very complicated for both the developer and the user.

    That said, if it becomes a marketing "must have", so be it. That would be up to C1's management to assess the cost-benefit for the work.

    Please don't forget to make it optional so that I can turn it off!

    0
  • Thomas Kyhn
    Top Commenter

    A snapshot function has been requested here. I found this very useful in Lightroom. This is very different from a history panel, though, and would rather be used to save specific stages in the editing process than to save the whole editing history. Also, for snapshots to be useful and in order to remember what what stages they represent, you'd most likely want to name them, unlike the steps in a history panel. The advantage of a history panel is it does not require any action on the part of the user, and every step would be named automatically. 

    As for the quantification/splitting up of series of actions into individual steps, this works fine in Photoshop and Lightroom, so there's no reason to assume it wouldn't be possible in Capture One.

    0
  • Brian Jordan
    Moderator

    Thomas Kyhn How are these different from variants?

    0

Please sign in to leave a comment.