SERIOUS 2.3 AUTOPLAY ISSUES IN UBUNTU

[Darren Smithson]

Hi guys! Long time no speak, but we have some real issues with Ubuntu v20 and Mixxx 2.3 that are causing some major problems with our stream.

The two issues are:

1. Autoplay track skip. autoplay jumps over tracks - in a one hour 13 track schedule for example, it skipped 5 of those tracks. In a long autoplay that can be issue enough if we run out of songs before one of us is around. But in a live show, at the end I usually play out on 3 live tracks and a handover mp3 so i can get a drink and a sandwich or go for a loo break. It will skip almost every time over 1 of those 3 tracks, meaning I cannot leave the room. I have checked every preference setting I can find, and checked/unchecked any new command that might be responsible, but to no avail.

2. More serious. Back when we first started using Mixxx, autoplay would fill up some memory log in Mixxx and it would crash. You fixed this issue following some work with us, as at the time we were the first to really use Mixxx for dedicated station autioplay, and in versions 2.2.1 to 2.2.4 we were quite happily running a 30 day autoplay (interrupted only for our live shows and then set back on). Now we are lucky if we get 3 days with 2.3. As you can imagine, we are often out when this crash occurs, meaning dead air time!

I have the same two issues on two different Ubuntu computers, running in two different locations. Furthermore, when I tried to reinstall 2.2.x, earlier Mixxx simply refuses to open, meaning I have to reinstall 2.3.

Please be aware also that I have done TWO complete delete and reformat to reinstall Ubuntu and Mixxx (with no other apps) on the server, with the same result.

PLEASE ADVISE URGENTLY!

Thanks and over to you!

[Be (be.ing)]

1. Please check for duplicates before reporting bugs.
2. Report every issue as a separate bug.
3. Using all caps is rude and, speaking for myself, demotivating to pay attention to the issues you're experiencing.

[Darren Smithson (darrenitu)]

Firstly, I have asked THREE times for this to be resolved. Hence the CAPs in the title this time.

Secondly, I did a search for autoplay issues in Ubuntu Mixxx V2.3 and no duplicates came up in the results. hence my doing a separate post. If this bug has been fixed elsewhere perhaps you would be good enough to show me where.

Thirdly, BOTH issues are a BUG with Autoplay, not two separate issues, but related to autoplay.

Way to go to hack off a long time user who has promoted Mixxx for years on his radio station.

[Darren Smithson (darrenitu)]

And when I go to the links of reports of this bug, I see people logged both issues as I have. And what's more, after ELEVEN months you have actually provided NO solution.

What is going on with Mixxx????? When did you change from being a user-focused entity into rushing out platforms as "stable" when clearly they are not, and then attacking users when they need answers?

[Darren Smithson (darrenitu)]

I suggest you change your approach and attitude FAST. Who do you think you
ARE and who do you think you are dealing with? Shocking response and as a
developer, you should be ashamed that after 11 months you have provided no
solution to two issues that mean your product is anything but stable for
live streaming.

At least link to a guide of how I can successfully reinstall 2.2.4 in
Ubuntu!

What a shame. I had a lot of time for Mixxx and have spent years promoting
the platform. Not any more.

On Mon, 6 Sept 2021 at 15:30, Be <email address hidden> wrote:

> *** This bug is a duplicate of bug 1941989 ***
> https://bugs.launchpad.net/bugs/1941989
>
> ** This bug has been marked a duplicate of bug 1941989
> AutoDJ skips scheduled tracks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1942782
>
> Title:
> SERIOUS 2.3 AUTOPLAY ISSUES IN UBUNTU
>
> Status in Mixxx:
> New
>
> Bug description:
> Hi guys! Long time no speak, but we have some real issues with Ubuntu
> v20 and Mixxx 2.3 that are causing some major problems with our
> stream.
>
> The two issues are:
>
> 1. Autoplay track skip. autoplay jumps over tracks - in a one hour 13
> track schedule for example, it skipped 5 of those tracks. In a long
> autoplay that can be issue enough if we run out of songs before one of
> us is around. But in a live show, at the end I usually play out on 3
> live tracks and a handover mp3 so i can get a drink and a sandwich or
> go for a loo break. It will skip almost every time over 1 of those 3
> tracks, meaning I cannot leave the room. I have checked every
> preference setting I can find, and checked/unchecked any new command
> that might be responsible, but to no avail.
>
> 2. More serious. Back when we first started using Mixxx, autoplay
> would fill up some memory log in Mixxx and it would crash. You fixed
> this issue following some work with us, as at the time we were the
> first to really use Mixxx for dedicated station autioplay, and in
> versions 2.2.1 to 2.2.4 we were quite happily running a 30 day
> autoplay (interrupted only for our live shows and then set back on).
> Now we are lucky if we get 3 days with 2.3. As you can imagine, we are
> often out when this crash occurs, meaning dead air time!
>
> I have the same two issues on two different Ubuntu computers, running
> in two different locations. Furthermore, when I tried to reinstall
> 2.2.x, earlier Mixxx simply refuses to open, meaning I have to
> reinstall 2.3.
>
> Please be aware also that I have done TWO complete delete and reformat
> to reinstall Ubuntu and Mixxx (with no other apps) on the server, with
> the same result.
>
> PLEASE ADVISE URGENTLY!
>
> Thanks and over to you!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1942782/+subscriptions
>
>

