Christian Rush

Members
  • Posts

    7
  • Joined

  • Last visited

Course Comments posted by Christian Rush

  1. On 10/5/2021 at 1:06 AM, Jason Bowdach said:

    Same thing w ACES, project level can work, but it limits what "tricks" we can do, including the halation strategy I demoed - which is why many prefer using a "manual" ACES  (sometimes called Fake ACES, or Pseudo ACES) set up within the node tree, as it allows the best of both worlds - great, industry-standard color management + full control over the color pipeline. 

     

    So then I am assuming the halation compound must take place before the Aces Pseudo workflow? 

    Davinci YRGB: Halation Compound Node with the CST's for linear/ARRI in it > ACES Node 1 > Balance/Looks Nodes > ACES Node 2?

    halation.PNG

  2. Curious about something for CST if I'm working in RCM or ACES.  I've experimented but not sure I've done it exactly right.

    This is in relation mainly to the Halation effect.

    What seemed to work for me was a bit complicated but seemed to work best when working with an Arri Clip and DRCM since when enabling/disabling I saw no change, but I would love a double check:

    1st CST node:

    Input Color space: Davinci Wide Gamut

    Input Gamma: ARRI LogC

    Output Color Space: Rec709

    Output Gamma: Linear

    2nd CST node:

    Input Color Space: Rec709

    Input Gamma: Linear

    Output Color Space: Davinci Wide Gamut

    Output Gamma: ARRI LogC

     

    Thanks to anyone that can confirm this would be the best practice.  And for ACES I'd assume just switch the Davinci Wide Gamut option (in the CST nodes) to ACES version in the project.