There is a thing called a Node Tree.
Not this sort of tree, but this type of file.
I did not get it for a long time, partly because I am a stills shooter and tend to work in a pretty linear way, because I do things in a set order from RAW so as to reduce too much messy over working of the pixels in my files and to stay consistent.
If you do things in the right order, do them well and complete them properly, you will get consistent results and minimise file damage.
Layers are the same. They are each separate so that each job can be done properly then combined and there is a best order of business to use.
Nodes are basically layers.
They separate each task so that maximum cleanliness can be achieved and the best order applied.
Nodes in DaVinci Resolve were not my thing, but they have become a must do for me because;
I want to do as little as possible to my files with maximum effect.
I want to do the right manipulations the right way.
I want to do them in the right order (this is very important).
I want to be consistent, especially when different cameras are used**.
I also ant to make sure I remind my self of the options available.
My previous process was similar to my RAW processing, but I was wrong and it showed. I would process B-Raw manipulations for exposure and white balance, then do the three-wheel dance of Lift/Gamma/Gain, which was then supplemented by LOG Shadows/Mids/Highlights because I read that these were cleaner and more logical.
This then became a switch to Linear Gamma, which allowed me to more gently control all the above with one wheel and a less twitchy one at that. This was a breakthrough for me, because it allowed me to process by eye and more intuitively. This, combined with properly setting up my project settings, looking at colour better (Colour Slice and HDR Channels), were helping.
The whole thing was becoming more on point, but not more organised.
I needed a Node Tree and it turns out there are a lot of opinions on this and I have found, the strength of power grading (not just applying LUT’s), is also the perceived weakness in that at some point you have to balance applied knowledge with personal preference.
No, there are no “one answer” rules here, but there are cleaner and stronger ways of working.
My sources are Cullen Kelly and Darren Mostyn with a little help from “Write and Direct”. These three are all reliable, knowledgeable and accurate, but they also vary in answers such as;
https://www.youtube.com/watch?v=hOSkEnupHUM
My Node Tree is based on Cullen Kelly’s latest with some mild changes to suit my realistic work flow, because some things he covers are still beyond me.
This assumes the use of B-Raw in some form to Da Vinci Resolve.
0. Project settings; https://www.youtube.com/watch?v=NnNqjPbfIG8 .
1. Colour Space Transform Node. This is the input transformation Node to tell Resolve what camera took the footage, what codec was used, what color space is going to be used to process the file, preferrably an expanded one. Black magic film gen 4/5 > BM film gen 5 > DaVinci wide gammut > DV Resolve Intermediate). This tells the
2. Colour balance Node. This node is before the one below (exposure) but will be used after it. This is the one wheel instead of three fix that pro colourists use and was a game changer for me. With a single wheel (Gain), I will be able to balance colour and white balance by eye with a gentle and precise touch. Gamma > Linear > Gain ball.
3. Exposure and Contrast Node. This can be done with the above wheel, but is better done in LOG setting. Apparently the effect on shadows is cleaner and more logical. LOG > Global wheel > exposure, and the second part is putting some punch into an image. LOG > Shadows/Highlight wheels > contrast.
4. Saturation-Global. This one I will just do as Cullen does. HSV > Colour space > turn of channels 1 and 3 and use 2 only (Saturation).
This is the end of the core manipulations
5a*. (Parallel Node) Saturation-Specific. This is also a Cullen recommendation, to use Colour Slice for more specific saturation and density changes. The common trend here is to use newer generation tools that work cleanly and more precisely than older, more global tools. > Colour Slice.
5b*. (Parallel Node) Power Windows. This is a little beyond my pay grade just yet, but I will be using it a lot I hope. It is the ability to locally effect an image area with masking, picking etc.
6. Reflection Node. This is the node where last touches can be made or possibly and preferably even re-visiting the previous ones to fix any issues. This may, should even end up as a spacer
7a to x. Textures and Effects. This is where the little extras are added like noise reduction, de-blur, filters etc, because they are destructive if used too soon (crude and heavy handed tools I assume) and tend to slow down my computer (especially blur and noise reduction). As desired or needed.
8. Colour Space Transform Out. This is where the wide gamut colour space is transformed back into a more deliverable form. So you have gone from opening up the work space to now delivering something standardised. DV Wide Gamut > DV Intermediate > Rec 709 > Gamma 2.2 (becasue my monitor is not referenced e standard or I would use 2.4).
This may be changed to DV Wide Gamut > DV Intermediate > Rec 709 > Cineon LOG. This is if I want to apply a pre-loaded Resolve film stock look.
9+. Audio Balance and Effects. My choice here as it is not mentioned in other trees, but by now I have heard the track a lot, the and fixes tend to be like above, heavy and destructive, so late in the picture makes sense.
So, basically 4 core Nodes which should produce a finished base file, 3 secondary ones for effects, fixes and deeper repairs and an export Node.
*A parallel Node is used when several Nodes are of equal importance coming from a previous Node and no linear contamination is wanted.
**By using a consistent CST-In Node, I will be treating B-Raw and V-Log files the same way, but still getting maximum quality from each. Technically B-Raw files have their own window and settings, but using Pana cams, not all of these are fully enabled, so for consistencies sake, using the same tree is faster.