[Jan Holthuis (holthuis-jan)]

> I have asked THREE times for this to be resolved. Hence the CAPs in the title this time.
> [...]
> And what's more, after ELEVEN months you have actually provided NO solution.

The first bug report was made a week ago (and by Uwe, not you): https://bugs.launchpad.net/mixxx/+bug/1941989

> I suggest you change your approach and attitude FAST. Who do you think you
> ARE and who do you think you are dealing with? Shocking response and as a
> developer, you should be ashamed that after 11 months you have provided no
> solution to two issues that mean your product is anything but stable for
> live streaming.

Sorry, but I think *you* should overthink *your* attitude. Mixxx is an open source project. We have absolutely no paid staff. Every developer works on Mixxx in his/her free time. It's not exactly motivating to come home after work, open the Mixxx bug tracker and be virtually shouted at.

I understand that bugs are annoying, but Mixxx is open source. We cannot force anyone to work on a specific issue in his or her spare time (especially if nobody files a bug reporrt for 11 months). If think it takes too long for us to fix it, you can just download the source code and fix it yourself, then share the fix with others. This is how our development model works and exactly what we are doing, too.

[Darren Smithson (darrenitu)]

There was no shouting in my message, in fact it was quite jovial and
engaging. You decided to take umbrage at the title, that's down to you. A
proper read of the message itself would have set that straight. The fact is
that lack of a reliable autoplay is a serious issue, as is the crashing
whilst in autoplay. A search did NOT yield results of multiple threads, so
I reported for a third time the issues after getting no response from 3
emails. The threads you sent me to had no answers or even etas. And some of
them are dated much longer than a week ago. All you had to do was say "hi,
yep, we're aware of it from other reports and we're dealing with it. Please
see this thread for updates." Instead you tried to be clever and throw some
kind of forum weight around. I'm the wrong person and the wrong age for
that kind of attitude. And as I said, nice one for turning a long time ally
of Mixxx into a disgruntled enemy.

Don't bother responding unless it's to point me to your boss.

On Mon, 6 Sept 2021 at 18:10, Jan Holthuis <email address hidden>
wrote:

> *** This bug is a duplicate of bug 1941989 ***
> https://bugs.launchpad.net/bugs/1941989
>
> > I have asked THREE times for this to be resolved. Hence the CAPs in the
> title this time.
> > [...]
> > And what's more, after ELEVEN months you have actually provided NO
> solution.
>
> The first bug report was made a week ago (and by Uwe, not you):
> https://bugs.launchpad.net/mixxx/+bug/1941989
>
> > I suggest you change your approach and attitude FAST. Who do you think
> you
> ARE and who do you think you are dealing with? Shocking response and as a
> developer, you should be ashamed that after 11 months you have provided no
> solution to two issues that mean your product is anything but stable for
> live streaming.
>
> Sorry, but I think *you* should overthink *your* attitude. Mixxx is an
> open source project. We have absolutely no paid staff. Every developer
> works on Mixxx in his/her free time. It's not exactly motivating to come
> home after work, open the Mixxx bug tracker and be virtually shouted at.
>
> I understand that bugs are annoying, but Mixxx is open source. We cannot
> force anyone to work on a specific issue in his or her spare time
> (especially if nobody files a bug reporrt for 11 months). If think it
> takes too long for us to fix it, you can just download the source code
> and fix it yourself, then share the fix with others. This is how our
> development model works and exactly what we are doing, too.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1942782
>
> Title:
> SERIOUS 2.3 AUTOPLAY ISSUES IN UBUNTU
>
> Status in Mixxx:
> New
>
> Bug description:
> Hi guys! Long time no speak, but we have some real issues with Ubuntu
> v20 and Mixxx 2.3 that are causing some major problems with our
> stream.
>
> The two issues are:
>
> 1. Autoplay track skip. autoplay jumps over tracks - in a one hour 13
> track schedule for example, it skipped 5 of those tracks. In a long
> autoplay that can be issue enough if we run out of songs before one of
> us is around. But in a live show,...

