Partners Blog Contact Us

ARCHIVED ARTICLE: VidyoClient API 20.2.0 and 20.1.0 (LA): Releases


IMPORTANT NOTICE - ARCHIVED ARTICLE: This article has been archived. Please refer to the published and up-to-date article here.

This article describes the new features, functionality, and resolved issues for each of the VidyoClient API releases beginning in 2020 (subsequent to the VidyoClient API 3.x releases). 



2020 Releases



VidyoClient API: About Version 20.2.0

What's New in This Release

Multiple Enhancements for Custom Layout

  • Multiple enhancements have been added to the Custom Layout in order to provide a better user experience. These enhancements include APIs that the application can use to reduce the chance of getting black video tiles as well as to reduce the receive bandwidth usage.
  • The VidyoConnector Sample has also been updated to include a new layout where all the tiles are equal-sized.

Disabling Video Under Prolonged Low Bandwidth Conditions

  • If an individual user in a call experiences prolonged low network bandwidth, their video feed will automatically shut off. By doing so, their limited bandwidth can be used to transmit their audio.
  • Whenever the VidyoClient API shuts off a video stream due to prolonged low bandwidth, it will notify the application.
  • This feature is disabled by default. For information about how to enable it, contact Enghouse Vidyo as listed in the Contact Us article.

Automatically Reconnecting to Conferences

  • Calls will now automatically attempt to reconnect if they were disconnected under conditions where Enghouse Vidyo  determines a reconnection attempt may be successful.
  • If this occurs, the affected users will be notified of the following:
    • When a reconnection is being attempted.
    • The number of attempts at reconnection. 
    • Whether the reconnection is successful or not. 
  • This feature is disabled by default. For information about how to enable it, contact Enghouse Vidyo as listed in the Contact Us article.

Support for Additional Processors

  • We can now detect newer processors including the Intel Cannon Lake, Intel Ice Lake, and Apple A13, thereby enabling our customers to achieve top-level performance.

Disabling the Default Install License Behavior

  • By default, an install license is consumed whenever a VidyoClient-based app is installed on a new machine. However, an Advanced option is now available that enables you to disable the default install license behavior.
  • This feature is disabled by default. For information about how to enable it, contact Enghouse Vidyo as listed in the Contact Us article or by reaching out to your authorized Vidyo Reseller.

Pinning and Unpinning One Video Tile at a Time

  • The ability to pin and unpin one video tile at a time on a composite layout has been added.
  • Support for pinning multiple participant tiles is not yet available.

Number of Encoded Spatial Layers Added to Statistics

  • For easier debugging, the statistics now identify the number of spatial layers received, decoded, or rendered by the receiving client.

New and Updated APIs

  • VidyoConnectorSetPool API for guests
    • The VidyoConnectorSetPool API can now be used for guest users. This API enables the  application to determine which VidyoRouter in the network will be used for the call by the client.
  • New API to lock orientation of mobile devices
    • The new VidyoLocalCameraSetOrientation API enables the application to lock the orientation of the video rendering window.


Resolved Issues

The following table lists the resolved issues in VidyoClient API version 20.2.0:  

VidyoClient API Version 20.2.0 - Resolved Issues

Key Summary


Enghouse Vidyo fixed a crash issue that was caused when moving a window on Windows 10.


Enghouse Vidyo fixed an issue where white flickering could sometimes be seen in the background of some video tiles.


Enghouse Vidyo fixed a black tile issue that occurred for some users in large calls when using a Custom Layout.


A crash issue that occurred when using VirtualVideoSource and SetBoundsConstraints has been resolved.


If a user attempts to connect to a locked room or specifies an invalid room PIN, only one callback (rather than two) is now triggered and the correct error messages are received.


Enghouse Vidyo fixed an issue where the user's display name was not being updated properly if the user left and rejoined the call.


Enghouse Vidyo fixed an issue where connecting to a call took longer for iOS users when compared to Android and Web users. 


Enghouse Vidyo fixed an issue where Japanese characters in device names and participant names appeared garbled when using the IE plugin.


Enghouse Vidyo fixed an issue where the app got stuck when a local window share was started before joining a call.  


Enghouse Vidyo fixed an issue where DTMF signals were being played in a call if, for the previous call, the user had dialed out and entered the meeting ID using the dialpad.
Enghouse Vidyo fixed an intermittent crashing or freezing issue that occurred due to a deallocated "VCParticipant" object.
Enghouse Vidyo fixed an issue where the app would crash if the user disabled Wi-Fi on their Android or iOS device when in the process of joining a call.
IO-1552 Enghouse Vidyo fixed an issue where raw frames were not working on C# and Java bindings. 
IO-1539 When a crash occurs on the Android platform, the crash stack trace is now getting printed in the logs.
IO-1535 Enghouse Vidyo fixed an issue where a registered user on tenant A (who gets their privileges on tenant A) joins a call on tenant B, they erroneously get the same privileges on tenant B as on tenant A.
IO-1116 Enghouse Vidyo fixed a camera labeling issue so that the correct labels now appear for camera preview and content preview. 



VidyoClient for WebRTC JavaScript Library: About Limited Availability (LA) Version 20.1.0

What's New in This Release

