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 browser experience. The WebRTC client now directly interacts with the infrastructure without needing to go through transcoding gateways.

In 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 SDK and possibly make changes to your code.

Note: To maintain Chrome support in the application, you must upgrade to version or later. The service will no longer accept connections from Chrome; unless you are using version or later.

Upgrade Your SDK

  • Vidyo Client library versions prior to have been deprecated for Chrome.
  • Starting with version, 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 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.


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. 

Was this article helpful?
1 out of 1 found this helpful


  • 0
    Sharat Chandra

    Is this change required for Xamarin SDK?

  • 0
    Philip Futernik

    Xamarin uses the iOS and/or Android SDKs so this update is not relevant to Xamarin. It is only needed to update your web based application.

    Edited by Philip Futernik
  • 0
    Hector Garcia

    These changes affect other browsers like Safari?

  • 0
    Philip Futernik

    Hi Hector, this thread in particular is only related to Chrome. Do note, however, that Apple has deprecated support for NPAPI plugins as of Safari 12, which may impact you if that is a browser that is supported by your web application.

  • 0
    Tunstall Health

    I have made changes to API and updated to version 4.1.24, but video quality is not good it's few seconds behind on chrome. It runs fine on Firefox  and Edge but lacks on Chrome. This is call between chrome and native android app.  What else can I do for my users to continue to make video calls using Chrome? 

  • 0
    Philip Futernik

    In regards to the video being a few seconds behind on Chrome - there are two things that are recommended:

    1 - ensure you are using version of the library as a fix related to this was made

    2 - the ShowViewAt API is now required (in versions prior to 4.1.24, it was not), so make sure you are calling it

Please sign in to leave a comment.