W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > November 2015

Re: [mediacapture-main] Track changes on cloned streams

From: stefan hakansson via GitHub <sysbot+gh@w3.org>
Date: Thu, 12 Nov 2015 09:15:54 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-156041073-1447319751-sysbot+gh@w3.org>
I think the mediacapture-fromelement document specifies tracks coming 
and going out pretty well, there will be removeTrack and addTrack 
events fired on the MediaStream, and a media element videoTrack or 
audioTrack that goes a way and then comes back will be (when coming 
back) be represented by a new MediaStreamTrack (as ended MSTs can't 
come back to life).

As for the PeerConnection example, the sending side app controls what 
will happen on the remote side via the streams argument to addTrack. 
The only uncertain thing I can see in your example is the order the 
addTrack and removeTrack events should fire on the remote MediaStream.

So that deals with @alvestrand #2 above. For @alvestrand #1 I think 
Harald is correct.

-- 
GitHub Notif of comment by stefhak
See 
https://github.com/w3c/mediacapture-main/issues/271#issuecomment-156041073
Received on Thursday, 12 November 2015 09:15:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 24 October 2017 05:05:46 UTC