Version 22.5.0 GA
What's new in this release?
- Compatibility with Android 13 OS
- We’ve updated the VidyoClient API binary library so it’s now compatible with Android 13, Google’s latest mobile operating system.
- Call quality indicators
- With this release, applications get call quality indicators to enable users to easily retrieve information about the sending and receiving video quality of their calls.
- The existing callbacks VidyoRoomOnAvailableResourcesChanged and VidyoConnectorOnAvailableResourcesChanged now report this information:
- cpuEncode — Available CPU for encoding sources
- cpuDecode — Available CPU for decoding sources
- bandwidthSend — Available bandwidth for sending sources
- bandwidthReceive — Available bandwidth for receiving sources
- The values above are percentages and in the range of 0-100.
- cpuEncode or cpuDecode: If the value is higher than 0, assume that the system has sufficient CPU and the call is running with high quality; otherwise, the call is running with low quality.
- bandwidthSend or bandwidthReceive: When the application chooses a particular resolution to be transmitted for video OR shared content, VidyoClient calculates these two numbers:
- preferredBitrate — If enough bandwidth is available to do this, the video and call quality will be good.
- nominalBitrate — This is the minimum bandwidth required to stream the resolution chosen by the application. The preferredBitrate is always greater than the nominalBitrate.
- The call quality indicator callback logic is as follows:
- If the available bandwidth on the system is less than the nominalBitrate, the application will get 0 in the callback, which indicates low call quality.
- If the available bandwidth on the system is greater than the nominalBitrate but less than the preferredBitrate, the application will get a value between 1% and 70% in the callback.
- If the available bandwidth on the system is greater than the preferredBitrate, the application will get a value between 71% and 100% in the callback.
- Applications are free to choose their own ranges, but the following ranges are from the VidyoClient perspective:
- High quality — 50-100%
- Medium quality — 25-50%
- Low quality — 0-25%
- Deprecated APIs
- To simplify the APIs, we deprecated some of the existing APIs for video sources such as window share, monitors, and virtual video sources. The following table lists the deprecated APIs and their replacements, if any:
|
This API... |
Has been replaced by this API... |
|---|---|
| VidyoVirtualVideoSourceSetBoundsConstraints | VidyoVirtualVideoSourceSetMaxConstraints |
| VidyoVirtualVideoSourceSetDiscreteConstraints | VidyoVirtualVideoSourceSetMaxConstraints |
| VidyoVirtualVideoSourceSetLowLatencyProfile | N/A |
| VidyoLocalWindowShareSetBoundsConstraints | VidyoLocalWindowShareSetMaxConstraints |
| VidyoLocalWindowShareSetDiscreteConstraints | VidyoLocalWindowShareSetMaxConstraints |
| VidyoLocalWindowShareSetFrameInterval | VidyoLocalWindowShareSetMinFrameInterval |
| VidyoLocalWindowShareSetScaleFactor |
N/A |
| VidyoLocalWindowShareSetLowLatencyProfile |
N/A |
| VidyoLocalMonitorSetFrameInterval | VidyoLocalMonitorSetMinFrameInterval |
| VidyoLocalMonitorSetFrameIntervalConstraints | VidyoLocalMonitorSetMinFrameInterval |
| VidyoLocalMonitorSetBoundsConstraints | VidyoLocalMonitorSetMaxConstraints |
| VidyoLocalMonitorSetDiscreteConstraint | VidyoLocalMonitorSetMaxConstraints |
| VidyoLocalMonitorSetLowLatencyProfile |
N/A |
Resolved issues
The following table lists the issues we have resolved in VidyoClient for API Binary Library version 22.5.0.
|
VidyoClient for API Binary Library version 22.5.0 - resolved issues |
|
|---|---|
|
Key |
Summary |
|
VIDVCB-525 |
A crash no longer occurs after upgrading to iOS version 16.0 when using kCFStreamNetworkServiceTypeVoIP. |
|
VIDVCB-482 |
Using a non-English Windows account name no longer causes the VidyoConnect desktop application to crash while launching. |
Known issues
There are no new known issues for this release.