PR: Modify JFIF full range YCbCr. #1064
Merged
Conversation
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
Update JFIF example in docstring. Flake8 fixes. Add BT.2100 reference.
for more information, see https://pre-commit.ci
…colour into experimental/jfif-alt
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.
Changes to address points discussed in #1063
Modifies full range integer Y'CbCr (JFIF) to better match the spec in ITU-T T.871. Also applies to BT.2100.
Adds a
clamp_intargument toRGB_to_YCbCrandYCbCr_to_RGBto limit integer output to valid range forbit_depth.The
clamp_intargument is not added toYcCbcCrc_to_RGB. @KelSolaar please add if you think appropriate.