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: Fri, 13 Nov 2015 06:50:40 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-156342143-1447397439-sysbot+gh@w3.org>
We moved away from that problem a bit, but it was not forgotten!
I'm trying to find the use case where this is a practical problem. I 
don't think the `RTCPeerConnection` example is one. First of all, the 
time for the signaling to set up the additional audio track is 
probably much longer than the event propagation on the receiving side.
 Secondly, we have ways to set up an empty track from the start, and 
make that part of both streams on the remote side (and once content 
starts flowing in that track it would do so in both streams of 
`HTMLMediaElement::captureStream()`could be a case, but why can't the 
original stream be used for all consumers (instead of being cloned)? 
Or why can't the second consumer capture from the same element rather 
than cloning the first stream being captured?

GitHub Notif of comment by stefhak
Received on Friday, 13 November 2015 06:50:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:28 UTC