Recommend using extended transfer functions to handle negative values #434
Conversation
This file contains 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
simontWork
approved these changes
Mar 1, 2024
fintelia
reviewed
Mar 1, 2024
index.html
Outdated
| <p>If <code>Video Full Range Flag</code> is <code>0</code> | ||
| (a <a>narrow-range image</a>), recommended practice | ||
| is to define transfer functions | ||
| such as EOTF or inverse OETF |
There was a problem hiding this comment.
The EOTF acronym doesn't seem to be defined anywhere else in the document. It would be nice to avoid introducing new terminology just to explain how to handle the Full Range flag, but at very least the terminology should be defined
|
Re-requesting reviews due to addition of EOTF and OETF definitions |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Would fix #420