Introducing the New VidyoClient for WebRTC JavaScript Library

  • Enghouse Vidyo introduces the new VidyoClient for WebRTC JavaScript Library which is based on the latest generation VidyoClient Library rather than the legacy VidyoWorks SDK (version 3.x). We have dramatically improved it for ease of use, performance, and flexibility. 
  • If you are a Vidyo customer with an existing application built with the previous-generation VidyoWorks SDK, you can now migrate to our new VidyoClient for WebRTC JavaScript Library.  

WebRTC Supported Browsers   

  • The VidyoClient for WebRTC JavaScript Library, along with the VidyoConnector reference app, now run on the Javascript platform on the following supported WebRTC browsers: 
    • Google Chrome™ on Windows®, macOS® and Android™
    • Safari® on iOS/iPad OS and macOS
  • Supported Platforms 
    Platform OS Version Browsers
    Windows 10 and later Google Chrome 83 and later
    macOS 10.14 and later

    Google Chrome 83 and later

    Safari 13.1.1 and later
    iOS/iPad OS 13.6 and later Safari
    Android  8 and later Chrome 83 and later

Codec Support

  • Enghouse Vidyo provides the following audio and video codec support in our desktop and mobile applications: 

    Codec   Audio/Video Browser Support 
    VP9 - SVC Video  Google Chrome 
    VP9 Video 

    Google Chrome 

    VP8 Video  Google Chrome and Safari
    OPUS  Audio N/A

New WebRTC Features and Updates

  • Content Share
    • Participants can share and receive content by selecting the Content Share button in supported browsers (e.g., Chrome and Safari). 
  • Device Switching Support 
    • Users can easily switch between devices. 
  •  Public Chat
    • Support is available for in app public chat to send and receive in call messages via the VidyoConnectorAddMessageClass API.
  • Transport-CC Support 
    • VidyoClient API's for WebRTC now natively support the transport-cc protocols which improves bandwidth estimation and congestion control in WebRTC.
    • For more information on transport-cc, refer to the RTP Extensions for Transport-wide Congestion Control web page.  
  •  PIN Protected Calls
    • To enhance security during calls, there is an option to enable PIN access. Once set up, users are required to to enter a PIN prior to joining a call. 
      • For Epic Context Aware Linking (CAL) Integrations: The extDataType and extData parameters are available to support Epic CAL integrations.  
  • Custom Layout Rendering Support
    • When it comes to embedded video, different layouts are often required for varying types of applications as one size does not fit all. With this version, developers can easily customize the layout of the on-screen video by changing the location, size, and shape of the tiles.

New APIs

  • VidyoConnector.GetConnectionProperties() API
    • The VidyoConnector.GetConnectionProperties() API allows you to get the room display name.  
  • VidyoConnectorConnectToRoomAsGuest API
    • This API allows a guest to join a conference call with a PIN.  
  • VidyoConnectorRegisterRecorderInCallEventListener API
    • This API enables participants to know when they are being recorded during a video call. 
  • VidyoConnectorAddMessageClass API
    • This API allows the application to white list special messages to forward to the application (default is none).
  • APIs to Limit Bitrate on WebRTC  
    • The VidyoConnectorSendMaxBitRate API allows you to set the VidyoClient maximum send bitrate information from the joinWeb response from the VidyoPortal.
    • The VidyoConnectorSetMaxSendBitrate API permits you to set the VidyoClient maximum set bitrate information. 
    • The SetMaxBitRate API was used in prior versions and only was limited to setting the max bit rate and in this version support was added to set the maximum send bitrate information.
  • EnableDebug API
    • This API allows you to enable additional log messages to diagnose issues.

IMPORTANT NOTE: You will need to add your CORS default domain per tenant of your web application to the VidyoPortal. Please contact the Vidyo Support Team via email or phone at the locations listed in the Contact Us article for instructions. 


Known Issues

The following table lists the known issues in VidyoClient Library Version 20.1.0 (LA):

VidyoClient Version 20.1.0 for WebRTC JavaScript Library (LA)- Known Issues

Key Summary

When using iOS on Safari with WebRTC, some iPhones (e.g., X GSM and XS/XS Max) will hear a clicking sound transmitted. 


Some Android device users experienced a crash issue when using VidyoClient native WebRTC on Google Chrome. Workaround: Applications using the WebRTC library must update to Chrome version 83 or later.  

IOWEBRTC-1135 and IOWEBRTC-1134 Audio issues occur when using Safari version 13.1 and earlier. Workaround: Use Safari version 13.2 or later or Safari Technology (TP) Preview version 107 or later. NOTE: Audio will be fixed in Safari TP, but AV synchronization issues may still occur.
IOWEBRTC-1100 During calls, the Chrome tab crashed after changing the microphone (mute/on off) with some Android devices. Workaround: Applications using the WebRTC library must update to Chrome version 83 or later.  
IOWEBRTC-1067 Mobile share may not work on some Android devices that do not support  VP8 video acceleration.
IOWEBRTC-1060 Sometimes audio will not work from participants using an iPhone with iOS version 13.5.1 and earlier in WebRTC. This issue occurs intermittently for iPhone and iPad users and refreshing the mobile browser does not remedy the issue.  Workaround: This issue may resolve when using iOS version 13.6 and later. 
IOWEBRTC-1037 The energy bar (e.g., battery  indicator) does not work for some Android devices when using Chrome version 80 and later.  


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



Please sign in to leave a comment.