W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > March 2019

Re: [webrtc-pc] Add setTargetJitterBufferDelay method to RTCRtpReceiver (#2139)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Mon, 25 Mar 2019 21:06:43 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-476377574-1553548002-sysbot+gh@w3.org>
> ("not less than this" and "no more than this", with "preference for something like this"

How would `latency: {min: 0.5, ideal: 0.7, max: 0.9}` differ from `latency: 0.7`?

How would it differ from `latency: {min: 0.2, ideal: 0.7, max: 1.2}`?

> Having a single number attached to a receiver destroys all of this flexibility in implementation.

"flexibility in implementation" != standard. We'd have to specify this.

I also commented in https://github.com/w3c/webrtc-pc/pull/2138#issuecomment-475774761 but we should move here.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2139#issuecomment-476377574 using your GitHub account
Received on Monday, 25 March 2019 21:06:44 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:46 UTC