Repository navigation
screencast: encode TV-range yuv420p, not full-range yuvj420p - #37
Merged
Merged
Conversation
The frames are JPEGs (full range); the encode now converts to TV range, which every player and uploader expects.
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.
Follow-up to #36.
CdpScreencastRecorder's frames are JPEGs, so the encoded recording was full-rangeyuvj420p, a flag Safari/iOS and uploaders mis-show or refuse.encode_argvnow scales to TV range (out_range=tv) beforeformat=yuv420p; the ffmpeg test assertsyuv420p,tv. 217 passed.