[Bug 25361] Media Capture and Streams spec should explicitly specify that recvonly streams / tracks should be considered as muted.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25361

--- Comment #3 from Kiran <kiran.guduru@samsung.com> ---
I agree with Adam to give the example of a future "MediaStream source".

Re-reading the spec, it seems "disabled" should be replaced with "recvonly",
instead of extending, as explained below.

A disabled track outputs blackness / silence.
Since in this case, remote track is disabled, it will any how send blackness /
silence to remote end (to its consumer). So receiving end will receive
blackness / silence from its (remote) source.

But from [1], A MediaStreamTrack is muted when the source is temporarily unable
to provide the track with data.

If the track is "recvonly", then remote peer will not send any data (even
blackness / silence), will be more apt for that example?

[1] http://www.w3.org/TR/mediacapture-streams/#life-cycle-and-media-flow

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Received on Thursday, 24 April 2014 06:16:12 UTC