W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2017

Re: [webrtc-pc] Handling of encoding/decoding errors

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Fri, 09 Jun 2017 05:25:01 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-307298450-1496985899-sysbot+gh@w3.org>
With respect to the resource model Section 4.3.2 says: 

"If a system has limited resources (e.g. a finite number of decoders), createOffer needs to return an offer that reflects the current state of the system, so that setLocalDescription will succeed when it attempts to acquire those resources. The session descriptions must remain usable by setLocalDescription without causing an error until at least the end of the fulfillment callback of the returned promise. "

I think your question relates to what happens once media is flowing and the situation changes (e.g. CPU or encoder/decoder resources become scarce).  The model is "best efforts" where the encoder/decoder will do the best it can based on potential guidance (e.. for the encoder, degradationPreference.).  Rather than resulting in an error, performance (which can be monitored via WebRTC-stats) will degrade. The application can monitor this and adjust parameters to try to improve the situation.

-- 
GitHub Notification of comment by aboba
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1323#issuecomment-307298450 using your GitHub account
Received on Friday, 9 June 2017 05:25:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:44 UTC