As I have the same camera Ive got some notes:
- Ignore the blackmagic colorspaces for practical reasons, their names are pure nonsense, I would not even consider shooting prores on these things, braw is just … better, and nuke can now nust read it too so its a non issue really, For legacy workflows I treat BM like its LogC (debayer straight to LogC)
Regarding the colorchart stuff just from a practical standpoint I would not do that in resolve
-
Its not reversible in resolve, it is with mmcolortarget however.
-
Colorchart accuracy is questionable @Thomas_Mansencal I think made a great blog post outlining the difficulties of using them for camera calibration, since then I switched to using 18% grey patch whitebalance and exposure only. Ill try to find it and post it later, I have to say though that I didnt quiet undertsant why exactly this is a issue but tbh… (bur i kinda trust thomas sooo, haha)
Here it is:
The ColorChecker Considered Mostly Harmless | Colour Science
The basics of what I understood from that:
Values of “ideal” colorchart cant be compared with any actual shot colorchart because of different illuminants and spectral distribution. and that reversing the operation after neutralizing using a 3x3 matrix can introduce errors. I cant say i have ever had any issues by using mmcolortarget in practice so far, I might be dodging a bullet and I actually do a greycard in addition to a mcBeth nowadays I am supervising on set because of this and then I am only using mmcolortarget to match the hdri to the neutrally balanced plate (and i try to put colorchart in the same spot with the same light) and that usually turns out well.
-i just find it easier to balance in nuke.
-Blender: Blender is not applying OCIO viewers to camera backplates, so thats fun… you have to make special backplates for blender that are completely mangled , It goes like this:
AcesCG-> lin/sRGB then gamma 2.6 to gamma 1.8 colorspace node in nuke then export that as acesCG(or raw… same same) as EXRs feed that into blender and set input colorspace to acesCG.
Its stupid. And definetely not right but it at least gives you a backplate thats somewhat close…
-Also Blender: Blenders ocio implementation is a bit rough so you want to create a simplified ocio config or else you will hate your life trying to find stuff, note that buke 13.1 is very picky when it comes to syntax of ocio configs like when you remove a colorspace you also need to remove the aliases.
Trying to think if it would ever make a difference if you greybalance before or after 
Also depends on what after and before is, with a raw that you debayer straight to aces your before controls would be the raw settings, for a prores, the before would be before the IDT, For me the debayering to ACES is a blackbox, and I have no idea where and how the whitebalance settings are applied.
With Braw there is also the thing that its not really raw, so thats another special case, so there is probably just colorspace transforms under the hood.
To be fair in most vfx productions you wouldnt dare to touch raw settings unless specifically told to do so. But I am interested in learning if there are better ways.
feel free to join our vfx editor discord channel as well if you like discord 