Comment 18 for bug 1623620

We are testing it tomorrow (Monday)- we had too many live shows on last
week to fit it in. But have scheduled it for tomorrow from 11am.

On 18 November 2016 at 19:19, Daniel Schürmann <email address hidden>
wrote:

> Darren, do you have a log from the new builds for us?
>
> --
> 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
>