W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > April 2017

Re: [mediacapture-main] Algorithm to mute/disable tracks is unclear

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Wed, 12 Apr 2017 18:05:20 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-293660626-1492020318-sysbot+gh@w3.org>
Update: In Firefox Nightly, [where we support `framesEncoded` now](https://jsfiddle.net/tzf4u0ak/), the behavior is slightly different. When I mute, the frame rate goes from 30 fps to 1fps, and we're sending 1 packet/second. Frame rate wasn't really observable in mediaRecorder.

The spec seems to go to great lengths to grant UAs final say in what's actually produced, including externalizing requirements into constraints, so I'm not surprised by the leeway here. For instance, a browser that wanted to introduce a "privacy screen" might overload mute with a user-defined image.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/441#issuecomment-293660626 using your GitHub account
Received on Wednesday, 12 April 2017 18:05:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:32 UTC