-
Notifications
You must be signed in to change notification settings - Fork 29
cmm: Make log_100 and log_316 TFs symmetric #826
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
Open
kennylevinsen
wants to merge
1
commit into
mahkoh:master
Choose a base branch
from
kennylevinsen:log_eotf
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Binary file not shown.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like this should just
clamp(c, 0.0, 1.0)like the other SDR transfer functions.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem is that when
cis zero,pow(vec3(10), vec3(2.0) * (c - vec3(1.0)))yields0.01, so a clamp wouldn't help.The approach is similar to
compound_power_2_4. and matches what is done in their respective inverse EOTF's (a mix overgreaterThanEqual(c, vec3(0.01))andgreaterThanEqual(c, vec3(sqrt(10)/1000)), respectively).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem I see with your current code is that it creates a discontinuity at 0. I.e.
E=0maps toO=0butE=epsilonmaps toO=0.01. For a single black tile that would be fine, but I'm not sure if it would be fine for a gradient or any image that just so happens to have a black pixel.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The step in log_316 is small enough that it is unlikely to matter, but log100 clearly shows the discontinuity in the gradient (images below).
Searching around a bit I don't see a whole lot of implementations to reference, but the fix matches gstreamer and the color-science python package. moxcms does neither and instead uses the midpoint to minimize the maximum error. Not a whole lot of support out there for these TFs though, so don't really have much in way of a benchmark or convention...
Plain gamma22:

Before this fix:

After this fix (note the left side of the gradient bar):

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to use 0 as the fixed point, which is what all other EOTFs do right now, then maybe applying an affine function could work:
However, I'd prefer to standardize these things in https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/main/staging/color-management/appendix.md.