You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think once autostart is implemented for the stream, this becomes de facto rather obsolete.
For autostart, buffering could be prioritized before the loading of other components,
so by the time the page is displayed, buffer is full and can play right away.
The problem is, once we load the buffer, there is no way to jump to current time. So it will always play from the moment we loaded the buffer.
The only possibility is to clear the buffer and reload a new one if you want to jump to current time. So preloading doesnt work afaik.
The alternative would be to always play the audio and just mute it. But I wouldn't recommend it as some have limited data plans.
I mean just to start buffering & play while the page loads,
so users don't need to click the play button, or rather just use it to stop the sound if they like to.
That'd avoid much of the confusion users reported that they didn't know whether there is a stream or not, because they probably kept re-clicking before the Buffer was full.
so, with both autostart and Loading message, we shd be on the safe side.
The text was updated successfully, but these errors were encountered: