-
Notifications
You must be signed in to change notification settings - Fork 53
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
Support VP9 encoding? #7
Comments
It currently does not support VP9. It would probably make the library considerably bigger. I’ll take a look at some point (it also depends on browser support). |
I had a first stab at this and managed to get it running: Joe-Palmer@6598e3a The encoder gives me data from live.html but it does not play in the video as it throws this exception:
I'm going to analysis the data to see if it is valid video data but if you have any ideas as to why this exception occurs, let me know. Regarding the size, the .wasm file roughly doubles (874 KB) when including the VP9 encoder which is a trade-off I am happy with for the improved video quality. Maybe it should be an option for the user to choose VP8, VP9 or both when compiling. |
Oh great stuff! Who would have thought it’s that easy :D My hunch is indeed that the SourceBuffer gets removed because the data is invalid. I don’t remember if there’s on
Yeah either that or we compile them into separate .wasm modules. |
@Joe-Palmer Have you fixed the |
@Joe-Palmer One issue is that the first message from |
I haven't had a chance to work on this since but do plan to at some point soon. Thanks for the tip 👍 |
@Joe-Palmer Two other issues are 1) |
@surma Is |
@surma At
|
@Joe-Palmer A single
|
Nice work! I have added your code to Joe-Palmer@dacbb85 My video was not encoded correctly, but this may just be the incorrect video resolution. I will investigate further in the coming week... |
@surma It wasn't! :) I have learned more about WASM and have a good debug environment setup so I'm now in a position to focus on getting this working. Simply changing This is where I feel having a better understanding of the VP8/VP9 inner workings would be really helpful. Does anyone have any ideas why these errors might be happening? Or any suggestions on things to try to find out more? Thanks in advance for any help you can provide. |
Good news! I have managed to make the required changes to successfully encode VP9 😄 https://github.com/Joe-Palmer/webm-wasm/pull/1/files This obviously hardcodes it to VP9 so VP8 no longer works. I assume you would want to support both so I haven't created a PR to this repo but happy to if that is helpful. |
Great work! I’ll get back to this soon, I am currently swamped in some other efforts. If you fancy, feel free to turn this into a PR with some sort of switch to either load the VP8 wasm or the VP9 wasm :D |
Is it possible to support VP9 encoding with this great library?
The text was updated successfully, but these errors were encountered: