- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Dec 2017 01:15:52 +0000
- To: public-webrtc-logs@w3.org
I agree that the actual steps outlined in the document do not appear to require asynchronous operation. As I recall, the argument for asynchronous operation mostly related to hardware encoders within media capture devices, under the theory that there might be an interaction between the negotiated codecs and the capabilities of the device hardware encoder. However, my own experience in general is that hardware encoders are backstopped by software encoders, so that if the negotiated codec isn't supported in hardware, software is used instead. This can easily be determined (e.g. you know what codecs the hardware encoder supports), so doesn't require asynchronous operation by itself. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1677#issuecomment-349162597 using your GitHub account
Received on Tuesday, 5 December 2017 01:15:54 UTC