+3
Under review

Retry with ascending time interval.

Arrowcatcher 8 years ago • updated by Jona (Lead Developer) 8 years ago 1
Rather than give up after 6 quick retries, it may be more convenient to have retry continue at longer and longer time intervals. This would help greatly when the app is used to stream in a moving auto. The present retry setup sometimes gives up before a network site handoff can occur, requiring the distraction of a manual restart.

Answer

Answer
Under review
Current design loops around a whole playlist 5 times. So if the playlist has only one url it only will retry 5 times, and if it had 5 urls it will retry 25 times. If after any count of retries and it successfully reconnects we reset the amount of retries and you get 5 retries again.

We will review the possibility to allow unlimited retries as an option.
Answer
Under review
Current design loops around a whole playlist 5 times. So if the playlist has only one url it only will retry 5 times, and if it had 5 urls it will retry 25 times. If after any count of retries and it successfully reconnects we reset the amount of retries and you get 5 retries again.

We will review the possibility to allow unlimited retries as an option.
I listen to classical music and want to stay with the same one station, i.e., playlist=1. Having to restart after the 5 quick retries is a hassle, if not hazardous, when driving. My news reader uses ascending time intervals, and that may be practical here. I dunno. I do know that 5 fast retries is not enough to cover some percentage of tower hand offs in the car.