W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2013

Re: Why people munge SDP

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Fri, 18 Oct 2013 14:58:51 +1100
Message-ID: <CAHp8n2k465q8eY6PoDYhbA5P7vhQBR1fqSi=+BRJgVoCvquVYg@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Cc: "<public-webrtc@w3.org>" <public-webrtc@w3.org>
Hi everyone,

sorry for picking up an old thread, but I'd like to point out an
awesome interface for SDP munging:
https://github.com/clux/sdp-transform .
I wished browsers would expose SDP in the kind of JSON that this
library provides!
It even has a pretty formal grammar and parser.
This should be an inspiration.

Cheers,
Silvia.


On Wed, Jul 24, 2013 at 3:17 PM, Silvia Pfeiffer
<silviapfeiffer1@gmail.com> wrote:
> On Wed, Jul 24, 2013 at 2:01 PM, Cullen Jennings (fluffy)
> <fluffy@cisco.com> wrote:
>>
>> The next issues that got mentioned was setting bandwidth. I think we should add a constraint, or some API, to be able to do this. It is a bit more complex to add because we likely need to set it on a track not a stream.
>
>
> Yes, I'd really like an API for controlling the bandwidth use better.
>
> I've seen in Chrome that a PeerConnection ramps up to 2Mbps and then
> tries to stay there.
>
> When I have multiple video tracks going over the same PeerConnection,
> they together have to share the 2Mbps, which usually ends up in having
> one video track continue to be active and the others drop in and out
> all the time. That is not sustainable and we should provide bandwidth
> limitations on a per track basis.
>
> Also, when I have a video at 640x480 and another one at 1080x720, they
> both get limited to 2Mbps independently. Even if I know that I have
> hundreds of Mbits available, I can't currently tell Chrome to give the
> 1080x720 video 10Mbps, while the 640x480 can continue with 2Mbps.
>
> HTH,
> Silvia.
Received on Friday, 18 October 2013 03:59:38 UTC

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