Hello Karol,
-
The player has a 19-20 seconds timeout while it is trying to download a segment. If the timeout is reached it will cancel the request and try to switch to the next lower representation/rendition. It repeats this until it has reached the lowest/smallest representation. Once it has reached this point it will just keep on downloading. It will not timeout anymore. The reason for this is that higher/better speeds might become available at any point.
-
If you want to implement a retry counter and base your handling logic around that then please have a look at the following Community post: Understand and customize Bitmovin Player's behavior when internet connection is lost
-
The reason why you are seeing infinite retries is the way you are testing this. The player implementation is such that if the domain was reachable for a previous request then it will keep trying and not actually error out. If the domain was never reachable it will error out. You can see this by doing the following: block the domain before the page is loaded and then load the page. You will see the player error. But if you block the domain during playback you will see it trigger a
stallstartedevent and then it tries to download the segment(s). This is as designed.
I hope the above helps you with your implementation. Have a great day!