21–30 of 34 posts
In the same genre of Go video streaming adapter servers. Here are a couple neat projects which stream from RTSP (as used by eg security cameras) to either fragmented .mp4 files over WebSocket or WebRTC: https://github.com/deepch/RTSPtoWSMP4f https://github.com/deepch/RTSPtoWebRTC I'm jealous of Go's WebRTC library that makes the latter possible. I'd love to have a similar Rust crate.
In the same genre of Go video streaming adapter servers. Here are a couple neat projects which stream from RTSP (as used by eg security cameras) to either fragmented .mp4 files over WebSocket or WebRTC: https://github.com/deepch/RTSPtoWSMP4f https://github.com/deepch/RTSPtoWebRTC I'm jealous of Go's WebRTC library that makes the latter possible. I'd love to have a similar Rust crate.
Doesn't Gstreamer provide a rust-based plugin to achieve this yet? It is surely just a matter of time if not.
I see you are invoking Ffmpeg via the shell. I also tried steaming to Youtube from Go and had to resort to the same solution. It's a shame there isn't a usable library for implementing a RTMP client in Go. Using Ffmpeg from the shell is very limiting because there is no way to monitor the status of the stream or to provide audio and video separately using stdin.
Which side of this proxy is producing/consuming only FLV/Flash streams?
Cool project! I've done similar things with Kurento acting as a WebRTC peer to proxy WebRTC --> RTMP before but this is a lot more lightweight. One thing I'd love to see at some point is a project that compiles FFMpeg's transmuxing code to WASM such that the WebM --> FLV conversion could be done client-side. That way the server-side portion would be as simple as proxying the WebSocket to a TCP socket for the outgoing…
Getting the client to do the heavy lifting while the server acts solely as a relay is a really good idea. In my use case, however, I have a flutter client that's not capable of doing that at the moment, perhaps that's something that could be explored further in the future.
Awesome to see this on the front page! I’ve been chatting with the OP for a few days and this is based on a Node.js PoC I wrote for a blog post on the state of broadcasting live from a browser[1]. This is, IMO, the simplest way to be able to go from a modern browser to an RTMP endpoint. You could try and do server-side WebRTC using a project like Pions[2], or use headless Chrome and be a peer, but both of those come…
Meanwhile, there's another well-explained tutorial that complements [1] along with a code walkthrough to implement something similar in Node.js.
https://github.com/fbsamples/Canvas-Streaming-Example/blob/m...