OvenMediaEngine VS server

We're thrilled to announce the release of OvenMediaEngine 0.15.16!

We are pleased to announce that OvenMediaEngine has been updated to version 0.15.15. This update follows the recent 0.15.14 release, which introduced the SRT Push Publisher and support for OCSP stapling. With the 0.15.15 update, we have fixed a few crash issues. Thank you for your continued support, and we look forward to providing you with more reliable and enhanced streaming solutions.

OvenMediaEngine has been updated to 0.15.13, which includes 0.15.12 with support for HEVC in SRT Provider and LLHLS Publisher. In 0.15.13, we have enhanced compatibility and usability to make the streaming server more stable. For more information, see the release notes for versions 0.15.12 and 0.15.13.

The following content is taken from OvenMediaEngine Discussions #1242.

OvenMediaEngine has been updated to version 0.15.10, please see the release notes for details.

Info: OBS Studio 29.0.2, OME 0.15.7

Since OvenMediaEngine's update to version 0.15.4 uncovered several policy and feature conflicts, which have since been resolved in the latest version, 0.15.7. For more details, please look at the release notes for versions 0.15.5, 0.15.6, and 0.15.7.

With the 0.15.3 update, OvenMediaEngine supports multiple audio track inputs via SRT and stream creation/deletion APIs. Please see the release notes or below for details.

Also, we are preparing to show you OvenMediaEngine, a sub-second latency streaming solution using LLHLS and WebRTC, and give you a chance to experience the OvenMediaEngine Enterprise Demo.

The first update of OvenMediaEngine for 2023 has been released. This is version 0.15.0 and has improved stream quality for WebRTC providers. Please check out the release notes or below for details.

Amazing work! The WebRTC community needs something like this so bad. Not only will this push a bunch of users toward self-hosted/free software but will also inspire others to build cool things :)

If/when you hit scaling challenges I would love to help! I maintain github.com/pion/turn and github.com/pion/webrtc. You can see that with how screego[0] does it.

Happy to help however I can (even if not using Pion!) One of the reasons I built it was so that I could put my TURN and Signaling server in the same process. It makes it way easier to tie your auth together for signaling+TURN. Then if you do go down the SFU route lots of interesting things you could do.

[0] https://github.com/screego/server/blob/e845b3d29c4b5794ed10f...

Check out ScreeGo : https://github.com/screego/server