Jump to content

dsideb

Members
  • Content count

    3
  • Joined

  • Last visited

About dsideb

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Stokerg, I actually have a license of Affinity Photo and did went through the documentation and online videos. From what I see, the configuration is evaluated once and the interface only gives access to the Display transforms (as a combo-box selector in the 32-bit preview panel) and colorspaces (as a correction layer that applies a colorspace conversion). If Affinity Photo had a scripting API and was exposing the current OCIO configuration, I would be able to update the variables through a script but I don't believe that's an option for now. In any case, it would be better to offer a way for the user to re-define values of theses variables on the fly , and in that regard, Nuke's solution is a good inspiration:
  2. Hi everyone, I was wondering if Affinity Photo was capable of handling OCIO context variables? It's quite common in the film industry to define context-driven colorspace(s) in the OCIO configuration. Either by having a variable part in the search path, or directly in the name of a LUT/CDL file. Theses variables can be then set to different values at runtime and force updating the resources loaded by OCIO processor(s). An example of this being implemented at the user-level is Nuke OCIODisplay and OCIOColorspace nodes that expose a "Context tab" where you can define key-values where the key is the name of variable and value the literal value (e.g. SHOT sc010_0010). This is a quite essential feature for TV shows, feature film etc... I'm happy to elaborate more if needed be. Best, Nicolas.
×