OvenMediaEngine VS webrtc

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.

I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc....

When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build!

Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :)

-----

I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options!

* https://github.com/shinyoshiaki/werift-webrtc (Typescript)

* https://github.com/pion/webrtc (Golang)

* https://github.com/webrtc-rs/webrtc (Rust)

* https://github.com/algesten/str0m (Rust)

* hhttps://github.com/sepfy/libpeer (C/Embedded)

* https://webrtc.googlesource.com/src/ (C++)

* https://github.com/sipsorcery-org/sipsorcery (C#)

* https://github.com/paullouisageneau/libdatachannel (C++)

* https://github.com/elixir-webrtc (Elixir)

* https://github.com/aiortc/aiortc (Python)

* GStreamer’s webrtcbin (C)

See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

This is not true, there are actually multiple WebRTC implementations in different languages besides the reference library: aiortc (python), libdatachannel (C++), sipsorcery (C#),webrtc-rs (rust), werift (Typescript), and Amazon Kinesis (C)

I am trying to get WebRTC working using Rust https://github.com/webrtc-rs/webrtc

I have opened an issue on GitHub [1], we can continue there.

[1] https://github.com/webrtc-rs/webrtc/issues/426

webrtc

webrtc.rs is a port of Pion (which we also use). It's a better fit for server-side use

I want to use peer-to-peer communication and data transfer for my next side project (client-server web app). I've been doing some research and WebRTC seems to be the only option for this on the client. There are a ton of libraries and product offering for facilitating STUN/TURN servers as a service, but I'm quite interested in learning more about these protocols. That being said, I'm not the best rust programmer (part of the reason of using Rust as the server is so that I can learn more), and the signalling protocols seem rather complicated. I've looked at https://github.com/webrtc-rs/webrtc and it seems promising.