PSA: Chrome M45 WebRTC Release Notes

Skip to first unread message

Christoffer Jansson

Aug 24, 2015, 2:29:47 PM8/24/15
to WebRTC-discuss



We are excited to announce that the audio output device selection JavaScript API has been implemented behind a flag. Try it out using the following the demo pages, just make sure to follow the in-page instructions on how to enable it:

Our new delay-agnostic echo canceller is on for a majority of users on Windows, Linux and ChromeOS. Mac OS X will be ramping up later this quarter but is still behind a flag. This new AEC should result in fewer users hearing echo from the remote side. Do help us test it, and please let us know if you encounter a scenario where it doesn't work well.

A first initial step has been taking in assisting users that want to limit the IP addresses used by WebRTC, through the release of an official Chrome extension. More details in the discuss-webrtc PSA.

We encourage all developers to run dev versions frequently and quickly report any issues found. The help we have received has been invaluable! On to dev and canary everyone!

For some pointers on how to file a good bug report, please take a look at this page.



  • Issue 511082: Put navigator.mediaDevices behind a flag again.

  • Issue 504346: Hangout services extension preferences not updated

  • Issue 501120: Crash after getUserMedia()

  • Issue 280726: PeerConnection's RTP-based Data Channel allows bypassing rate limiter via SDP mangling, allowing for sending data with no congestion control.

  • Issue 447431: WebRTC does not respect packet boundaries with DTLS.

  • Issue 506206: Screenshare notification horizontal dimension is to small to display the text properly

  • Issue 507994: Using audio SourceID constraint with getUserMedia() causes video to fail.

  • Issue 1675: If application is send only there shouldn't be a thread waiting for decode

  • Issue 4042: Crash in SrtpSession::~SrtpSession() if srtp_create fails

  • Issue 49989004: Ensure mediasession generated offers with RTX contain an RTX ssrc for each video ssrc.

  • Issue 45439004: Add support for iOS http proxy detection.

  • Issue 4366: Adapted frames have wrong width and height and are cropped

  • Issue 4316: googTrack stats reports don't set timestamp

  • Issue 4617: RTX-TIME parameter is disappeared

  • Issue 4717: WebRTC ISAC audio codec fails on ARM7

  • Issue 4722: Stats for decoded framerate is always zero if frame is backed by a texture

  • Issue 4724: Candidate could be resurrected with incorrect candidate type

  • Issue 4778: Initial bitrate probing doesn't work with combined audio/video BWE.

  • Issue 4651: Change name of ReportedDelay

Pavel Baykov

Dec 18, 2015, 4:20:05 PM12/18/15
to discuss-webrtc
new WebRTC code have DA-AEC (delay agnostic), will it work for Android?

понедельник, 24 августа 2015 г., 21:29:47 UTC+3 пользователь Christoffer Jansson написал:

Christoffer Jansson

Dec 21, 2015, 3:16:54 AM12/21/15
to discuss-webrtc,

I think you posted this in the wrong post (I assume you mean M48). I do not think DA-AEC is enabled yet on Android, +Tina le Grand could you confirm?



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
To view this discussion on the web visit
For more options, visit
Reply all
Reply to author
0 new messages