[Jan Holthuis (holthuis-jan)]

> There was no shouting in my message, in fact it was quite jovial and
engaging.

This is not how Be and me interpreted the message, and I think most people would see all uppercase sentences that way.

> A
proper read of the message itself would have set that straight.
> [...]
> Don't bother responding unless it's to point me to your boss.

If you had read my message properly, you'd be aware that my boss has probably never heard of Mixxx. The same goes for any other dev because *all* Mixxx developers are volunteers that contribute in their free time.

Please read your your own posts again and try to put yourself into the shoes of a volunteer that receives such messages. Would you be motivated to invest your spare time to work on it?

[Uwe Klotz (uklotzde-deactivatedaccount)]

Even as a user and not as a developer you could help. Mixxx 2.3 was in beta for 1 year and no one cared to properly test if their use cases still work and there are no regressions with AutoDJ. We didn't receive a single bug report about this issue before the release.

This bug could have been a release blocker. But now we just have to wait until someone invests their spare time to find and fix this bug.

I care for bugs. But I refuse to spend any time for someone who condemns me and my team.

[Darren Smithson (darrenitu)]

What we have here is a case of "shoot the messenger". You have a seriously
flawed autoplay, and this is mission critical not just for us and other
radio shows, but for YOUR platform. That's why I flagged it up. For your
information, I searched for forum first and nothing came up which is why I
then raised the report. I am sorry if being told your product was flawed
made you all twitchy. The fact is. there is nothing wrong with my message.
I used caps in the heading cos I thought it was important that you knew- we
have promoted MIXX for years and didn't want this bad bug to give the
product a bad name. The email itself IS jovial and reports the facts. The
response was totally uncalled for.

So fix it or don't. I simply don't care anymore, we'll find something else
to use.

On Mon, 6 Sept 2021 at 20:25, Uwe Klotz <email address hidden> wrote:

> *** This bug is a duplicate of bug 1941989 ***
> https://bugs.launchpad.net/bugs/1941989
>
> Even as a user and not as a developer you could help. Mixxx 2.3 was in
> beta for 1 year and no one cared to properly test if their use cases
> still work and there are no regressions with AutoDJ. We didn't receive a
> single bug report about this issue before the release.
>
> This bug could have been a release blocker. But now we just have to wait
> until someone invests their spare time to find and fix this bug.
>
> I care for bugs. But I refuse to spend any time for someone who condemns
> me and my team.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1942782
>
> Title:
> SERIOUS 2.3 AUTOPLAY ISSUES IN UBUNTU
>
> Status in Mixxx:
> New
>
> Bug description:
> Hi guys! Long time no speak, but we have some real issues with Ubuntu
> v20 and Mixxx 2.3 that are causing some major problems with our
> stream.
>
> The two issues are:
>
> 1. Autoplay track skip. autoplay jumps over tracks - in a one hour 13
> track schedule for example, it skipped 5 of those tracks. In a long
> autoplay that can be issue enough if we run out of songs before one of
> us is around. But in a live show, at the end I usually play out on 3
> live tracks and a handover mp3 so i can get a drink and a sandwich or
> go for a loo break. It will skip almost every time over 1 of those 3
> tracks, meaning I cannot leave the room. I have checked every
> preference setting I can find, and checked/unchecked any new command
> that might be responsible, but to no avail.
>
> 2. More serious. Back when we first started using Mixxx, autoplay
> would fill up some memory log in Mixxx and it would crash. You fixed
> this issue following some work with us, as at the time we were the
> first to really use Mixxx for dedicated station autioplay, and in
> versions 2.2.1 to 2.2.4 we were quite happily running a 30 day
> autoplay (interrupted only for our live shows and then set back on).
> Now we are lucky if we get 3 days with 2.3. As you can imagine, we are
> often out when this crash occurs, meaning dead air time!
>
> I have the same two issues on two different Ubuntu computers, running
> in two different locations. Furtherm...

[ronso0 (ronso0)]

Rtaher than making up 'autoplay' you could have used the actual name of the feature as it visible in the GUI (Auto DJ) and you would have found enough recent forum threads on that exact issue. Maybe then you'd also have noticed that we're aware and that these are medium/high prio bugs, and that it's a pity no user reported those during the rather long 2.3 beta period.

would, could, should...
Shooting messengers is kinda pointless for a project that is primarily based on user feedback.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/10515