Chrome WebRTC M35 Release Notes.

1918 views
Skip to first unread message

Vikas Marwaha

unread,
May 30, 2014, 8:01:53 PM5/30/14
to discuss...@googlegroups.com
Hi,

Please find below WebRTC Release notes for Chrome M35. Below is the list of major changes:

Features:-
  • Issue 960 :- Implemented MediaStreamTrack readyState. The readyState should show the current mediaTrack state. 
  • Issue 1577 :- Implemented CPU overload control in WebRTC. WebRTC will back down on it's video encode resolution if CPU overload is detected. 
  • Issue 2774 :- SDES is now disabled by default in WebRTC when DTLS is enabled. You can enable SDES by setting DTLSSRTPKeyAgreement constraint to false. But this will be removed in future versions of chrome. 
  • Issue 3071 :- Added a method to WindowCapturer to bring captured window to the front. When doing screen sharing, it would bring the shared window to the front.
  • Issue 294145:-  Decoupled MediaStream from MediaStreamTrack. Earlier MediaStreamTrack belonged to exactly one MediaStream now it can belong to zero to many MediaStreams. Also, the clone() method for MediaStream and MediaStreamTrack has been added.
  • Issue 316731:- Added a HIDE button to the desktop capture notification bar. The new button is used to minimize the notification to the task bar.
  • Issue 351437:- Limited DesktopCapture API to secure scheme (HTTPS) unless -allow-http-screen-capture is enabled.
  • Issue 341729:- The  notification bar from DesktopCapture API, now shows both helper extension name and the page security origin, earlier it used to only show the page security origin.
  • Issue 352619:- Render a black frame if a MediaStream track is disabled or the source ends.
  • rev 260052 :- Chrome will use IPv6 temporary address when available. This feature only supported on Windows and OSX. Temporary addresses provides better privacy for users as they are changed frequently.
  •  Bandwidth estimation mechanism now generates timestamps in the browser process instead of the renderer process. This improves the accuracy of BWE significantly, especially under CPU load.
  • Adaptive jitter buffer (NetEQ) has been rewritten for improved maintainability and better performance. In particular, decoding Opus stereo should use noticeably less CPU.
Bugs:-
  • Issue 2789:- Fixed problem where, Chrome screen sharing message visible to webRTC peers. Currently only fixed for Mac.
  • Issue 2841 :-  Fixed problem with chooseDesktopMedia picker OK/cancel order on Mac.
  • Issue 2842 :- Changed the ChooseDesktopMedia picker OK button label to "Share".
  • Issue 2937 :- Fixed problem with Chrome failing if telephone-event was at the top in the sdp. 
  • Issue 2941 :- Fixed problem with Chrome failing to parse sdp containing G.729 codec without any rtpmap lines.
  • Issue 344718 :- Fixed problem where video frame was letter boxed when the window was resized during window capturing.
  • Issue 339953 :- Fixed a problem with screen casting in Linux, where re-sizing a window was causing the windows contents to not update.
  • Issue 327724:- Fixed the problem, where GetUserMedia was not failing, if audio and video is requested but there is no webcam.
  • Issue 306285:- Fixed problem in TURN SSL certificate handling with domain name.
  • Issue 344874:- Updated GetUserMedia to match the spec. Both the success and fail callbacks are mandatory, failure to provide any will throw an error now.
Chrome://webrtc-internals:-
  • Issue 347337:Fixed webrtc-internals to properly handle negative values in graphs. Previously the graph drawing code assumed that the minimum value displayed is 0. Now its extended to the actual value range, including negative values.

/Vikas

Айдар Габдуллин

unread,
May 31, 2014, 4:27:17 PM5/31/14
to discuss...@googlegroups.com
Nice!

streamencode

unread,
Jun 3, 2014, 12:22:30 PM6/3/14
to discuss...@googlegroups.com
This issue, that constraint will be removed in Chrome 36 stable?

Justin Uberti

unread,
Jun 4, 2014, 2:18:22 AM6/4/14
to discuss...@googlegroups.com
We don't have a specific timeline to announce right now. But it will not be until at least Chrome 38.

yayay

unread,
Jun 6, 2014, 8:17:10 PM6/6/14
to discuss...@googlegroups.com
Hi Vikas,

For the issue Issue 294145. I noticed this API is not available in the libjingle.
Will the API add to libjingle?

Vikas

unread,
Jun 9, 2014, 8:07:44 PM6/9/14
to discuss...@googlegroups.com
Hi,

 There should be an API available in native code to add same track to a different mediastream. Let us know if you have issues with the api.

/Vikas

yayay

unread,
Jun 10, 2014, 1:49:46 PM6/10/14
to discuss...@googlegroups.com

Vikas

unread,
Jun 10, 2014, 8:00:02 PM6/10/14
to discuss...@googlegroups.com
What API's are you exactly looking for, there is addTrack API in the mediastream.h.

/Vikas

yayay

unread,
Jun 10, 2014, 8:24:52 PM6/10/14
to discuss...@googlegroups.com
I'm looking for clone() API.

Vikas

unread,
Jun 11, 2014, 2:55:31 PM6/11/14
to discuss...@googlegroups.com
Yes, it seems like we don't have clone() API in native layer. You can file a request in the webrtc tracker.

yayay

unread,
Jun 11, 2014, 5:27:53 PM6/11/14
to discuss...@googlegroups.com

Developer

unread,
Jul 22, 2014, 8:03:51 AM7/22/14
to discuss...@googlegroups.com
On Android chrome browser (version 36) there is no flag to enable-screen-share. and i m not able to share screen from android to desktop. Any suggestions. 
Reply all
Reply to author
Forward
0 new messages