waltervolpatto wrote:Can you explain better? On my phone I cannot make out what you're doing.
Usually, when working in
DaVinci YRGB or
DaVinci YRGB Color Managed, changing node color space and node gamma go from timeline color space.
For example, If I set timeline color space to
AWG LogC and then set node color space to
Rec709 and node gamma to
Linear, I get transform from
AWG LogC to
Rec709 Linear at the input of the node and transform from
Rec709 Linear back to
AWG LogC at the output of the node.
If I change timeline color space to
S-Gamut3.Cine Slog3 and then set node color space to
V-Gamut and node gamma to
V-log, I get transform from
S-Gamut3.Cine Slog3 to
V-Gamut V-log at the input of the node and transform from
V-Gamut V-log back to
S-Gamut3.Cine Slog3 at the output of the node. And so on.
Everything ok with that and it works as it should.
When I change Color Science to
ACES I got
ACEScc(t) timeline color space. Everything fine with that too.
If I load any Resolve built-in plugin, which has ability to choose color space (CST, Gamut Mapping, Chromatic Adaptation) and set "
use timeline", all the plugins recognize timeline color space as
ACEScc(t). Still everything ok and it works as it should.
But all node color space transforms go based on
rec709 gamma 2.4 color space instead of
ACEScc(t) color space as it should.
For example, If now I set node color space to
RWG and node gamma to
redlog3g10, I get transform from
Rec709 Gamma 2.4 (instead of
ACEScc(t)) to
RWG redlog3g10 at the input of the node and transform from
RWG redlog3g10 back to
Rec709 Gamma 2.4 (instead of
ACEScc(t)) at the output of the node.
But transforming from and to
rec709 gamma 2.4 has no sense since our timeline color space is set by
ACES Color Science and fixed to
ACEScc(t).