- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Jun 2020 21:01:43 +0000
- To: public-webrtc-logs@w3.org
The reason the Chrome bug was an issue is that the process on Android to figure out whether or not a H.264 encoder is available takes time. It will return the same answer every time on the same hardware, but until WebRTC asks about it, it is not going to be known to the underlying system. So we have a short interval in which the reply to "do you support H.264 encode" is "I don't know yet". Depending on the answer resolving one way or the other is not a Good Thing. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2539#issuecomment-645009684 using your GitHub account
Received on Tuesday, 16 June 2020 21:01:45 UTC