Re: Track cloning behavior of MediaStream() constructor and addTrack()

On 2013-03-19 09:48, Harald Alvestrand wrote:
> On 03/19/2013 09:05 AM, Adam Bergkvist wrote:
>> On 2013-03-19 07:27, Harald Alvestrand wrote:
>>> An alternate method of straightening out the API would be to rename the
>>> addTrack operator to addCopyOfTrack  or
>>> addTrackWithSameSourceAsTheArgument.
>>>
>>> I think the ability to control tracks-in-streams independently is more
>>> important than the linkages you mention, but agree that the API name
>>> doesn't fit with what the operation does.
>>>
>>
>> I'm not arguing to remove that functionality, just that it would be
>> more intuitive, IMO, to clone the track first and then add it to the
>> new stream if you wanted a independent instance to control.
>>
>
> and I'm arguing that having *dependent* instance control (that is,
> muting a track in one stream mutes it in all other streams too) is
> behaviour I don't want....

I think that particular issue, with enabling/disable, is application 
specific.

/Adam

Received on Tuesday, 19 March 2013 09:04:08 UTC