Releases
3.0.0#
Changelog#
- General Availability of OpenVidu 3, which is considered now stable and production-ready. Beta versions of OpenVidu 3 are preparing to be discontinued (including 3.0.0-beta1, 3.0.0-beta2 and 3.0.0-beta3).
Known limitations#
- When using mediasoup:
- No
ConnectionQualityChangedevent (LiveKit reference). - No
TrackStreamStateChangedevent (LiveKit reference). - Limitted ingress support: non-simulcast video tracks are not supported. Firefox may experience issues when subscribing to ingress video.
- No
Version table#
3.0.0-beta3#
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.
- There was a race condition when multiple participants connected to the Session at the same time that could cause remote
- 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 available: iOS, Android, Recording.
Known limitations#
- When using mediasoup:
- No
ConnectionQualityChangedevent (LiveKit reference). - No
TrackStreamStateChangedevent (LiveKit reference).
- No
Version table#
3.0.0-beta2#
Changelog#
- Improved mediasoup support:
- Data messages work (LiveKit reference).
- Ingress supported (LiveKit reference).
- Improved OpenVidu Local Deployment:
- Fixed Room Composite Egress (LiveKit reference) support when using mediasoup.
- WebHooks (LiveKit reference) supported against a local OpenVidu Call.
- Production deployments have a better private IP discovery process when there are multiple valid private IPs in the same host. This will make work more deployments out-of-the-box without the need of manual intervention.
- OpenVidu PRO Evaluation Mode improved. Before a maximum a 2 Rooms of 8 Participants each could be created. Now the upper limit of Participants still apply, but the number of Rooms is unlimited. For example you can have 4 Rooms of 2 Participants each, or 1 Room of 8 Participants.
- Minor bug fixes related to OpenVidu Call.
Known limitations#
- When using mediasoup:
- No support for Speaker Detection events (LiveKit reference).
- No
ConnectionQualityChangedevent (LiveKit reference). - No support for Dynacast (LiveKit reference).
- No support for Adaptive Streaming (LiveKit reference).
- When using OpenVidu Call against an OpenVidu Local Deployment, recordings cannot be accessed.