Player Stuck in Buffering State for Audio Stream

[wajidp]

Discontinuity detected [expected 12613060, got 12189160]
Am getting this buffering problem frequently Sometimes it recovers but most of the times doesn't. Am using 1.5.8.

http://stream.peaceradio.com:8000/aacsblow

[andrewlewis]

How frequently do you see the discontinuity logging? I haven't been able to reproduce the issue so far, having left the stream playing for 10 minutes.

[wajidp]

Its happening too frequently,It usually happens in mobile networks but you can reproduce the same issue by turning off the wifi and on again.

[andrewlewis]

This looks the same as #1285. Did you try the workaround there?

[wajidp]

There is audio slutter for the mentioned temporary fix changing the minimum re buffer to 0, still there is no proper permanent fix for this, its effecting the users in low bandwidth network heavily.

[ojw28]

Users with insufficient bandwidth are going to get re-buffering every ~5 seconds or so anyway, even with a permanent fix. So it's not like a permanent fix is going to solve the problem for this class of users. If they fundamentally don't have sufficient bandwidth for the stream, it's not going to play without interruption.

I think (although I'm not 100% certain) this is fixed in a more satisfactory way in 2.x, but it'll be at least another few weeks until we start pushing this version to GitHub, and we have no plans to backport a fix to the current release.

[wajidp]

My problem is the stream is not coming back even in sufficient bandwidth, and how can i use in 2.x version as am using r1.5.8 in my gradle

[ojw28]

If you use the temporary fix as described in #1285 then the stream will come back. If you don't then it might not, as is clearly documented on that issue. I'm not really sure what your question is. We're going to implement a more permanent fix in 2.x. It's not available on Github yet. Even the permanent fix wont allow users with insufficient bandwidth to play content without interruption.

[ttencate]

For those who found this issue through a search engine: if I'm not mistaken, that "more permanent fix in 2.x" is now on GitHub in the dev_v2 branch: 90b7081