| Category: Golang / Server Applications |
| Watchers: 2 |
| Star: 38 |
| Fork: 1 |
| Last update: Nov 17, 2020 |
An RTMP stream recaster / splitter
Calling prism with one or multiple RTMP URLs will listen for an incoming RTMP connection, which will then get re-cast to all given URLs:
prism url1 [url2, ...]
If you want prism to listen on a different port than the default 1935, call it with the --bind flag:
prism --bind :1337 ...
i tested to publish to facebook live but i got a response
Starting RTMP server...
Waiting for incoming connection...
New connection!
can't write header: unexpected EOF
can't write header: unexpected EOF
I think you're tracking on this, but I'm encountering broken pipes when there's a disconnect from the downstream RTMP streams (for example, if an Owncast instance restarts).
It manifests itself with a wall of errors like:
write tcp 206.189.205.219:50394->172.104.12.173:1935: write: broken pipe
My current workaround is just to kill the prism instance.
Could you share instructions on how to install and use your application?
From what I can tell from limited digging this is something that would have to wait. Looks like current deprecated library for rtmp doesn't accept the encoder being set on metadata.
https://github.com/notedit/rtmp-lib/blob/1cc66d6cf88bab7f93886259bc3c3a90d14aedb7/flv/flv.go#L435
Not sure how you feel about using uuid there. But its a function I have sitting around in my scratch that is nice for uuid so dropped it in to generate a default key.
Attempting to multiplex with a YouTube stream fails within a second or two of connecting. It's able to reconnect, but then disconnects again.
A simple prism setup, e.g. ./prism rtmp://a.rtmp.youtube.com/live2/stream-key fails with this pattern once connected:
Starting RTMP server...
Waiting for incoming connection...
New connection!
connection established: rtmp://a.rtmp.youtube.com/live2/stream-key
write tcp 100.115.92.198:35122->74.125.159.231:1935: write: broken pipe
connection established: rtmp://a.rtmp.youtube.com/live2/stream-key
Duration: 4.65s
write tcp 100.115.92.198:35124->74.125.159.231:1935: write: broken pipe
Duration: 6.933s
connection established: rtmp://a.rtmp.youtube.com/live2/stream-key
Duration: 7.966s
write tcp 100.115.92.198:35126->74.125.159.231:1935: write: broken pipe
Duration: 9s
connection established: rtmp://a.rtmp.youtube.com/live2/stream-key
Duration: 10.005s
write tcp 100.115.92.198:35128->74.125.159.231:1935: write: broken pipe
Weirdly, YouTube's "Stream Health" shows it as an excellect connection, though no video or audio shows.
A few other debugging notes:
I wonder if the next step might be to have someone else try streaming to their own YouTube, to see if anyone else can reproduce this? Beyond that, I'm not sure how to debug further.
I'm testing out prism to split an incoming stream to two external RTMP services (YouTube and Flote). Installed prism from the .deb package on a VPS running Ubuntu 20.04 LTS, stream source is from OBS on my local machine.
Initially I used the syntax requested, but added the stream key to the end of the URL. After starting OBS, prism reported "New connection!" before immediately outputting "EOF" and then stopping.
I tried again, this time dropping the stream key from the end of the URLs, but the same occurred. Both times, OBS reported the connection as dropped when EOF was output.
No response on either streaming service, but I suspect it never went out to them. Is this an error from my input, or is this a crash of some sort?
I don't have an easy way of testing this on my end, but this should do the trick. The channel approach is essentially manual message injection.
