Re: [webrtc-extensions] How does a developer decide on a value for `playoutDelay` ? (#46)

I think these are valid concerns. There's also a precedent here in [latencyHint]( Following that model we could imagine:
enum RTCRtpReceiverLatencyCategory {

partial interface RTCRtpReceiver {
  attribute (RTCRtpReceiverLatencyCategory or double) playoutDelay;
This should be more web compatible, and remove the onus on web developers to discover the [minimum allowed delay]( of each browser and work around it with tables of different values for well-known browsers.

Happy to bikeshed enum names based on use-cases. This should also hopefully produce a healthy discussion of what the default value should be (presumably web conferencing is `"interactive"` not `"balanced"`, right?)

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at using your GitHub account

Received on Friday, 17 July 2020 18:55:01 UTC