Single Node Presets

Please add simple one node presets. No still image embedded is required, just a text name.

Using stills presets are not always usable, because they replace all the node tree and require a lot of additional prepare steps.

But if we will just add a preset by using a Node content menu like "Grab this node still", it will be more usable to create and edit.

This one-node presets can be developed as a current still presets. We only need to check a case when they are created using a special Node command and they store only one node.

Some examples of useful presets I can create:

- CST RED_To_Rec709
- CST Rec709_To_RED
- FilmGrain_1
- FilmGrain_2
- LowDenoise
- HeaveDenoise
- HSV_SAT
- ColorWarper_TealOrange
- ColorWarper_DesatLook
...

If you make a single node preset in the Stills Gallery, all you need to do is drag the whole still onto a new node in the node tree. You can also use the Append mode to add the still in one operation.

I do exactly what Peter Cave suggests above, and I think I've been doing it for at least 7-8 years now. I have these in a PowerGrade bin (actually 9 or 10 of them), each dedicated to different kinds of single node presets.

Here's one of them:



Note that once I have that single node that does one thing, I create a big title for it so I can read it from a distance, and I label the node itself, and I label the PowerGrade as well. When I need to do that one thing, I drag it onto my fixed node tree and go to town.

One of the PowerGrade folders is just for different kinds of cameras, so I can grab one for damn near anything (Alexa, Alexa 35, recent Red, old Red, Venice, Panasonic, Canon, Blackmagic, etc.).

Of course I know this idea. Many colorists use this way. I use too.

But the idea is to improve usability and speed for one node.

Of course I know this idea. Many colorists use this way. I use too. But the idea is to improve usability and speed for one node.

I think I answered this question.

I think I answered this question.

No one asked you any questions on the feature request forum area. If you personally think that many prepare steps to create a single node preset is a good idea, use this way.

I think the Resolve improvement for many users is better that your useless recommendations.

No one asked you any questions on the feature request forum area. If you personally think that many prepare steps to create a single node preset is a good idea, use this way. I think the Resolve improvement for many users is better that your useless recommendations.

Note that Peter Cave had a very similar answer. I think we're both right.

If you make a single node preset in the Stills Gallery, all you need to do is drag the whole still onto a new node in the node tree. You can also use the Append mode to add the still in one operation.

That's exactly how it works. A lot of tricks and situations with Resolve boil down to altering your work methods to get the most out of the software. If you wait for the software to change to match your work methods, you're going to be waiting a long time.

I think I answered this question.

No one asked you any questions on the feature request forum area. If you personally think that many prepare steps to create a single node preset is a good idea, use this way.

I think the Resolve improvement for many users is better that your useless recommendations.

Thet response seems quite rude when others are trying to assist you,

Aggressive assisting is not needed.

My point why I suggest feature requests is not because I don't know how to use software. I use Resolve since version 12. I want help to developers to find ways where software will be better and more functional.

When I see some users aggressive hate suggestions, I don't understand why they do not want to make software better. I remember old Resolve where we had no most features we use currently.

I think users who do not want new simple useful features (those may be easily created) should use Resolve 10 and never use HDR rings, Color Warper, Color Temperature correction, Midtone Details and so on.

I don't understand why a simple node content menu like "Create a Preset using this node" is a bad idea. I really need this simple feature more often than regular stills for a complete node tree I use.

I don't understand why a simple node content menu like "Create a Preset using this node" is a bad idea. I really need this simple feature more often than regular stills for a complete node tree I use.

That's not the way I interpreted the original question.

The way to do it -- at least, the way I do it -- is to do the following:

1) let's assume you've just created a node tree that has one node you want to use as a Powergrade for future projects.

2) create a new version. In that version, delete all the nodes except for the one you want to reuse as a Powergrade.

3) make sure both ends of the node are connected to the input and outputs. And make sure the node is labeled (and I usually slide it over to the left so it's more visible in the Node window).

4) choose the Powergrade bin and grab the node still, and label the new Powergrade still. (Optional: create a background and title so you can easily see this Powergrade still from a distance.)

5) now, go back to the original grade version and keep working.

You do this long enough, this becomes second nature and you can do it very quickly. I don't even think about it these days, because I'm trying to work as quickly as I can.

I think one of the operational issues is that you can have one node, two nodes, even 50 or 100 nodes in a Powergrade. There's no mechanism just to highlight X number of nodes and then "Save as Powergrade." Could it be done? Sure, but I think the dev team has about 979 other things to fix and take care of first.

There is no aggression here, just trying to help. Sometimes users need methods to achieve the desired result until the user feature requests are implemented. We can’t know how experienced users are until they explain in a post.