Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Built-in Transforms should be used when available #103

Open
doug-walker opened this issue Jul 4, 2023 · 0 comments
Open

Built-in Transforms should be used when available #103

doug-walker opened this issue Jul 4, 2023 · 0 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@doug-walker
Copy link
Contributor

In some of the color spaces (e.g. camera logs) the current configs contain individual transform operators even when a Built-in Transform is available.

The benefit of that is that it is more apparent what math is being applied. The drawback is that it is not apparent at a glance whether the matrix coefficients and etc. are really the correct ones for that color space (e.g. a specific camera log) or whether they have been tampered with.

At the working group discussion today, it was felt that it is somewhat preferable to use the Built-in Transforms whenever they exist. This proposal is to update the Python script to insert a Built-in Transform if it exists for the given OCIO version that the config is being built for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants