- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Apr 2017 22:13:05 +0000
- To: public-media-capture-logs@w3.org
youennf has just created a new issue for https://github.com/w3c/mediacapture-main: == Algorithm to mute/disable tracks is unclear == The spec is not really clear about how to mute a track. Let 's take the example of disabling a a gum video track. Should it: 1. continue sending black frames at the expected frame rate? 2. Should it send a black frame and stop sending after that? If 2, should the last black frame be sent immediately or follow the frame rate? Note that this might be observable by a web application using the stats API through the framesEncoded value. Looking quickly at https://webrtc.github.io/samples/src/content/peerconnection/bandwidth/, it seems as if Chrome is doing 1 and Firefox is doing 2. 2 has obviously some efficiency advantages. Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/441 using your GitHub account
Received on Wednesday, 5 April 2017 22:13:12 UTC