mistserver: Streaming SRT using OBS does not work / causes heavy artifacts
Mistserver version: 3.0 Free_64
Server OS: Debian 11.2
Server stream settings
Server netstat
# netstat -tulpn | grep 8002
udp 0 0 0.0.0.0:8002 0.0.0.0:* 500806/MistInTSSRT
Server status
OBS Server url: srt://<ip>:8002
Mistserver log
Stream preview fails
If you need any additional information or command I should run on the server for debugging this, please just let me know.
EDIT:
The video encoder used on OBS is x265 with CBR set to 2500 Kbps and streaming using rtmp works without issues.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 15 (3 by maintainers)
@labor4 @nerijus here are my settings in case you are interested:
protocols setting
stream setting
in OBS:
playback url:
https://<domain>/obstest.mp4MistServer 3.1 is released as of the 24th. So it should be possible to use those srt-values now when set up as a single stream input. If not we’d obviously want to hear that 😉
And it’s a bit late on the password question, but: With the way the SRT library works you can’t set a password when inputting all SRT streams over a single port. This is because the password will then count for all connections and not just a single stream a password the way you’d want it to work isn’t implemented in the actual SRT library. That said, I can see value in adding all parameters to be set up for the single port connection as well, even though all SRT streams would have to share the passphrase the other options could be meaningful. I’ll add it to the list of features to add.
Passphrase comes close, but can only be used when the port is only meant for that stream. So you’d need to use a stream with “srt://etc” as source.
@nerijus SRT URL syntax is usually along:
Push to Mist:
srt://1.2.3.4?streamid=test&var=key&var2=key2“test” being the identifier with which Mistserver can create subchannels.
@Rokamun Hi, would you please re-up your screenshots of your config? I see only “[image: image.png]”. Thanks.
Hello,
We’ve found this issue ourselves just recently as well. Apparently the SRT connection doesn’t go well when using a specific port through the source set up. We did find out an alternative that works just as well:
Go to the protocols panel and add TS over SRT, choose any (TCP) port and set it up to only allow incoming connections (first option): [image: image.png]
Set up your live stream to:
push://
[image: image.png]
Now push towards MistServer using this address:
srt://mistserveraddress:port?streamid=streamname
Using the examples above mine would be:
srt://misttserveraddress:27015?streamid=test
You can re-use this url for multiple streams within MistServer, just be sure to change the stream name accordingly. That should work, hope that helps while we fix the specific port binding.
With kind regards,
Balder Viëtor Head of Testing
On Sat, Mar 5, 2022 at 6:54 PM zocker-160 @.***> wrote: