W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2017

[webrtc-pc] No way to associate streams using addTransceiver()

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Wed, 05 Jul 2017 21:01:55 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-240775119-1499288514-sysbot+gh@w3.org>
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-pc:

== No way to associate streams using addTransceiver() ==
As I mention in https://github.com/w3c/webrtc-pc/issues/1237#issuecomment-313210542, JSEP says:
 * *"For each MediaStream that was associated with the transceiver when it was created via addTrack or addTransceiver, an "a=msid" line, as specified in [I-D.ietf-mmusic-msid]"*

But there's no way to associate a MediaStream with a transceiver using `addTransceiver`. Omission or bug in JSEP?

E.g. the [warm-up example](http://w3c.github.io/webrtc-pc/#advanced-peer-to-peer-example-with-warm-up) and [simulcast example](http://w3c.github.io/webrtc-pc/#simulcast-example) in the spec are only possible with zero stream associations.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1452 using your GitHub account
Received on Wednesday, 5 July 2017 21:02:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:40 UTC