-
Notifications
You must be signed in to change notification settings - Fork 139
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
Is there a way to keep and process chunks in WASM only #148
Comments
I expect it wouldn't make any difference. @ecmziegler to confirm |
How would that work? WebAssembly/design#1162 isn't solved, so there is a copy, so it's slower. Of course then you can use WASM to process the encoded packet, but this really is orthogonal to Web Codecs. |
@sumeet-tiwari-samespace Applications which formerly used WASM for video encode/decode are moving to WebCodecs, because of the improved performance. So while WASM is viable for audio encode/decode, it will not improve performance in video encode/decde, even with WASM SIMD and a Dedicated Worker. |
I think this is about post-processing the packets/frames in WASM, right ? Not really encoding/decoding in WASM. |
yes @padenot |
Then I'd just say that it works today, but it might work better at some point if/when WebAssembly/design#1162 is designed and implemented and shipped. Because this is not a Web Codecs issues, I'm closing this, but please feel free to open more issues if needed. Thanks! |
If we pass a WASM function as the callback to the encoder, will it be good for my performance or will it not make any difference.
The text was updated successfully, but these errors were encountered: