-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
WebRTC AV1 streaming failed, no valid AV1 payload type found. #2760
Comments
You should have failed to push the stream, it didn't go up successfully, it's not a playback failure.
|
Before and after exchanging SDP on the client side, you can solve it by using
It feels very strange that this problem only appeared after upgrading Chrome.
|
https://bugs.chromium.org/p/webrtc/issues/detail?id=13166
|
@jocover 👍 Can you conveniently submit a PR?
|
@winlinvip @jocover I submitted a fix PR #2784, please help take a look. Make sure to maintain the markdown structure.
|
Fixed in SRS 4 |
WebRTC AV1 streaming, playback failed, using SRS returned 400, checking SDP found that AV1X has changed to
a=rtpmap:35 AV1/90000
.Using a self-built server (Linux on a local network).
chrome:
Google Chrome | 96.0.4664.55 (Official Build) (x86_64)
Operating System | macOS Version 12.0.1 (Build 21A559)
JavaScript | V8 9.6.180.12
User Agent | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36
SRS version:
SRS/5.0.19(Leo)
SRS log:
Replay
How to replay bug?
1. Visit
https://ubuntu.pve/players/rtc_publisher.html?autostart=false
webrtc://ubuntu.pve/live/aabbcc?codec=av1
1. The player is destroyed, and the console prints
Got answer: {code: 400}
.推流端sdp (Streaming end SDP)
I don't know why
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: