SIPSorcery VS SIPSorceryMedia.FFmpeg

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 checked another example in Sipsorcery and it works. In this example it show a basic test pattern. For screen sharing Sipsorcery uses FFMPEG. I think FFMPEG has the restriction to capture the screen when the system is signed out.

I was going through FFmpegFileAndDevicesTest, it is created using Sipsorcery library. In this code a websocket server is created and the PeerConnection is added to the websocket. Is there any way to connect to an external websocket server instead of creating one. The code is

Hello. I am new to WebRTC and currently working on a small project in .NET using Sipsorcery, a WebRTC library for C#. In this particular example, an application is used to enables screen sharing using WebRTC. The screen can be viewed through an HTML page, while WebSocket is utilized as the signaling channel. The application includes both the WebSocket server and the code for screen sharing. The application works like a charm. After testing the application I converted the application into Windows Service to always run it in the background. I used NSSM to make service. But when I tested the service, I encountered an issue where the WebSocket server works fine when the system is logged out or signed out, but the screen sharing functionality fails. I googled this problem and discovered that WebRTC does not function properly when the system is signed out or logged out. I am curious to understand the underlying mechanism behind this limitation. Why is it that the screen cannot be shared when the system is signed out?

I was going through FFmpegFileAndDevicesTest, it is created using Sipsorcery library. In this code a websocket server is created and the PeerConnection is added to the websocket. Is there any way to connect to an external websocket server instead of creating one. The code is