A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/Haivision/srt/commit/a58af53b41fa3f34a9bfe479ea74b9a6a827f731 below:

[docs] Fixed retransmitalgo naming plus added the link for Medium art… · Haivision/srt@a58af53 · GitHub

File tree Expand file treeCollapse file tree 1 file changed

+5

-3

lines changed

Filter options

Expand file treeCollapse file tree 1 file changed

+5

-3

lines changed Original file line number Diff line number Diff line change

@@ -1268,13 +1268,15 @@ procedure of `srt_bind` and then `srt_connect` (or `srt_rendezvous`) to one anot

1268 1268 1269 1269

An SRT sender option to choose between two retransmission algorithms:

1270 1270 1271 -

- 0 - an intensive retransmission algorithm (default until SRT v1.4.4), and

1272 -

- 1 - a new efficient retransmission algorithm (introduced in SRT v1.4.2; default since SRT v1.4.4).

1271 +

- 0 - aggressive retransmission algorithm (default until SRT v1.4.4), and

1272 +

- 1 - efficient retransmission algorithm (introduced in SRT v1.4.2; default since SRT v1.4.4).

1273 1273 1274 -

The intensive retransmission algorithm causes the SRT sender to schedule a packet for retransmission each time it receives a negative acknowledgement (NAK). On a network characterized by low packet loss levels and link capacity high enough to accommodate extra retransmission overhead, this algorithm increases the chances of recovering from packet loss with a minimum delay, and may better suit end-to-end latency constraints.

1274 +

The aggressive retransmission algorithm causes the SRT sender to schedule a packet for retransmission each time it receives a negative acknowledgement (NAK). On a network characterized by low packet loss levels and link capacity high enough to accommodate extra retransmission overhead, this algorithm increases the chances of recovering from packet loss with a minimum delay, and may better suit end-to-end latency constraints.

1275 1275 1276 1276

The new efficient algorithm optimizes the bandwidth usage by producing fewer retransmissions per lost packet. It takes SRT statistics into account to determine if a retransmitted packet is still in flight and could reach the receiver in time, so that some of the NAK reports are ignored by the sender. This algorithm better fits general use cases, as well as cases where channel bandwidth is limited.

1277 1277 1278 +

To learn more about the algorithms, read ["Improving SRT Retransmissions — Experiments with Simulated Live Streaming (Part 1)"](https://medium.com/innovation-labs-blog/improving-srt-retransmissions-experiments-with-simulated-live-streaming-part-1-7d192483bba4) article.

1279 + 1278 1280

NOTE: This option is effective only on the sending side. It influences the decision

1279 1281

as to whether a particular reported lost packet should be retransmitted at a

1280 1282

certain time or not.

You can’t perform that action at this time.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4