I have nimble streamer setup to receive SRT connections in Listen mode, then transcode to NDI using live Transcoder. This workflow works well, except when the SRT stream stops and restarts.
Here are the issues:
Using OBS or Larix Broadcaster, if the user stops the SRT stream, then restarts within 30 seconds, 2 different errors result:
1. In some instances, the user cannot reconnect and nimble.log shows the following error, and cannot reconnect unless I manually restart the connection in WMSPanel :
[2021-01-12 18:24:03 P1248-T1266] [srtlisten] E: srt_bind for 0.0.0.0:5002 failed, s=193196335: Connection setup failure: unable to create/configure SRT socket: Address already in use
[2021-01-12 18:24:03 P1248-T1266] [srtlisten] E: failed to bind srt socket 0.0.0.0:5002
2. In other instances, the user can reconnect, but nimble.log shows the following error, and the transcode pipeline does not restart:
[2021-01-12 18:29:53 P1248-T1316] <- [2021-01-12 18:29:53 P5586-T5586] [nimble_ndi] E: failed to read msg size
[2021-01-12 18:29:53 P1248-T1316] <- [2021-01-12 18:29:53 P5586-T5586] [nimble_ndi] I: nimble ndi stopped, id=3
There seems to be a timeout period for a disconnected SRT stream. Is this normal behavior? If so, is there any way to reduce the timeout period? If a connection drops, I need the user to be able to reconnect quickly, without waiting 30 seconds.
Thanks for your help
Could you please send us this request via https://wmspanel.com/help so we could assign it to our engineers and discus it further? Many of such questions require account-specific information so we prefer keeping it away from public forum.
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the