Live data from Hacker News

Show HN: Pxy – A Go server that proxies websocket livestreams to RTMP servers

github.com

1–10 of 34 posts

Re: Show HN: Pxy – A Go server that proxies websocket livestreams to RTMP servers

#4
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.

Re: Show HN: Pxy – A Go server that proxies websocket livestreams to RTMP servers

#5
post #4

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.

Re: Show HN: Pxy – A Go server that proxies websocket livestreams to RTMP servers

#7
post #4

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.

Re: Show HN: Pxy – A Go server that proxies websocket livestreams to RTMP servers

#8
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 RTMP traffic.

Re: Show HN: Pxy – A Go server that proxies websocket livestreams to RTMP servers

#9
post #7
post #4

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.

A...WebM H.264 stream? Again, with feeling. This time, try something that's a thing.

Re: Show HN: Pxy – A Go server that proxies websocket livestreams to RTMP servers

#10
post #7

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.

That's what I always assumed you got back when you create a MediaRecorder like so:

  new MediaRecorder(stream, { mimeType: 'video/webm;codecs=h264' })
Which is what this project does. Is it actually returning something else behind the scenes?
Post reply on HN