OpenVidu 2.17.0: enjoy scalable recordings and forced codecs!

New features

Scalable COMPOSED recordings (OpenVidu Pro)

OpenVidu Pro has always been focused on offering scalability features upon OpenVidu CE, and there was still one very important limitation: COMPOSED recordings were not scalable, as they were being performed in the OpenVidu Server Pro Node. Until today: from 2.17.0, recording modules will be launched in Media Nodes. Since Media Nodes are infinitely scalable, the limit of simultaneous COMPOSED recordings has been effectively eliminated, and the load on your OpenVidu Server Pro node should remain much lower and stable. This is great news!

COMPOSED recording in OpenVidu Pro 2.17.0 is fully scalable

Force the video codec in OpenVidu Sessions

Until now OpenVidu always honored the preferred video codec requested by each client. This had a very important consequence: whenever 2 clients negotiated 2 different codecs, OpenVidu had to perform transcoding between them, which resulted in much more intensive CPU usage and poorer media quality. With 2.17.0 codecs are managed in a much better way:

Improving the performance and compatibility of your OpenVidu app has never been easier!

New signalSent event

This has been a very requested feature. You can now receive in your backend side all the signals sent to your OpenVidu Sessions. They will be received by your WebHook and registered in your CDR. Take a look at this new useful event here.

Microsoft Edge now supports screen sharing

Just as it sounds. Now Microsoft’s browser is also able to screen share in OpenVidu!

Choose the instance type when launching new Media Nodes on AWS (OpenVidu Pro)

When deploying OpenVidu Pro on AWS now you are not forced to set a default size for all your Media Node. Simply indicate the EC2 instance type that you want as a parameter in the operation to add a new Media Node:

curl -u OPENVIDUAPP:YOUR_SECRET --request POST --header "Content-Type: application/json" --data '{"instanceType":"c5.2xlarge","volume":200}' https://your-openvidu-ip/openvidu/api/media-nodes

More powerful S3 recording upload (OpenVidu Pro)

There is a new configuration property OPENVIDU_PRO_AWS_S3_HEADERS that allows defining any HTTP header value that the internal S3 client may require to upload recordings to the bucket. The internal S3 client also better manages expired credentials and tries to automatically renew them if necessary. Check out S3 recording upload here.

Programmatic restart of OpenVidu Pro greatly speeded up (OpenVidu Pro)

The REST operation to restart OpenVidu Pro and apply new configurations is now much quicker. Internal improvements have accelerated the process by several seconds.

OpenVidu Pro monitoring completely revamped (OpenVidu Pro)

There is now more information and better displayed in Kibana. This includes things like:

Check out the new monitoring section of the documentation.

There are new dashboards in OpenVidu monitoring stack to provide a much more accurate and useful information.

Bug fixes

OpenVidu Pro

openvidu-java-client / openvidu-node-client


COMPOSED recordings

Breaking changes

Stay tuned for next iterations! You can follow us on Twitter and a Star in GitHub is always welcome :)