Comment 12 for bug 1623620

Hi Daniel, I am unsure what you mean by the buffer in hardware preferences?
Do you mean preferences in Mixxx or in Windows? Under Mixxx it is set to
92.2ms? I have attached an image of my settings (Mv2.0)- which is the same
for all our Mixxx setups and one of the underflow counter you refer to
(also from 2.0).

We will try and replicate the stop loading in the alpha but as I say the
main problem 99.9% of the time is the disconnect.

Cheers!

On 9 November 2016 at 10:48, Daniel Schürmann <email address hidden>
wrote:

> OK, so we can sort out the ISP and other Applications.
>
> It looks like Mixxx itself is not able to empty the network buffer in
> time. However the issue starts slowly and Mixxx is always able to pass some
> samples to the network (see attached graph).
> So it is not a deadlock. It is more a "slow down issue".
>
> What is your buffer size in hardware preferences? Does your under-run
> counter at the bottom of the hardware preferences count?
>
> ###
>
> The "stop loading" issue is tracked here
> https://bugs.launchpad.net/mixxx/+bug/1525738
>
> Since we have actually fixed one deadlock issue since 2.0:
> https://bugs.launchpad.net/mixxx/+bug/1565382 it is very important for us
> to know, if it ever happens with Mixxx 2.1 alpha, that a single deck just
> refused to load a track. Are you able to confirm this?
> If you manage to reproduce it with Mixxx 2.1 alpha a mixxx.log would be
> very helpful.
>
> This bug might be also related to
> https://bugs.launchpad.net/mixxx/+bug/1445298
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1623620
>
> Title:
> TWO SERIOUS BUGS in Mv2 (cache management maybe?)
>
> Status in Mixxx:
> Confirmed
>
> Bug description:
> Ok guys, we've been using Mv2 extensively now for several months and
> there are two serious issues that need fixing urgently.
>
> 1. Memory cache issue. If you play a long track- for example a 90
> minute radio play- (or several long tracks) and then attempt to load
> another, Mixxx simply stops broadcasting. Sometimes it doesn't TELL
> you it has, but mostly it just locks. It will also eventually just
> lock or throw off stream after several days of playing even if there
> have been no long tracks.
>
> 2. Any weakness in internet connection causes it to disconnect stream-
> even a nano second of fluctuation. For example, if I am broadcasting
> at 5pm and my neighbours get home and start to check their emails etc,
> there is a momentary drop in MY bandwidth as supplied by the ISP. This
> causes Mixxx to drop the stream. Every time.
>
> Note- we are 4 users all living in different areas, all on different
> ISPs, all on different computers. The only common ground is Windows
> 10.
>
> We LOVE Mv2 but the caching and robustness really needs sorting out
> urgently as we may be forced to replace it at our station (we would
> make a fab case study for you if you can make it work!).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1623620/+subscriptions
>