- From: Sun Shin via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Mar 2023 15:36:32 +0000
- To: public-webrtc-logs@w3.org
> However, because one of the reasons that your decoder could fallback is that the HW is not available, if another website or application acquired the same HW before you did, this could result in decoderFallback when you try to instantiate your decoder (depending on HW limitations in number of concurrent instances). @henbos Thank you for the feedback, Based on my proposal, decoder fallback only triggerred when the decoder starts with hardware acceleration. Unless the session starts with hardware decoding, the decoder fallback will be not triggered. -- GitHub Notification of comment by xingri Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/730#issuecomment-1463978912 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 March 2023 15:36:34 UTC