In the next couple days (pending reviews) I intend to land patches to
enable jitterBufferTarget for all platforms for use with Firefox 115
Nightly.

*Summary:* The jitterBufferTarget attribute allows the application to
specify a target in milliseconds of media for the jitter buffer to hold.
Altering the target value allows applications to control the tradeoff
between playout delay and the risk of running out of audio or video frames
due to network jitter.

*Bug for Feature:* https://bugzilla.mozilla.org/show_bug.cgi?id=1592988

*Standard: *

   -
   
https://w3c.github.io/webrtc-extensions/#rtcrtpreceiver-jitterbuffertarget-attributes
   - https://github.com/w3c/webrtc-extensions/pull/160

*Platform Coverage:* Available on all platforms.

*Preference:* This WebRTC API will be available by default and service
providers who wish to take advantage may do so.

*Other Browsers:* No other browser has implemented jitterBufferTarget.

   -  Blink: Shipped a similar feature playoutDelayHint but it is not spec
   compliant.
   
https://groups.google.com/a/chromium.org/g/blink-dev/c/4W4orKqA3Rs/m/6k0LdB9wCwAJ.
   They have mentioned their intent to align to the jitterBufferTarget spec
   here
   https://github.com/w3c/webrtc-extensions/issues/12#issuecomment-1508067133
   .
   - Webkit: Not implemented

*Web-platform-tests: *WPT tests exist from the implementation of
playoutDelayHint with my changes these will be updated to match
jitterBufferTarget.

   - playoutDelayHint WPT:
   
https://wpt.fyi/results/webrtc-extensions/RTCRtpReceiver-playoutDelayHint.html?label=experimental&label=master&aligned
   - Patch to convert to jitterBufferTarget:
   https://phabricator.services.mozilla.com/D176450

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAGNfvCe72TB1BcnDKTZQNdvBWLAun-orXwfHFgjUHh_SKuGNsA%40mail.gmail.com.

Reply via email to