- From: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Jul 2020 10:37:57 +0000
- To: public-webrtc-logs@w3.org
jitter should never be less than min/hint values, that would be quite safe to implement. Regarding max, if only plaoutDelayHint is defined, then I agree that neteq would have trouble deciding whats the best behaviour for the app. That's why i think that adding a max value will allow the apo to set the desired behaviour without neteq having to guess it. El vie., 24 jul. 2020 12:16, henbos <notifications@github.com> escribió: > Yeah I definitely think the implementation needs to apply the playoutDelay > faster. Maybe it is quicker at speeding things up again than slowing things > down? Otherwise it would be quite "dangerous" when you become interactive > again > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webrtc-extensions/issues/46#issuecomment-663469281>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAIFN46YIHWY5BWNYK2RSKTR5FNO3ANCNFSM4O6MJYMQ> > . > -- GitHub Notification of comment by murillo128 Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/46#issuecomment-663477081 using your GitHub account
Received on Friday, 24 July 2020 10:38:00 UTC