srtrelay
srtrelay copied to clipboard
voc
Adapt StreamID scheme to SRT standards
I was playing with a media server that follows this spec https://github.com/ossrs/srs , and honestly it felt quite cumbersome for streaming compared to RTMP's simple app/streamid pair. Also, bash really doesn't like shebangs when using ffmpeg on the command line, but that might be an outlier.
That said, it's not the end of the world and would be more spec compliant than SLS. Plus, This might be the best way to implement SRT crypto/passphrase checking for streams?
Just a .02.
At the moment it's not really relevant anyway because all implementers of streamid I know of so far (ffmpeg and obs) just give you a text field. It would be interesting to see whether broadcast devices will allow setting a streamid. Afaik at the moment they mostly don't.
If more applications follow the official scheme it would be nice to adopt it as well.
I think for crypto/passphrase we are dependent on https://github.com/Haivision/srtgo/issues/12 but I haven't tried it at all yet.
Small update here, most broadcast devices (my reference point here being various cheap standalone video encoder boxes on the market) allow setting the streamid field as just a text box as specified above and ultimately work quite well with the current scheme.
This is non issue.. I actually prefer this because like LiveU Solo doesn't support stream ID -- so if I had multiple streams incoming... I would need multiple docker images. So this way, for example - I can stream from Larix on a mobile phone to another "channel" and have it available for mixing, all within one solution- Keep It Simple!
This actually solves the problem nicely and is very explicit, publish, play - it just work
Also thank you very much for this.. the multiple subscription is what I was looking for- super light weight freaking awesome!
LiveU - just put in the publish/streamname in the stream id.. works fine.
If there is no input for that then just add it your self on the end of the url streamid=publish/streamname