1) Under Mac and Linux unless applications are color managed, ICC Profiles don't do much. Under Mac OS specifically, 1D LUTs for VCGT that maybe included in ICC Profiles can affect black/white points and gamma, is this correct? (source DisplayCal and ArgyllCMS documentation)
No, Mac applies ICCs OS wide.
Windows only applies the VCGT, unless the application is ICC aware.
Not sure on Linux...
2) Is there a way to reset/nullify the VCGT under Mac and Linux? Under Linux I used ArgyllCMS tools to verify the status of the loaded ICC profile as I can't seem to find any other tools to at least verify. No idea how to do that under Mac though, any thoughts?
No, Mac ICC use is a pain, as it cannot easily be disabled...
(We have never found a way to do it anyway...)
Again, not sure on Linux.
3) Is there any easy way to make sure Mac or Linux are not messing up my colors/gamma for the GUI display (as opposed to dedicated monitor which wouldn't have ICC Profiles)? I have SpaceMan ICC, can I generate a Null ICC profile from there by exporting a Linear LUT from LightSpace?
The only approach I can think of is as you say - a Null ICC.
But, will that actually make Mac colour null???
And a dedicated monitor will only Not use ICC if you are using a dedicated video output card (SDI connections).
4)Assuming an external dedicated monitor workflow(i.e. direct video output from Resolve or Nuke through Declink or similar), with LightSpace CMS, I'm profiling the capabilities of the monitor after manually bringing the gamma/white point/black point as close as possible to the output standard(e.g. Rec709 or Rec2020). With the main monitor(i.e. where Nuke or Resolve GUI's run), I'm doing the same thing but potentially "fighting" against the system color/gamma response implemented by the ICC profile(unless of course it's a null profile). Is my understanding correct?
5) Assuming profiling was done accurately and now I'm ready to create the calibrations LUTs for a dedicated monitoring workflow(e.g. through declink from Nuke or Resolve/Fusion): In LightSpace CMS I should be converting from the output color space of the application(i.e. Rec 709 Gamma 2.4 for the default project settings of Resolve, or Linear Colorspace for Nuke) to the profile generated by LightSpace for my monitor. Is this the correct approach?
It is the colour space you want to calibrate the display to that matters, not the graphics program.
So Rec709 G2.4
5b) If I'm using ACEStt in Resolve or ACEScg in Nuke as the working/output color space, I should follow the same steps as above but set the source color space to ACEStt or ACEScg, and destination of course to monitor profile, is this correct?
You should be using an ODT to set the video output to the standard of the display - Rec709 G2.4
6) For the profiling of the "GUI screen" I should do the same thing for color space conversion/LUT generation, although the OS's color management and would affect the ability of the LUT to do what it's supposed to do. Is this the right way of thinking about it?
As above, all display calibration must be to the target colour space standard - Rec709 G2.4
Mob Boss at Light Illusion