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

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

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Thu, 29 Jun 2017 17:34:39 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-312037997-1498757678-sysbot+gh@w3.org>
I won't object since getStats is a kind of workaround here.

That said, I don't think we should rely too much on the web engine "best effort" model here.
Web apps can usually take actions that have bigger impacts on performance and usability than what a web engine can do. Changing the resolution of a video track at the source is better than dropping the resolution or dropping frames later in the chain. If no encoder slot is available, the web application may decide to drop a low priority track.

Also, there are on-going discussions to expose things like memory pressure or cpu overuse to web pages. WebRTC applications could benefit from that, especially if WebRTC engines could provide some more feedback. getStats is the current answer but there might be room for further improvement.


-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1323#issuecomment-312037997 using your GitHub account
Received on Thursday, 29 June 2017 17:34:46 UTC

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