- From: chcunningham via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Oct 2021 17:32:19 +0000
- To: public-webrtc-logs@w3.org
>> getCapabilities is synchronous while codec enumeration is usually asynchronous, see discussion about getCapabilities results changing after the first createOffer/createAnswer call > > Worth highlighting. As we initially implemented SVC hw encode for WebCodecs, we (@Djuffin) were reminded that querying the platform encoder capabilities at browser startup is too slow. Async solves the issue. WebRTC may not feel this pain as long as it always has software fallback w/ capabilities matching/exceeding that of the hardware path. Maybe that's a safe assumption? @henbos to comment on the above. I recall that you earlier had issue w/ the sync getCapabilities() API... so maybe its already true that we don't always have equally sw fallback? Or maybe I've overlooked some subtlety. -- GitHub Notification of comment by chcunningham Please view or discuss this issue at https://github.com/w3c/webrtc-svc/issues/49#issuecomment-954054998 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 October 2021 17:32:20 UTC