WebRTC 112 Release Notes

1,676 views
Skip to first unread message

Harald Alvestrand

unread,
Mar 15, 2023, 9:35:26 AM3/15/23
to discuss...@googlegroups.com

WebRTC M112 is going to be released as part of Chrome M111 , currently planned for release on  April 4th 2023.


Three PSAs were published that may require action from developers:


In addition to this, please note that the legacy stream statistics are disabled by default in M112. If you still rely on them you need to register for the corresponding deprecation trial.


In terms of features the highlights for this release is the reordering of the tabs in the getDisplayMedia picker which improves privacy described in this blog post and which is now enabled by default in non-Chrome browsers as well.


The following issues were marked as fixed or verified and had at least one commit in M112 (build, test and trivial code changes are not included):


Issue

Summary

Component

chromium:1414370

Remove unused WebRtc encoded frame GetAdditionalData() methods

Blink>WebRTC

webrtc:11404

Add AV1 encoder and decoder wrapper behind flags

Video

webrtc:11803

AEC3: Misaligned render buffer when external delay estimates and initial capture calls

Audio

webrtc:12397

Audio RTP timestamps does not increment when RTCRtpEncodingParameters.active is set to false.

Audio

chromium:1410691

STATUS_ILLEGAL_INSTRUCTION on VIA Eden X4 C4450 CPU

Blink>WebRTC>Audio,
Blink>WebRTC

webrtc:13279

Audio mlines shouldn't advertise rid/rrid header extension support

PeerConnection

webrtc:14817

Video receive streams may be re-created when SSRCs are unsignaled causing GetSources() history to be cleared

Video

webrtc:14894

Update DXGI capturer to re-initialize when a monitor's DPI changes

DesktopCapture

chromium:1411614

Contributing sources are never set on received RTCEncodedVideoFrame.getMetadata()

Blink>WebRTC

chromium:1406331

VP8 encoder scales threads quickly, make max threads configurable

Blink>WebRTC,
Blink>Media>Video

webrtc:11031

Retransmission can fail when MID has been negotiated [Unified Plan]

Network>RTP

webrtc:9734

Potential bad performance with simulcast screensharing

Video

webrtc:4690

VoE API Refactoring Tracking Bug

Audio

webrtc:14885

Add test coverage for simulcast where media flows

Video

webrtc:14872

Treat Unrecognized Data Channel Protocols as Unsupported Media

PeerConnection,
SpecConformance

webrtc:14875

Remove webrtc::VideoStreamDecoderInterface

Cleanup,Video

webrtc:14910

Implement PeerConfigurer audio encoder/decoder factory setters

Tools

chromium:1414370

Remove unused WebRtc encoded frame GetAdditionalData() methods

Blink>WebRTC

chromium:1410129

media::AudioProcessor should not push the reference into WebRTC if there is no echo cancellation

Blink>WebRTC>Audio

chromium:1375217

tracking bug for webrtc-internals ui/ux improvements

Blink>WebRTC>Tools

chromium:1417654

Collect UKM tracking {preferCurrentTab: true}

Blink>GetDisplayMedia

chromium:1358278

Media Picker Reordering - Tracking Bug

Blink>GetDisplayMedia

chromium:1406874

Echo cancellation of WebAudio playing to a non-default output device

Blink>WebAudio,
Blink>GetUserMedia

chromium:1411703

WebRTC Insertable Streams: add RTP sequence number to incoming audio frames

Blink>WebRTC




For the full list of commits please refer to the git log between this branch and the previous branch.


We strongly recommend WebRTC developers to fully test their services in Chrome Beta to ensure stability for end-users.

 

The Chrome release schedule can be found here.


These release notes were prepared by Philipp Hancke.


Philipp Hancke

unread,
Mar 16, 2023, 4:13:18 AM3/16/23
to discuss...@googlegroups.com
part of Chrome M112 obviously

--

---
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/CAOqqYVG1a6JAF5hdm1DJH%3De-fGbuH2pSeLL%2BgXNPRvk9%3DTOs_w%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages