Skip to main content
Inspiring
April 11, 2011
Open for Voting

P: Lightroom: consolidate/flatten/merge history steps

  • April 11, 2011
  • 41 replies
  • 1246 views

Give us the option to consolidate/merge history steps.

All the little adjustments with the crop tool (it's often impossible to reach the final crop in a single operation) could be flattened to a single step, all the little stacked basic adjustment tweaks (+5, -7, +3, yada, yada), all the individual brush strokes, etc. could be flattened to a single adjustment.

This would make the history considerably cleaner and simpler - which makes much better use of the limited screen space (scrolling back down through presets and history is a pain).

41 replies

Inspiring
April 12, 2011
I'd merge the individual brush strokes to the mask displayed with the associated pin - again, it's the resultant mask I care about, not the stokes made to create it.

Slightly simpler with grads in the sense that each grad would remain discrete, but any adjustments to the effect applied would be consolidated to a single change (as if the adjustments had be set before applying the grad and it had been applied in its final location/width/etc)
john beardsworth
Community Expert
Community Expert
April 12, 2011
What Lightroom could do, for example, is *display* the current adjustment status in terms of differences from the default - that was partly why Lee Jay pointed you to the other thread. I think there's some value in that, and the data to do so is already in the catalogue. It's just a matter of calculating and displaying it.

How would you propose summarising local adjustment brush activity?
john beardsworth
Community Expert
Community Expert
April 12, 2011
What Lightroom could do, for example, is *display* the current adjustment status in terms of differences from the default - that was partly why Lee Jay pointed you to the other thread. I think there's some value in that, and the data to do so is already in the catalogue. It's just a matter of calculating and displaying it.

How would you propose summarising local adjustment brush activity?
areohbee
Legend
April 12, 2011
"Do we need an alternative panel?" - Nope.

The edit-history list is basically a dump of the edit-history table in the database. Its totally doable to add the feature you've requested to the existing edit-history list. But here I go infringing on Adobe territory again - sorry.
areohbee
Legend
April 12, 2011
"Do we need an alternative panel?" - Nope.

The edit-history list is basically a dump of the edit-history table in the database. Its totally doable to add the feature you've requested to the existing edit-history list. But here I go infringing on Adobe territory again - sorry.
Inspiring
April 12, 2011
But by your terms, I fake my history.

If I make an adjustment and don't want to keep it I'll probably undo it (rather than making a subsequent adjustment to negate it).

If I make a sequence of micro adjustments, I might roll back to the starting point and apply my final settings as a single set (because I might want to treat another image the same way and I don't like the magic of sync settings).

The last thing I want to do is discard the visibility of the changes to the image, but I really want to see the changes necessary to deliver the end result (including presets), not the individual steps. Maybe that's not history and we're debating different things.

Do we need an alternative panel?
Inspiring
April 12, 2011
But by your terms, I fake my history.

If I make an adjustment and don't want to keep it I'll probably undo it (rather than making a subsequent adjustment to negate it).

If I make a sequence of micro adjustments, I might roll back to the starting point and apply my final settings as a single set (because I might want to treat another image the same way and I don't like the magic of sync settings).

The last thing I want to do is discard the visibility of the changes to the image, but I really want to see the changes necessary to deliver the end result (including presets), not the individual steps. Maybe that's not history and we're debating different things.

Do we need an alternative panel?
areohbee
Legend
April 12, 2011
I too would prefer a well designed native interface.

But, I *may* also be willing to use an app/plugin that implements a database solution. I prefer the term "reverse engineered" to "hack", since the former sounds professional whereas the latter sounds "iffy".

Hopefully it won't come to this...
areohbee
Legend
April 12, 2011
I too would prefer a well designed native interface.

But, I *may* also be willing to use an app/plugin that implements a database solution. I prefer the term "reverse engineered" to "hack", since the former sounds professional whereas the latter sounds "iffy".

Hopefully it won't come to this...
john beardsworth
Community Expert
Community Expert
April 12, 2011
Sure history doesn't include undos (and I don't think it's worth adding them), but minor incompleteness doesn't invalidate the value of what's left.

Pedantic, I know, but I did say "supervise". That means being responsible for running the PP guys. Had the history been faked, how would a training need be identified?

If people only care about the end result, they can do without history entirely, can't they? That ability is there already. If you need a simpler display, ask for that - don't mess with the underlying data.