-
Notifications
You must be signed in to change notification settings - Fork 119
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
AV1Payloader does not work for WebRTC #273
Comments
@aleksitto-gh tried this one ? |
@lebedyncrs yes, but it did not work for WebRTC |
Hello, I'm working on AV1 support and creating a Docker image to test Pion AV1 with various AV1 encoders and WebRTC clients. Currently, I'm working on adding tests for libaom and dav1d. If you share your code I'm going to add it to the image. Thanks. |
Hi there, I'm using the updated version of pion/rtp and pion/webrtc with av1_nvenc and I found that the AV1 track can't be decoded correctly by chromium on linux (only the first frame is decoded), but on windows, chromium works. I've put more detail in #299 , not sure if this is a platform-specific bug in chromium. |
I'd love to share my code using av1_nvenc with ffmpeg for the test if needed, currently the repo is private, I'll make it public after fixing a few issues. |
Your environment.
What did you do?
I'm trying to use AV1 codec for WebRTC using the libaom lib.
The encoding works fine but probably AV1Payloader is not ready for that yet.
As a result, there is no video in my browser.
I found the browser expects to see obu size info but it is not sent.
The obu size flag is set as required via libaom in the obu header, I guess it is a default behavior.
I tried to manually change it as not required for the first encoded byte:
Packet buffer logic with the manually changed configuration:
c++ additional functions:
it helped a little bit, the error with obu size mismatch has gone, but I found another errors on the browser side:
And still, no video is shown.
What did you expect?
AV1 Payload supports WebRTC. Video stream is playing correctly.
What happened?
The text was updated successfully, but these errors were encountered: