- From: Miguel Casas-Sanchez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Dec 2016 18:49:48 +0000
- To: public-media-capture-logs@w3.org
The first repeating task will flip the value of `ignoreMutedMedia` from true to false. According to the current reading of the spec, MR will either ignore a muted track (`ignoreMutedMedia` == true) or insert blanks in the recording at the speed of the source (`ignoreMutedMedia` == false). But, IIRC: `MediaStreamTrack.muted` is a read-only attribute that doesn't relate to `enabled` (*), so the second line doesn't affect the `muted` value, and so renders the behaviour of the lines @jan-ivar posted totally dependent on the behaviour of `stream` :smile: (*) In [Chromium](https://cs.chromium.org/chromium/src/content/renderer/media/video_track_adapter.cc?sq=package:chromium&dr=CSs&rcl=1481717748&l=450), video `muted` state is updated by monitoring the amount of frames passing versus the frame rate. https://w3c.github.io/mediacapture-record/MediaRecorder.html#dom-mediarecorder-ignoremutedmedia -- GitHub Notification of comment by miguelao Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/99#issuecomment-267120688 using your GitHub account
Received on Wednesday, 14 December 2016 18:49:54 UTC