WebRTC M84 Release Notes
WebRTC M84 branch (cut at r31262)
WebRTC M84, currently available in Chrome's beta channel, contains 4 new features and over 20 bug fixes, enhancements and stability/performance improvements. As with previous releases, we encourage all developers to run versions of Chrome on the Canary, Dev, and Beta channels frequently and quickly report any issues found. Please take a look at this page, for some pointers on how to file a good bug report. The help we have received has been invaluable!
The Chrome release schedule can be found here.
When simulcast is used and multiple RTP streams are produced by the same RTCRtpSender, getStats() now produces one “outbound-rtp” stats object per RTP stream which can be identified by their ssrc. This means that counters such as packets and frame rate are now split per layer rather than aggregated into a single “outbound-rtp” object. This only affects the spec-compliant (promise-based) getStats() API; the legacy (callback-based) getStats() API will continue to report aggregate values. See PSA.
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CACxSdkEcor77Jetp9FOanDDnFf92VT2vDskN%2BT62B1V7S2DaXw%40mail.gmail.com.