Blackmagic Forum

I am not expert in the Color page, so please bear with me.

Why "undo" function doesn't work with some nodes in the color page?
Please see the screen record in this link:


If I do any change, like removing OFX plugin or changing the saturation, for example, I can never undo the changes I made! Why?

Watch the link in YouTube to see it more clear in full screen.

It would seem that history does't include the operation "remove OFX plug in from menu of the node. Use trash icon in the effect panel instead or reset the node. Also keep in mind that there are separate history systems in edit and color pages, respectively. They are independent of each other.

KrunoSmithy wrote:It would seem that history does't include the operation "remove OFX plug in from menu of the node. Use trash icon in the effect panel instead or reset the node. Also keep in mind that there are separate history systems in edit and color pages, respectively. They are independent of each other.

Thanks for your feedback. But still Undo did not work after I reset the node or delete the OFX from the effects panal! Any idea what is going on?

I also notcied that undo does not work with "shared" nodes:


I an no expert in the Color page, so I do not know what are shared nodes!

Shared nodes in DaVinci Resolve are a feature that allows colorists to apply the same adjustments or effects to multiple clips simultaneously, ensuring consistency across the project.

"Shared nodes are similar to group grades, except that they don’t require grouping and can be added to any normal grade. Changes made to a Shared node are automatically rippled to all other instances of that node in the grades of other clips. Furthermore, you can add as many Shared nodes to a grade as you like, and you can arrange them in any order to control the order of the operations they apply. And, of course, you can intersperse them with ordinary Corrector nodes

Shared nodes are meant to be a way to extend the benefits of automatically rippled changes among different clips to colorists that prefer a flatter node structure than Group Grading allows. By turning individual Corrector nodes into Shared nodes, and copying these to multiple clips, you enable linked adjustments right from within the clip grade. This means that the clip grade can freely mix both clip- specific nodes and Shared nodes, all within the same node tree. This makes Shared nodes fast to use as there’s no need to create groups or switch to a group node tree (covered in the next section) to reap the benefits of linked adjustments among multiple clips."

If you are not used to working in color page , I would leave more advance worflows for the time when you are more advance users of the color page.

For more information in the manual you can find more infor. Color | Chapter 140 Grade Management

KrunoSmithy wrote:Shared nodes in DaVinci Resolve are a feature that allows colorists to apply the same adjustments or effects to multiple clips simultaneously, ensuring consistency across the project.

"Shared nodes are similar to group grades, except that they don’t require grouping and can be added to any normal grade. Changes made to a Shared node are automatically rippled to all other instances of that node in the grades of other clips. Furthermore, you can add as many Shared nodes to a grade as you like, and you can arrange them in any order to control the order of the operations they apply. And, of course, you can intersperse them with ordinary Corrector nodes

Shared nodes are meant to be a way to extend the benefits of automatically rippled changes among different clips to colorists that prefer a flatter node structure than Group Grading allows. By turning individual Corrector nodes into Shared nodes, and copying these to multiple clips, you enable linked adjustments right from within the clip grade. This means that the clip grade can freely mix both clip- specific nodes and Shared nodes, all within the same node tree. This makes Shared nodes fast to use as there’s no need to create groups or switch to a group node tree (covered in the next section) to reap the benefits of linked adjustments among multiple clips."

If you are not used to working in color page , I would leave more advance worflows for the time when you are more advance users of the color page.

For more information in the manual you can find more infor. Color | Chapter 140 Grade Management

Thanks Kruno for the detaild information .. I highly appreciate it. However this topic is too advanced for me learn now .. I will for sure learn using it in the future, I just now need to finish the project in hand, so I think its just faster to re-edit the backup project file without touching the color nodes. Thanks again.

Also, I wish BMD can fix this undo problem in the color page.

Agreed.

One tip I've given many times to students: instead of relying on Undo, right before you make a change, create a new version. Now make the change you want to make. If you want to see where it was before, flip back to Version 1. The Versions never go away (unless you actually delete them), and are more reliable than depending on an Undo operation.

Remember that Undos have several limitations, particularly with Global change operations, deleting timelines and projects, and with large-scale edit changes/deletions. In the case of the latter, I just duplicate the timeline and make changes on the duplicate.

To me, the Undos can only go so far. There's so much happening in every clip -- literally every pixel of every frame -- it can't do 100% of everything 100% of the time.

Another way of saying what Marc said:
Undo is buggy so use versions which aren’t.

I sure hope they improve undo at some point because “forgetting everything you know” about your NLE should certainly not extend to abandoning undo.

Good to hear that it's not "just me" who wondered why the heck undo doesn't work on the Color page. Seriously, the flagship page of BM and the undo doesn't work. It seems so basic.

It mostly works. But like many things in Resolve there are these niggling little bugs or missing bits that diminish what is still the best platform out there.

Marc Wielage wrote:One tip I've given many times to students: instead of relying on Undo, right before you make a change, create a new version. Now make the change you want to make. If you want to see where it was before, flip back to Version 1. The Versions never go away (unless you actually delete them), and are more reliable than depending on an Undo operation.

Thanks Marc .. do you mean to create a new version of the whole project, or something else?

Joe Shapiro wrote:Another way of saying what Marc said:
Undo is buggy so use versions which aren’t.

I sure hope they improve undo at some point because “forgetting everything you know” about your NLE should certainly not extend to abandoning undo.

You are correct, Joe. It is just way faster to just click undo for any change you dont like or did by mistake. BMD should consider fixing this instead of interducing new featurs of less importance.

Is this a bug? Should I make a new topic, or is this just as to be expected?

Firstly excuse the poor camera quality, I don't have any screen recording software.

Also, I'm not using ctrl+z just so you can see what I am actually doing.

You'll notice I make various changes and "undo" appears to work as expected. But then at 00:18 it doesn't....

at 00:23 I do a "redo" but then this seems to do what I wanted to do originally (i.e. undo)

I make some more changes, then at 00:32 undo seems to not work again?

Then at 00:35 even the "reset" button isn't working correctly?