-
-
Notifications
You must be signed in to change notification settings - Fork 809
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
web,video: Add H264 decoding using the WebCodecs API #16794
Draft
torokati44
wants to merge
2
commits into
ruffle-rs:master
Choose a base branch
from
torokati44:external-video-webcodecs
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
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
torokati44
force-pushed
the
external-video-webcodecs
branch
5 times, most recently
from
June 27, 2024 18:30
65c01d8
to
e9c744b
Compare
torokati44
force-pushed
the
external-video-webcodecs
branch
from
June 28, 2024 00:57
e9c744b
to
877b6b1
Compare
torokati44
force-pushed
the
external-video-webcodecs
branch
5 times, most recently
from
July 23, 2024 19:23
816e327
to
c96c40c
Compare
torokati44
force-pushed
the
external-video-webcodecs
branch
from
July 29, 2024 18:03
c96c40c
to
43a992c
Compare
torokati44
force-pushed
the
external-video-webcodecs
branch
4 times, most recently
from
August 22, 2024 19:36
9afffe8
to
d40c036
Compare
torokati44
force-pushed
the
external-video-webcodecs
branch
2 times, most recently
from
September 11, 2024 10:03
c47534e
to
f3bd05b
Compare
torokati44
force-pushed
the
external-video-webcodecs
branch
2 times, most recently
from
September 12, 2024 11:06
35cf89c
to
bf5c71c
Compare
torokati44
force-pushed
the
external-video-webcodecs
branch
2 times, most recently
from
September 18, 2024 08:29
74cf97b
to
cf85e0f
Compare
Rebased on top of #17878. |
torokati44
force-pushed
the
external-video-webcodecs
branch
from
September 18, 2024 09:30
cf85e0f
to
033a7c7
Compare
torokati44
force-pushed
the
external-video-webcodecs
branch
from
October 2, 2024 09:49
033a7c7
to
f4edc57
Compare
torokati44
force-pushed
the
external-video-webcodecs
branch
from
October 21, 2024 13:38
f4edc57
to
98302d1
Compare
torokati44
force-pushed
the
external-video-webcodecs
branch
from
October 21, 2024 13:55
98302d1
to
d45c3de
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
A continuation of #14654.
Not really done yet, just pushing for visibility, and so that it doesn't get forgotten.
(Just look at the commit history lol.)Due to this API being based on callbacks, this currently adds at least one additional (video) frame of delay as compared to a synchronous decoder, such as OpenH264 on desktop. I think this should be acceptable.
It would be possible to wire the callback straight from the browser through the video backend to the renderer backend, to update the texture immediately (off the regular frame pacing schedule), but I think that would be a bit too complicated, and could potentially result in less smooth playback.
Mostly works, in Chrome and in Firefox 129+.
I don't think this could be problematic at all from a patents/licensing/royalty standpoint.
Advances #8891.