- From: Sergey Silkin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 08:56:29 +0000
- To: public-webrtc-logs@w3.org
There is a logic in WebRTC which changes encoder on failure (create, init or encode). For example: https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/video/video_stream_encoder.cc;drc=acabb3641b924dd0c5198a16883ae8326f35487e;l=1396 It removes the failed codec from the list of negotiated ones: https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/media/engine/webrtc_video_engine.cc;l=891-892;drc=2df668b7cbf6c1d0766b6ee0ae8147adc8830f2e;bpv=1;bpt=1. And forces usage of the next negotiated codec by that. How do solve missing encoding parameters for this case? Can we make it possible providing encoding parameters for multiple codecs? -- GitHub Notification of comment by ssilkin Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/126#issuecomment-1333432610 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 December 2022 08:56:31 UTC