5/21/2023 0 Comments Maya 2022 ocio![]() This would aid those people and it's a big. Those that don't have someone to write config for them and need to understand the config. Carol: Another group pf people sit between authors and users.Current toolkit not complex and solves all these problems without extra level. Mark B: Who needs it other than the config author? If you're the author you know where you need to_ref and from_ref.Don't like to compromise, but if have to have it, see benefit of it being explicit. Agree having them in there as first class citizen potentially perpetuating workflow and simplistic interpretation of color management to avoid. MArk B: Increasing complexity with little benefit.Carol: Should be explicit though, call this what it is, not a color space.Just a block in chain that joins images together. Mark B: Color spaces are a simplification to allow talking about OCIO.If they are going to do it, and ACES config has it, and should be called what they are. Don't want to frame the question as: is this a good idea for color management? Most on same page to not recommend it. If you say we don't want you to use named transforms, clear way to talk about the scenario. See it as making it clearer to people how to do color management. ![]() If you're worried about encouraging this behavior, I don't see that. Reality that some want these and we should not call them color spaces. Right now masquerading these as color spaces, but they aren't. Not that we're encouraging this, just calling it what it is. Doug: To clarify, think its clear users feel a need for this.Everyone has valid point of view, but as a whole, what is the missions statement here? Are we willing to compromise OCIO principles, or are there decisions and workflows we want the industry to move into? J: Valid question, is there an appetite for something like this as a guiding path? Love to get input on that.OCIO is an opinionated color management library, not just a toolbox. Going to be enabled to work how they want and think they have OCIO blessing. Those that don't understand color management are not are not going to be set right by named transforms. If you're trying to get facilities caught up in a non-disruptive way, this would be an ok way to do that since it's saying what it is explicitly. Carol: If not using the standard ACES config, using nuke-default, not making own configs.Don't want to enshrine these workflows, allow people to break the model. Mark B: Talking about OCIO, not legacy workflows.Doug: Not recommending this approach, just saying it's a reality that a lot of people want to work this way.Mark T: Just to replicate Nuke color management system.Just proof of concepts to get Nuke color management outside of Nuke. J/Mark B: Legacy config, made to allow continuation of Nuke workflows with OCIO. ![]() Looking in OCIO example configs repo, one is called nuke-default, a Foundry config, made up of these sort of utility transforms as well. Proponent of the benefits of working proper color managed way, but a lot of our users have not gotten to that point yet.
0 Comments
Leave a Reply. |