I'm using Nimble Streamer to republish an SRT stream via RTMP. I'm testing a live streaming provider's (3rd party) primary/backup ingest failover (RTMP).
When streaming RTMP directly (from hardware encoder) to the provider the fail over works immediately. However when I manually stop the SRT stream (going into Nimble Streamer) and being republished via RTMP, the failover takes several seconds. Now if I simply pause the RTMP republishing the failover works immediately (as with the external encoder).
It appears that when the SRT stream fails there is some type of time out window occurring before Nimble Streamer closes the republished RTMP connection. Is this configurable? Perhaps an SRT parameter?
We do not provide any timeout option to close the RTMP connection. We are not aware of SRT settings that can help with this too.
I went digging in the SRT github and found this option:
SRTO_PEERIDLETIMEO 1.3.3 pre int32_t msec 5000 positive only
The maximum time in [ms] to wait until any packet is received from peer since the last such packet reception. If this time is passed, connection is considered broken on timeout.
Are these options, like latency and maxbw, exposed through WMSPanel?
This option could not be used in Nimble's SRT settings, and it won't help with your case. RTMP republishing uses MPEGTS OUT (corresponding to SRT IN) as input and this delay occurs in it.
We are working on improving this. Stay tuned for Nimble streamer updates.
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