The new major version of Kurento has been recently released, and it is now the default version used in OpenVidu. This new version of the media server focuses on upgrading the internal dependencies to recent official versions, compared to the old versions and custom forks used in Kurento 6. This brings improvements in terms of security and stability. You can read the release notes of Kurento 7 here.
openvidu-ruby sample application server now available
We have added a new sample application server in Ruby. If you plan to build your OpenVidu application server in Ruby, you can use it as a starting point. You can find it here: openvidu-basic-ruby.
Audio-only broadcasts now available
It is now possible to broadcast an OpenVidu Session as only-audio. Visit Broadcasting to learn how.
- openvidu-browser: calling
Publisher.publishVideo(false, true)before publishing the Publisher to a Session was causing the audio track to not play on the Subscriber side. If the Publisher called the method after publishing to the Session, the audio played correctly. Now audio also plays correctly even in the case the Publisher stopped its video track before publishing to the Session. Related forum discussion: 4514. Related PR: 797
- Broadcasting: broadcasting to AWS Media Live was not possible. Now it is.
- Broadcasting: a failure in the startup process of a broadcast could end on some occasions with the Media Node being disconnected from the OpenVidu cluster. This is now fixed.
- Broadcasting & Speech To Text: a fatal error was preventing these services to start normally in very specific cases: A) If a custom Speech To Text module was based on an outdated version of the base Speech To Text module. B) If a custom layout with an outdated version of openvidu-browser was being used to broadcast. This is now fixed and the fatal error is now a warn/error message in openvidu-server-pro logs.
- OpenVidu Components: in a session with two participants and one of them using iPhone, if the other participant mutes the video, the iPhone participant was not able to see the video poster (instead the last frame was shown). This is now fixed.
- OpenVidu Components: if a Session was recorded, that recording was then deleted and the Session was recorded again, the recording service was showing the oldest deleted video due to the browser caching the request to the resource. This is now fixed.
- Openvidu Components: non-moderator participants didn’t update their recording list because they didn’t know when a recording had been deleted. Now all standard participants know the recording activity status. New
onActivitiesPanelForceRecordingUpdateevent is emitted when participants need to update their recording list.
- OpenVidu Call: the application updates the recording list from the backend listening to
- OpenVidu Call: fixed issue with participants name using Java Backend. Nicknames were not synchronized with other participants.
- OpenVidu Call: fixed a security bug with recording access. This is now fixed.