Version 21.4.0

Version 21.4.0

What's new in this release?

Support for three Simulcast streams in WebRTC
With three Simulcast streams, we can now better adjust what your client is capable of receiving based on network bandwidth and performance.

Resolved issues

The following table lists the issues we have resolved in VidyoClient for WebRTC JavaScript Library Version 21.4.0.

VidyoClient for WebRTC JavaScript Library Version 21.4.0 - resolved issues
Key	Summary
IOWEBRTC-2191	The AddMessageClass API now works as expected.
IOWEBRTC-2092	When an iOS user on a mobile WebRTC call receives a cellular call, accepts that call via the full screen (not via the banner notice), and then ends that call, the audio and video for the WebRTC call now resume properly.

Known issues

The following table lists the known issues in VidyoClient for WebRTC JavaScript Library Version 21.4.0.

VidyoClient for WebRTC JavaScript Library Version 21.4.0 - known issues
Key	Summary
IOWEBRTC-2218	When using VP9, the application reacts too quickly when there is a change in the available outgoing bandwidth which, in some cases, unnecessarily impacts the send resolution.
IOWEBRTC-1921	Video tiles that drop from calls due to network conditions sometimes do not get restored when the network conditions improve.
IOWEBRTC-1906	If a call participant with more than one camera or microphone disconnects their active device while their camera/microphone drop-down list is open, the drop-down list doesn't update to display the remaining camera/microphone.
IOWEBRTC-1861	When using iOS 14, audio artifacts can be heard for a few seconds after the remote participant starts speaking.
IOWEBRTC-1860	When using Safari Technology Preview 121 on a Mac with an Intel processor, users are unable to share content.
IOWEBRTC-1784	Audio lip-sync is delayed on iOS Safari after flipping the camera, muting and unmuting, or putting VidyoConnect in the background.
IOWEBRTC-1705	Occasionally, Chrome encodes at 10-15 fps even when the network is unconstrained.
IOWEBRTC-1673	On Macs with dual-core CPUs, when the "Google Chrome Helper (Renderer)" process goes beyond 100% CPU, Chrome detects a CPU limitation and lowers the encoding resolution.