W3C home > Mailing lists > Public > public-orca@w3.org > February 2014

Re: A Big Proposal: A way to control quality/resolution/framreate/simulcast/layering with RtpSender

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 19 Feb 2014 09:49:45 -0800
Message-ID: <CABkgnnUPyqh2XPFG5yWkDZ7uejuyFQw=Q2AGj=0p2OZrk5qt-w@mail.gmail.com>
To: Peter Thatcher <pthatcher@google.com>
Cc: "public-orca@w3.org" <public-orca@w3.org>
On 18 February 2014 17:17, Peter Thatcher <pthatcher@google.com> wrote:
> As for priority, your "add bits proportionally" is exactly what I was
> thinking, but, as you pointed out, it's "roughly proportionally", since you
> can quite split up bit allocation that finely.  Whether a browser does it in
> a simple fashion or with more fancy "curves" may simply be browser, codec,
> and BWE dependent.  The JS gives the policy, and the browser does its best.

I think that unless there is some amount of determinism here, we will
leave applications doing funny heuristic things, browser sniffing and
the like.  I understand that it might be hard to specify something,
but I'd like something a little more deterministic than what you have
specified.
Received on Wednesday, 19 February 2014 17:50:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:39:24 UTC