W3C home > Mailing lists > Public > public-webrtc@w3.org > December 2014

Doohickey vs. MediaStream confusion

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Tue, 2 Dec 2014 08:54:38 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1D0ED63E@ESESSMB209.ericsson.se>

reading the doohickey branch of webrtc-pc [1] there is one piece that 
confuses me a bit.

In section 4.3.1 it is said (probably this part should be moved to 
somewhere in section 5 "RTP media API") that if no MediaStream was given 
as argument to the corresponding RTPSender, the RTPReceiver should 
create one.

Is that really the way we want it to work? I could imagine a situation 
where several tracks are sent over, with the intention to assemble them 
together in a specific way to a few/couple of MediaStreams at the 
receiving end, and then several MediaStreams are created for no use.

And it does not help the legacy (one audio and one video track 
communication) case either since two MediaStreams are created, but you 
want one (for synced display using a video element).

Would it not make more sense to say that for situations when no 
MediaStream is given as argument to RTPSender the corresponding ontrack 
event would include one RTPReceiver and a MediaStreamTrack, but no 


[1] https://github.com/w3c/webrtc-pc/tree/doohickey
Received on Tuesday, 2 December 2014 08:55:07 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:42 UTC