AcademySoftwareFoundation / AcademySoftwareFoundation/OpenColorIO
[RFC] support for role names as the process_space in Looks
- Dominant language
- C++
- Stars
- 2.1k
- Forks
- 503
- PR merge metrics
- No merged PRs in 30d
Description
Recently I've been thinking a bit about how to improve the config format, so I'm going to open a few issues to spawn some discussions, relates to the recent v2 working group meeting discussion.
One thing I noticed this morning, is that it is not possible in v1 to use a role name for the process_space in a Look (running ociocheck fails as an example).
My specific use case was I wanted to specify in a generic way that client supplied LUTs 'client Look' should be applied in 'the client Look colour space', using the role as an indirection layer, which also helps with anybody reading the config, with understanding the intent.
I know there are limitations with this, when you have a requirement for multiple colour spaces, but I had another thought for that...
Contributor guide
Research direction
Start by examining the v1 config handling exercised by ociocheck, focusing on how process_space is interpreted for a Look. Compare the current behavior with the proposed role-name indirection and define the configuration and validation behavior needed to support the use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100