W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2020

[webrtc-extensions] Allow more control over playoutDelay behavior (#28)

From: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
Date: Tue, 11 Feb 2020 09:54:05 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-563087017-1581414844-sysbot+gh@w3.org>
murillo128 has just created a new issue for https://github.com/w3c/webrtc-extensions:

== Allow more control over playoutDelay behavior ==
After have tried to make the current `playoutDelay` extension to work in chrome, I found several usability issues that  prevent it from being usable (at least from my point of view and others on the discuss-webrtc mailing list).

I think that it would be very interesting to allow more control on how the `playoutDelay` is applied by the browser.  IMHO this would require to add to new attributes:

- `playoutDelayMin` which specifies the minimum value allowed for the actual playout delay applied by the browser. In case that the current delay is lower than the min one, the browser must insert silence or no audio/video be played until the min delay is reached.
- `playoutDelayMax` which specifies the maximum value allowed for the the actual playout delay applied by the browser. In case that the current delay is bigger than the maximum value, the browser will drop frames until the max playout delay is reached.

When the playout delay is between the min/max values, the browser should accelerate/decelerate the media playout until the `playoutDelay` is reached. 

Each browser would be able to specify a different range for the allowed min/max values and the default values.

Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/28 using your GitHub account
Received on Tuesday, 11 February 2020 09:54:07 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 11 February 2020 09:54:08 UTC