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

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

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Fri, 13 Nov 2015 19:36:20 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-156536828-1447443379-sysbot+gh@w3.org>
I think I agree as well, mostly because I can't come up with how it 
would work otherwise. The only reason to clone a stream in the first 
place is wanting control over what's in and what's out, which I can't 
reconcile with automatic track addition (If I clone a 
DOMElement-captured stream to remove, say, the audio track, do I get 
new audio tracks or not when the source loops?).

There really are two kinds of streams here: hosted vs plain, and it 
sounds like we're agreeing that cloning a hosted stream should give 
you a plain stream, not a hosted stream.

We should remove `stream.clone()` then, to avoid confusion.

`var clone = new MediaStream(stream);` should suffice.

-- 
GitHub Notif of comment by jan-ivar
See 
https://github.com/w3c/mediacapture-main/issues/271#issuecomment-156536828
Received on Friday, 13 November 2015 19:36:28 UTC

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