docs(readme): record colour handling, and the new 4:2:0 10-bit format - #77
Merged
Merged
Conversation
Three gaps against what 1.0 actually ships. The output colour format list was missing 4:2:0 10-bit, added so a 10-bit source can keep its grading through a GPU encoder — no NVIDIA card before the RTX 50 series can encode 4:2:2 at all, which the row now says, since "matching the source" being unplayable is only half the reason to change it. The hardware encoding row now says a format the GPU cannot take is converted rather than failing the job, and that the panel says so first. And colour tagging went undocumented entirely, despite being one of the larger behavioural fixes in this release: without it every output was untagged and so read as BT.601 limited, shifting the colours of any BT.709 or full-range source. That, the depth handling, and the 8-bit-units convention for every threshold in the interface now have a details block of their own — the same ground the new in-app explanation covers.
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
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.
Three gaps between the README and what 1.0 actually ships.
<details>block, covering the same ground as the new in-app explanation.The filter table itself was already current — #75 refreshed it, and #76 added no passes.
Docs only, so
ci-test.yml'spaths-ignoreskips the test gate.