-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SERIOUS 2.3 AUTOPLAY ISSUES IN UBUNTU #10515
Comments
Commented by: Be-ing
|
Commented by: 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. |
Commented by: 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? |
Commented by: darrenitu I suggest you change your approach and attitude FAST. Who do you think you At least link to a guide of how I can successfully reinstall 2.2.4 in What a shame. I had a lot of time for Mixxx and have spent years promoting On Mon, 6 Sept 2021 at 15:30, Be wrote:
|
Commented by: Holzhaus
The first bug report was made a week ago (and by Uwe, not you): https://bugs.launchpad.net/mixxx/+bug/1941989
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. |
Commented by: darrenitu There was no shouting in my message, in fact it was quite jovial and Don't bother responding unless it's to point me to your boss.
|
Commented by: Holzhaus
This is not how Be and me interpreted the message, and I think most people would see all uppercase sentences that way.
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? |
Commented by: uklotzde 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. |
Commented by: darrenitu What we have here is a case of "shoot the messenger". You have a seriously So fix it or don't. I simply don't care anymore, we'll find something else On Mon, 6 Sept 2021 at 20:25, Uwe Klotz wrote:
|
Commented by: 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... |
Duplicate of #10505 |
Reported by: darrenitu
Date: 2021-09-06T13:55:36Z
Status: New
Importance: Undecided
Launchpad Issue: lp1942782
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:
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.
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!
The text was updated successfully, but these errors were encountered: