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

Re: API or spec to limit a certain sending track

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Fri, 4 Aug 2017 11:10:25 +0200
Message-ID: <CALiegfmg0QUjGVSSEX7tKpVSinsmdNVPJMZjLNyYMxpTYx4G4w@mail.gmail.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Fri, Aug 4, 2017 at 11:01 AM, Stefan Håkansson LK
<stefan.lk.hakansson@ericsson.com> wrote:

> I fully understand the pain trying to do magic with a toolbox that is
> not complete and with defects on some of the tools available - but I
> guess that is what you can expect at this stage!

Yep. For now I'll go with an approach that handles separate transports
(different WebRTC PeerConnections or different ORTC
Ice+DtlsTransports) for sending video tracks for which I need
different bitrate limits, so I should be able to limit a specific
video track via REMB (generated by the server) or even using b=AS.



-- 
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Friday, 4 August 2017 09:11:09 UTC

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