- From: Jim Jin via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Oct 2020 15:32:43 +0000
- To: public-webrtc-logs@w3.org
> This calls setCodecPreferences with [vp9, vp8] > But since the remote SDP indicated VP8 first the answering peerconnection will send VP8. > Restricting setCodecPreferences to VP9 does work but how does one figure out the remote understands VP9 from the offer (without parsing SDP :-))? In my case, both the caller and the callee are wrote by me. So, I call setCodecPreferences with [vp9, vp8] on both side. I hope it could use VP9. Actually, my real requirements is that, the advanced codec (`VP9, profile-id=2` here, since `av1` is not available yet) should always be selected whenever possible. But it seems that Chrome always takes VP8 as precedence. Firefox does the same until I change the flag `media.peerconnection.video.vp9_preferred` to true. I insist that Chrome should take VP9 as precedence. There is no reason to stick to VP8 when the more advanced codec is available. Lastly, WebRTC is such a fantastic technique that I predict it will be more and more popular and eventually dominate the internet video & audio field. -- GitHub Notification of comment by jim-king-2000 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2592#issuecomment-719623424 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 30 October 2020 15:32:45 UTC