W3C home > Mailing lists > Public > public-media-capture@w3.org > March 2013

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

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 19 Mar 2013 09:48:35 +0100
Message-ID: <51482663.5000101@alvestrand.no>
To: public-media-capture@w3.org
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....
Received on Tuesday, 19 March 2013 08:49:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:15 UTC