11–20 of 34 posts
Earlier quoted context omitted.
This appears to use the MediaStream Recording API ( https://developer.mozilla.org/en-US/docs/Web/API/MediaStream... ) to produce a WebM H.264 stream, which can be sent to the WebSocket. The server then transmuxes this to a FLV H.264 stream for RTMP output.
A...WebM H.264 stream? Again, with feeling. This time, try something that's a thing.
Earlier quoted context omitted.
This appears to use the MediaStream Recording API ( https://developer.mozilla.org/en-US/docs/Web/API/MediaStream... ) to produce a WebM H.264 stream, which can be sent to the WebSocket. The server then transmuxes this to a FLV H.264 stream for RTMP output.
A...WebM H.264 stream? Again, with feeling. This time, try something that's a thing.
What kind of video sources provide output via websockets to be proxied to RTMP? OBS and other streaming video tools usually support RTMP themselves and browsers only support WebRTC out of the box as far as I know. I'm curious what kind custom browser video streaming solution you're using on the client side.
I think the inverse of this (RTMP to Websockets) would be more interesting.
Can this be used as a web front end for say a raspberry pi camera ?
What kind of video sources provide output via websockets to be proxied to RTMP? OBS and other streaming video tools usually support RTMP themselves and browsers only support WebRTC out of the box as far as I know. I'm curious what kind custom browser video streaming solution you're using on the client side.
This appears to use the MediaStream Recording API ( https://developer.mozilla.org/en-US/docs/Web/API/MediaStream... ) to produce a WebM H.264 stream, which can be sent to the WebSocket. The server then transmuxes this to a FLV H.264 stream for RTMP output.
Earlier quoted context omitted.
A...WebM H.264 stream? Again, with feeling. This time, try something that's a thing.
WebM is Matroška, and it can contain H.264 as far as I'm aware. Not sure precisely what browsers decide to do here, but apparently it's something .
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.
What kind of video sources provide output via websockets to be proxied to RTMP? OBS and other streaming video tools usually support RTMP themselves and browsers only support WebRTC out of the box as far as I know. I'm curious what kind custom browser video streaming solution you're using on the client side.
I think the inverse of this (RTMP to Websockets) would be more interesting.
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 with their own headaches. This just uses the MediaRecorder API to send chunks of video as it’s available via a WebSocket, then the server pipes those messages into FFmpeg via stdin. It’s lightweight enough that it even runs incredibly well on Glitch[3].
Also, if you’re curious, the videos that come out of the MediaRecorder are all over the place between browsers, but they’re all varying degrees of “barely qualifying as playable video”. Incredibly fun to play with, but you will absolutely need to encode any output from it.
[1] https://mux.com/blog/the-state-of-going-live-from-a-browser