We are glad to announce that this is the last beta version of OpenVidu 3 before a General Availability version is released. You can expect a production-ready release of OpenVidu 3 very soon (at some point of Q4 2024).
Changelog
Centralized configuration
OpenVidu now automatically manages and synchronizes the configuration of all its components. This means that updating any configuration parameter in multi-node deployments (OpenVidu Elastic and OpenVidu High Availability) is as simple as updating the required file in a single node. OpenVidu handles the distribution and restart of the affected services across all nodes. See how easily you can change the configuration here.
mediasoup support
- Dynacast is now supported (LiveKit reference).
- Adaptive Streaming is now supported (LiveKit reference).
- Speaker Detection events (LiveKit reference).
- Server API method
MutePublishTrack(LiveKit reference). - Client API method
RemoteTrackPublication.setEnabled(LiveKit JS reference).
OpenVidu Call
- When using it against an OpenVidu Local Deployment, recordings couldn’t be accessed from the application’s frontend. This is now fixed and OpenVidu Call is able to access recordings.
- There was an error when applying Virtual Backgrounds (“No camera tracks found. Cannot apply background”). This is now fixed.
- Docker image openvidu/openvidu-call is now 50% smaller.
OpenVidu v2 compatibility
- There was a race condition when multiple participants connected to the Session at the same time that could cause remote
streamCreatedevents to not be triggered. This is now fixed. - Configuration parameter
V2COMPAT_OPENVIDU_PRO_AWS_S3_BUCKETdid not allow configuring subbuckets ("openvidu" worked fine, but "openvidu/subbucket" did not). Now it is possible to do so. - The operation to list recordings (available for REST API, openvidu-java-client, openvidu-node-client) was limited to 1000 recordings. This is now fixed and all recordings are always returned.
AWS deployments
- All secrets are now synchronized with AWS Secrets Manager. You can update any secret from the AWS console and restart your cluster for them to have immediate effect in all your nodes. This is also true in reverse: you can update any secret inside your node and after a restart of the cluster, the values in AWS Secrets Manager will be properly synchronized.
New application tutorials
- There are brand new application tutorials to get you started in the blink of an eye: iOS, Android, Recording.
Known limitations
While beta 3 has ironed out most of the limitations of using mediasoup instead of pion as the internal RTC engine, there are still a few details remaining (which will be addressed in the near future):
- No
ConnectionQualityChangedevent (LiveKit reference). - No
TrackStreamStateChangedevent (LiveKit reference).
