Sync #1
Merged
Sync #1
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
Current spec always defines a timestamp for user constructed VideoFrames. Setting a real timestamp is especially important for frames that sent to VideoEncoder, as the timestamp is used for rate control. With no way for users to generate a null timestamp, it makes sense to make the type non-nullable. This also aligns with AudioData.timestamp. This patch also addresses the one lingering opporutnity for null timestamps: ImageDecoder used null as a default for output VideoFrames. This patch updates that default to be zero. While it could be argued that null is technically more correct (we don't often present images on timeline), this is outweighed by the practical impact of using zero which allows us to define a clear contract: VideoFrame always has a timestamp.
…me_timestamp_fixes
A `<div>` cannot appear within a `<dl>`. Bikeshed used to automatically tie notes with the previous `<dd>` in a list but no longer does that, and generated HTML is now invalid.
Trailing `</dt>` has nothing to do here and now makes Bikeshed generate invalid HTML markup.
Use coded size in mp4-decode sample
We decided not to do this, but forgot to remove it from the spec. The fact that decode() calls stall until the next frame is available and the availability of the `completed` promise make it largely unnecessary. Clients which don't want to wait for for `completed` can instead handle a RangeError exception during decode() if no more frames remain. While not ideal it's inefficient to implement something like onchange since common formats like GIF would require us to attempt decode in order to update the frame count.
Co-authored-by: Chris Needham <[email protected]>
Revise processing model, fix queue size attributes
Add per-frame QP support to AVC
Enable configuration of AV1 screen content coding tools
Clone configuration should perform a deep copy
Fix usage of RFC2119 words in privacy and security section
Editorial: account for SharedArrayBuffer change in Web IDL
Fix remaining normative language issues
Changes: - Adds a requirement for a public specification that is stable - The WG may consult external expertise as part of its review - Fixes the numbering in the source document
This should be helpful for developer to test the browser implement or compare the performance of different codecs on different platforms. Note that the previous version of mp4box is not able to parse AV1 video codec string correctly, so to support AV1, we also need to upgrade mp4box to version 0.5.2. Safari doesn't support `gl.createShader` so change the default renderer to `2d`. All sample videos are encoded from `bbb-1920x1080-cfg06.mp4` using ffmpeg and shaka packager.
Fix HEVC registration text
Replace RFC2119 wording in Security Considerations
Fix normative language issues
Add to codec registry requirements
Add AudioDataInit.transfer
Add ImageDecoderInit.transfer
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.
No description provided.