How do I use history to restart editing from a certain point

[twm47099]

Sometimes when I process an image (starting with a raw) I decide I'd like to make a second version using using different noise reduction, sharpening, or making a B&W in addition to a color image, etc. But I may have sent some time straightening and cleaning followed by setting exposure and don't want to repeat those steps.

In some programs, I make a new version, and then go back and clear out the steps in history going back to the ones I want to keep. I can't seem to do this in ASP. I expect that I am doing something wrong. How could I do that?

Thanks,
Tom

[bananahead]

Choose View and then History.

You can then click on any point in the displayed History window to go back to any stage.

[DocBrown]

There is a small caveat to this if you use File System Mode. The history is only saved for your current session. To keep a full running history of all your edits, you need to be making them from within a catalog.

[larschristian]

I havn't used the history window for a long long time. In Bibble I could jump back and forward in the history. Now in ASP new history clears when I jump back! As soon as I jump back in history the newer history is cleared and there is a new step say "reset color". Is this an ASP problem or is is caused by a bad behaving plugin?

[twm47099]

Thanks, but I'm not sure I've got it.

What I want to do is keep the original version, make a second version and on the second version go back to the step I want to keep (such as straightening) and then continue processing the second version from there.

When I created the second version, the history showed nothing in it, although that version was obviously processed.

The original was imported into ASP.

I'm doing something wrong, so any additional help would be appreciated.

Thanks again,
Tom

[bananahead]

Hi Tom

When you create a new version from current it doesn't inherit the history.

What I do is - when I get to a point that I want to save - create a new version as the save point and then go back and make other changes to the original.

Cheers

Nigel

[lundbech]

Hi Tom

When you create a new version from current it doesn't inherit the history.

What I do is - when I get to a point that I want to save - create a new version as the save point and then go back and make other changes to the original.

It would be nice if you were able to browse history, but once you enter history you cannot go back to the future. So you have to make copies as you go along. Not the best solution. Having the possibility to browse the history (like in Darktable) and return would be very nice!

[Autark]

You can go back in history to the last desired edit and create a new version from that point, and then move forward to the current edit again. It is indeed unfortunate that the new version will not inherit the version history of the master.

It would be very handy to have a context menu item on each history item to create a new version from that.

[RickHeath]

You can go back in history to the last desired edit and create a new version from that point, and then move forward to the current edit again. It is indeed unfortunate that the new version will not inherit the version history of the master.

It would be very handy to have a context menu item on each history item to create a new version from that.

The history is still there - just it is in the original master version. Although I agree it could at times be handy to have the option of having the history in the new version. It is worth noting that in ASP, unlike in more "traditional" pixel editors, it generally doesn't matter what order you do a sequence of adjustments the end result will be the same.

If you want to go back in the history beyond the state where you created the version you would currently have to do it by making a new version from the master at that earlier state. And you can use selective copy & paste between versions if there is something you want to get from one to the other without doing all the settings by hand (for example, all the settings of a particularly complex plugin).

Regards

Rick.

[larschristian]

It would be nice if you were able to browse history, but once you enter history you cannot go back to the future. So you have to make copies as you go along. Not the best solution. Having the possibility to browse the history (like in Darktable) and return would be very nice!

Found in another thread that there is a confirmed bug in the zFrame plugin which causes a "Reset color" event that clears newer history. Tintin says it will be fixed in the next version.

[kaymann]

It would be nice if you were able to browse history, but once you enter history you cannot go back to the future. So you have to make copies as you go along. Not the best solution. Having the possibility to browse the history (like in Darktable) and return would be very nice!

Found in another thread that there is a confirmed bug in the zFrame plugin which causes a "Reset color" event that clears newer history. Tintin says it will be fixed in the next version.

And the zFrame also causes the 100% CPU problem.

[B4b5]

And the zFrame also causes the 100% CPU problem.

I think tin.tin has it here-> viewtopic.php?f=90&t=45441&p=240625#p240625

[kaymann]

And the zFrame also causes the 100% CPU problem.

I think tin.tin has it here-> viewtopic.php?f=90&t=45441&p=240625#p240625

Yes, it is awesome and I am continually amazed at how quickly and responsessive the plugin folks are - they are certainly deserving of our donations....