Q:Why is Vidyo making this change?
A: Vidyo’s migration to native WebRTC now bypasses the need for WebRTC transcoding (encoding and decoding of the video stream). In doing so, the quality of WebRTC calls are improved by minimizing delays.
Q: How much time do I have to make this change?
A: We will no longer allow calls from Google Chrome on versions earlier than SDK v4.1.24 starting November 4, 2018. Be sure to get your code updated prior to this date and deployed to your users to allow uninterrupted calls on Google Chrome.
Q: Are any other platforms affected by this change?
A: This change only affects users on Google Chrome. Users who connect via iOS, Android, Windows, or macOS SDKs are not affected by this change. Additionally, users on other supported browsers including Firefox, Safari, Microsoft Edge and Internet Explorer are not affected by this change.
Q: What is involved in this change?
Q: Will my users see a difference after this change?
A: Users who join video calls using Google Chrome will immediately benefit from improved video quality as there are minimal delays added by the transcoding process. Also you can obtain even higher resolutions through use of APIs.
Q: Are there any new features associated with this new version?
A: On November 4, 2018 we will no longer connect calls from Google Chrome using prior versions to 4.1.24. It is very important to make the necessary updates prior to to this date for uninterrupted Google Chrome service for your users.
Q: Will there be any changes like this in the future?
A: The current architecture change enables native WebRTC for Google Chrome. Over time, we plan to support additional browsers in the same native (non-transcoded) fashion. However, we do not anticipate any code changes but may require you to an updated and incorporate a later version of the SDK. Vidyo always recommends keeping up to date with the latest version of the SDK to take advantage of resolved issues/bug fixes, stability improvements, and new features.