Additions and changes to the Twilio platform
We are excited to announce AI-Based Noise Cancellation in Twilio Video to help developers remove unwanted sounds and build high quality meeting experiences. Built in partnership with leading noise suppression vendor Krisp.ai, the Krisp Audio Plugin for Twilio Video can be added to your browser application in a few lines of code.
We are excited to release two new features to help you improve the resiliency of your Twilio Video workflows.
First, we have updated the congestion control used to measure available bandwidth for publisher and subscriber clients. The new congestion control will provide higher available bandwidth in extremely low bandwidth scenarios as well as faster bitrate recovery times in oscillating network conditions. This feature has been rolled out across all Twilio Video workflows and is automatically enabled on your Rooms.
The Video Diagnostics App tests an end user’s ability to have a quality video call with Twilio Programmable Video. It runs through a series of tests to identify issues related to device and software setup, connectivity to the Twilio cloud, and network performance. Upon failed tests, it provides recommendations to help your users help themselves.
With this release, the Video Diagnostics app is now available for your use as a Twilio-hosted web app. It can be used as part of your onboarding or support processes to assist in diagnosing end-user issues. This hosted version of the Video Diagnostics app supersedes the legacy network test tool (https://networktest.twilio.com/).
Video Insights brings self-service tooling to the Twilio Console to help you observe application usage and quality, discover trends across all your rooms and participants, and troubleshoot end-user issues. You can use Video Insights to build higher-quality video experiences for your customers, reduce churn, and scale confidently.
As part of the general availability launch, you will now have a revamped experience to filter and explore your rooms, dropdowns for segmenting your participants by
end_reason via the Insights Dashboard, and much more.
The Preflight API (
When using adaptive simulcast, a publisher will only encode video layers up to the highest spatial layer being used by subscribers.
For example, a common presentation layout in video chat will have the active speaker’s video in a large format and the remaining participants as thumbnails. In this situation, adaptive simulcast will encode all spatial layers for the active speaker and only the smallest spatial layer for the thumbnail participants. As speakers change, the respective publishing participants will automatically have their spatial layers turned on / off based on what is being used by subscribers in the room.
Compared to standard simulcast, adaptive simulcast will provide significant CPU and bandwidth improvements for your publishing clients, and we recommend all users switch from standard simulcast to adaptive simulcast.
Full HD streaming is now Generally Available as part of Twilio Live. Twilio Live’s VideoComposer extension has been updated to include the new resolution.
You can now enhance your streaming quality and improve your audience experience by setting the video resolution on your livestreams up to 1080p (1920x1080). There is no additional cost for streaming at a higher resolution.
For additional information on this release, check out our developer documentation.
The feature External Storage for Video Recordings is now available for all video customers. Customers can configure the Video Recordings service to push Recordings or Compositions directly to their AWS S3 Bucket without additional charges.
This Video Recordings feature allows builders to create a recording workflow that matches their specific use case and regulatory needs. For example, a customer in the Education space may decide to store the composed recordings of a virtual classroom into a custom S3 for data sovereignty preferences.
This feature was previously a part of Twilio Editions.
The Twilio Video Room Monitor is now generally available.
The Video Room Monitor can be used as a tool during all phases of development or can be forked, customized, and provided to end-users as an in-call troubleshooting view.
Two new video room timeout parameters,
unused_room_timeout, have been added to the video rooms REST API to allow you to better manage the lifecycle of a video room.
The empty room timeout specifies how long a room will remain active after the last participant leaves, while the unused room timeout specifies how long a room will remain active if no one joins. Both values are set upon room creation and operate independently. The new maximum value for both parameters is 60 minutes and the default value remains five minutes.
These values are only configurable for rooms created with the REST API and can be applied to WebRTC Go, Peer-to-Peer, and Group Rooms. For rooms created via the Ad-hoc method, these values are zero by default and cannot be changed.
For more information on configuring room timeouts, view the Video Rooms REST API documentation.
We are excited to announce the availability of 24 hour participant durations for video rooms.
You can now configure the Maximum Participant Duration for any Twilio Video room type. This value is set at the time of room creation, and upon reaching the limit, a participant will be disconnected from the room.
The default value for maximum participant duration is 4 hours. You can change this value either through the Console under Rooms Settings to make it the default for Ad-hoc rooms or as a configurable parameter via the REST API upon room creation.
For more information on configuring the maximum participant duration, view the participant duration documentation. If you are composing room recordings of participants with long durations, you may want to review the composition size limitations.
We continue to invest in infrastructure improvements to provide scale and high reliability for our customers, and today we are excited to increase both the default maximum concurrent Room limit to 10,000 as well as the maximum concurrent Participant limit to 10,000 for Group and Peer-to-Peer Rooms.
The maximum concurrent Room threshold limits the number of Rooms that can be in-flight at the same time while the max concurrent Participant threshold limits the number of Participants that can be connected to your rooms at the same time. Both limits operate independently at the account level.
You can view your account room limit and participant limit in the Console under Room Settings. If a limit is reached, an error code (53119, 53206) is returned and it is also displayed in the Console Debugger. If your account limits were previously above 10,000, they will remain unchanged.
The default limits are designed to give developers ample room to grow while ensuring runaway issues get caught quickly. If you need to increase your account limits beyond the default maximum concurrent Room or maximum concurrent Participant limit, please contact Sales.
We’re thrilled to announce that Video Insights is now available in Public Beta.
Video Insights brings self-service tooling to the Twilio console to help you observe application usage and quality, discover trends across all your rooms and participants, and troubleshoot issues with ease, leading to higher quality video experiences for your customers, reduced churn, and increased confidence in scaling rapidly.
Twilio Live is now Generally Available
Twilio Live gives developers the tools to build immersive live experiences that can be directly embedded into their applications such as marketing conferences, next-generation social podcasts, shopping experiences, concerts, fitness classes, education sessions, and more.
One year after launch, we are excited to announce quota increases for WebRTC Go to allow you to build, launch, and run 1:1 video applications for free, for longer. The changes are as follows:
- WebRTC Go now comes with unlimited TURN usage, removing the previous 25 GB/month limit.
- You can now scale up to 500 concurrent participants or rooms, up 500% from the previous limit of 100.
To learn more about the quota increases and some of the key improvements we made for WebRTC Go developers over the last year, refer to the One year of WebRTC Go blog post.
The Video Room Monitor can be used as a tool during all phases of development or can be customized and provided to end-users as an in-call troubleshooting view.
The Chromium WebRTC engine in the iOS & Android SDKs has been upgraded from m83 to m88. In addition to the security and performance improvements, these mobile SDKs now use the newer “unified plan” WebRTC signaling protocol, which provides improved browser compatibility in P2P and Go Rooms. The iOS SDK has added support for running the iOS Simulator on Apple Silicon ARM64 Macs. There is a major version increment for the Android SDK to 7.0 and the minimum Android API level has been increased from 16 to 21.
We are excited to announce the release of the Video Diagnostics Web App, an open source ReactJS application demonstrating how to test a participant’s ability to have a high-quality video call with the Twilio platform - now available in Public Beta for WebRTC Go, P2P, and Group Room developers.
It can be customized, embedded into your application, and used as part of onboarding to ensure a successful first video call or for diagnosing issues that relate to the device, software, or network conditions of the end-user.
Following up on the changelog posted on March 8th, 2021, today is the official End of Life for the below Programmable Video SDK versions:
- Android - 4.x and below
- iOS - 2.x and below
The above versions of the Video SDKs utilize older infrastructure that is no longer considered reliable for customers. Brownouts will begin this week, meaning there will be partial loss of service for a short period of time for the above SDKs, and will continue periodically until 5:00PM PDT on November 1st, 2021. After this, the older infrastructure will be fully shut off and these SDKs will cease to function for all customers. The brownouts will start with a duration of one hour and progressively increase in duration and frequency as time goes on.
If you are still using one of these SDK versions and wish to continue using Twilio Programmable Video, you must upgrade your SDK to a supported version. If you are using a mobile SDK, please ensure your end-users have updated their applications.
For more information, please see the initial changelog entry and when upgrading your SDK, please refer to the following migration guides:
This enhancement allows for more efficient use of bandwidth and CPU in multi-party applications, which translates into a higher quality video experience for end users. It can dynamically tailor the incoming video tracks to match the active UI layout. In addition, it provides developers with more fine grained control over the video tracks to allow developers to create unique user interfaces while still being efficient with bandwidth and CPU.