Important Notice!
Read more below:
Vidyo's native WebRTC is a redesign and enhancement of Vidyo's WebRTC solution, which improves the scalability, quality, stability, and performance in your vidyo.io browser experience. The WebRTC client now directly interacts with the vidyo.io infrastructure without needing to go through transcoding gateways.
In vidyo.io version 4.1.24, Vidyo has significantly enhanced the way we support WebRTC calls by offering full native WebRTC support for Google Chrome™. Therefore, in order for your users to continue to make video calls using Chrome, you must update your application to the latest vidyo.io SDK and possibly make changes to your code.
Note: To maintain Chrome support in the vidyo.io application, you must upgrade to version 4.1.24.15 or later. The vidyo.io service will no longer accept connections from Chrome; unless you are using version 4.1.24.15 or later.
Upgrade Your SDK
- Vidyo Client library versions prior to 4.1.24.15 have been deprecated for Chrome.
- Starting with version 4.1.24.15, the Vidyo Client library will automatically route Chrome users to native WebRTC.
Verify and Update Your Code
The previous WebRTC APIs allowed you to pass arguments either by dictionary or directly. The new WebRTC APIs now only support dictionary notation. Therefore, you must ensure that all vidyo.io API calls you make pass in their arguments as dictionary objects.
You can quickly and easily make these modifications as outlined in the following example:
Previous API Call (ShowViewAt):
vidyoConnector.ShowViewAt(divId, offsetLeft, offsetTop, w, h);
Modified API Call (ShowViewAt):
vidyoConnector.ShowViewAt({viewId: divId, x: offsetLeft, y: offsetTop, width: w, height: h});
One additional change is in regards to the ShowViewAt API itself. In previous versions of the JavaScript library, this call was optional, whereas now ShowViewAt is required to be called to properly render video.
Resources:
For more information about this release, refer to the following resources:
Best Practices
To obtain the latest upgrades/releases, please refer to the Updating Your Code to Instantly Receive the Latest Upgrades/Releases article in the Best Practices section.
6 Comments
Follow