Re: Cloning and sharing of MediaStreamTracks - worth it?

On 05/08/2013 10:03 AM, Stefan Håkansson LK wrote:
> On 2013-05-08 09:38, Robert O'Callahan wrote:
>> If we clone a MediaStreamTrack and insert that into a different
>> MediaStream, how are the "enabled" and "muted" states of the clone
>> related to the original? Can the clone be enabled while the original is
>> disabled?
>
> "muted" relates to the source, and can't be controlled by the 
> application, so all tracks representing the same source should have 
> the same mute state.
>
> Regarding "enabled", I think there are two questions here:
>
> 1. When doing track.clone();, does the new track inherit the "enabled" 
> state of the track it is cloned from, or does it start "fresh"? In the 
> Ed's draft this is not outlined, but I think it must be defined. 
> Presumably it should be described under the "clone" section here: 
> http://dev.w3.org/2011/webrtc/editor/getusermedia.html#methods-1
>
> But this is also related to the Audio/VideoStreamTrack constructors 
> and getUserMedia: presumably any tracks delivered by those operations 
> should be "enabled", but it is not defined as far as I can see.

Agree on both points. These are "obvious choices", let's write them down.

>
> 2. Can the different tracks representing the same source independently 
> switch between enabled/disabled? My answer is: yes, so the clone can 
> be enabled while the original is disabled (or the other way around).

That's really the point of cloning.

Received on Wednesday, 8 May 2013 10:07:40 UTC