Displaying old editing history

[anon8280290]

@priort

Thinking on it people might apply a profile with modules set to their desired settings but disabled at least initially and for some images they would be activated at some point and maybe not on some others

Tried that - changed the the disabled settings of ‘Microcontrast’ and saved the .pp3 - the attributes remained at default. Even worse, the module name in the .pp3 was ‘SharpenMicro’, not ‘Microcontrast’ !!

Do you use RT?

[priort (Todd Prior)]

Only occasionally so I’m not to be trusted

[elGordo (Gord)]

@anon8280290

As far as I know, the .pp3 does not contain “the history stack”.

In other words, if the history stack shows a sharpness changed to say 3 then later changed to 5 and later yet changed to 4, the .pp3 will not show the values of 3 and 5, only the last value of sharpness (4).

That’s true: it’s conceptually similar to a compressed history stack in darktable.

You can exit RT, rename the .jpg.pp3, and reopen RT and the same raw file, and you will not see your old edits.

[anon8280290]

@elGordo

That’s true: it’s conceptually similar to a compressed history stack in darktable.

You can exit RT, rename the .jpg.pp3, and reopen RT and the same raw file, and you will not see your old edits.

Sorry, I don’t use dt. What exactly is a “compressed history stack”?

[elGordo (Gord)]

The manual says it better than I can:
“Click “compress history stack” to generate the shortest history stack that reproduces the current image. This causes all edits above the currently-selected step to be discarded. If any module appears multiple times in the remainder of the stack, these will be compressed into a single step in the history.”
( darktable 4.6 user manual - history stack )

[anon8280290]

@elGordo

The manual says it better than I can:
“Click “compress history stack” to generate the shortest history stack that reproduces the current image. This causes all edits above the currently-selected step to be discarded. If any module appears multiple times in the remainder of the stack, these will be compressed into a single step in the history.”
( darktable 4.6 user manual - history stack )

Thanks! The history stack itself is quite impressive:

The history stack stores the entire editing history for a given image, in the order in which those edits were applied. It is saved to darktable’s library database and the image’s XMP sidecar file and persists between editing sessions.

[bobm]

xpatUSATed Cousins

5h

@elGordo

Don’t forget that the raw file never gets altered, so the history stack in the pp3 provides the instructions to get you from the raw file to the image you created previously. If you didn’t have the history stack, you would need to do all your previous work again.

As far as I know, the .pp3 does not contain “the history stack”.

In other words, if the history stack shows a sharpness changed to say 3 then later changed to 5 and later yet changed to 4, the .pp3 will not show the values of 3 and 5, only the last value of sharpness (4).

Blockquote

But that’s all you need. That is all your final result depends on. I can’t think of any reasonable re-editing scenario that would require you to know the winding path you took to reach your final result. The order in which you change things doesn’t affect anything.

I suppose that maybe would want to experiment with various “finishing” edits. In that case you can save your intermediate stage pp3, in whole or in part, to either file or clipboard.

[anon8280290]

@bobm

But that’s all you need. That is all your final result depends on. I can’t think of any reasonable re-editing scenario that would require you to know the winding path you took to reach your final result. The order in which you change things doesn’t affect anything.

I suppose that maybe [you] would want to experiment with various “finishing” edits. In that case you can save your intermediate stage pp3, in whole or in part, to either file or clipboard.

I’m not the one asking for the history stack to be saved somehow. In fact, I already said that I don’t understand the need for it.

[bobm]

I apologize for misrepresenting your viewpoint. I have been following this thread closely but clearly that didn’t include associating the various viewpoints with their advocate accurately enough.

[anon8280290]

No problem, Bob. Where I’m from (England) “you” is often used to mean “one” …

[EsTaF (Дмитрий)]

Or maybe we don’t need this “history” yet?
The program sometimes crashes even without this “history” ;( The program fault unexpectedly · Issue #7101 · Beep6581/RawTherapee · GitHub

Please.

[paperdigits (Mica)]

Not every single bug will be fixed before adding features. This is not a realistic expectation or ask.