How to configure my SRT latency?
The SRT latency setting on each source and destination stream is key to optimize the quality of service.
The right SRT latency settings will depend on the network characteristics between the chosen Quortex Link region and the SRT device.
750 ms is a good starting point if you don’t know where to start. This will ensure reliable delivery for most common use-cases.
Depending on your network conditions, you could also typically
Go down to 300 ms if you have a high quality internet connectivity and delivering to a cloud location close to where you are located
Increase to 1500 ms or even more if you are using a lower quality internet connectivity or delivering to a cloud region located very far from where you are
The SRT latency can be configured independently for each source and each destination. This means that you can optimize the distribution independently for each destination, based on different network conditions
Once you create a source or a destination in a region, having a look at the SRT statistics is key to understand whether the connection quality is good or not.
The "SRT Dropped Packet" should always be null or very low, as it counts the number of lost packets after the SRT recovery took place (hence, it basically counts the number of unrecoverable packets). Having too many dropped packet is a clear indication that the link quality is low. You should increase the SRT latency in this case. Increasing the latency will give more room to the SRT protocol to recover packets, and is likely to reduce the amount of dropped packets.
The SRT "Round Trip Time" is also very important and can give you a very valuable hint on how to adjust the "latency" setting of your SRT stream. A good rule of thumb is that your SRT latency should be at least 3 to 4 times higher than the RTT.
The right SRT latency settings will depend on the network characteristics between the chosen Quortex Link region and the SRT device.
750 ms is a good starting point if you don’t know where to start. This will ensure reliable delivery for most common use-cases.
Depending on your network conditions, you could also typically
Go down to 300 ms if you have a high quality internet connectivity and delivering to a cloud location close to where you are located
Increase to 1500 ms or even more if you are using a lower quality internet connectivity or delivering to a cloud region located very far from where you are
The SRT latency can be configured independently for each source and each destination. This means that you can optimize the distribution independently for each destination, based on different network conditions
Troubleshoot the SRT latency
Once you create a source or a destination in a region, having a look at the SRT statistics is key to understand whether the connection quality is good or not.
The "SRT Dropped Packet" should always be null or very low, as it counts the number of lost packets after the SRT recovery took place (hence, it basically counts the number of unrecoverable packets). Having too many dropped packet is a clear indication that the link quality is low. You should increase the SRT latency in this case. Increasing the latency will give more room to the SRT protocol to recover packets, and is likely to reduce the amount of dropped packets.
The SRT "Round Trip Time" is also very important and can give you a very valuable hint on how to adjust the "latency" setting of your SRT stream. A good rule of thumb is that your SRT latency should be at least 3 to 4 times higher than the RTT.
Updated on: 01/03/2024
Thank you!