-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Single effect chains not visible after first start in effects_refactoring branch #10569
Comments
Commented by: Be-ing What do you mean? Where are they not shown? Please post a screenshot. |
Commented by: Be-ing I cannot reproduce this after |
Commented by: ronso0 Oh, they do show up after pressing Reset To Defaults, both in the preferences and in the selector in the skin. |
Commented by: Be-ing It's possible you have some weird state in ~/.mixxx/effects or ~/.mixxx/effects.xml from testing an earlier development version. Mixxx must not override the user's modified state with default settings unless the user presses Reset To Defaults in the preferences. Please test again after running |
Commented by: ronso0 I removed the effects folder for a clean start. 100% reproducible. |
Commented by: Be-ing Did you remove effects.xml too or just the effects directory? |
Commented by: ronso0 true, the effects.xml needs to be removed, too. Thought that was the one from main. |
Commented by: daschuer I have started Mixxx with a completely fresh preferences folder and I cannot longer reproduce the issue. So I think the issue is the same ronso0 describes. |
Commented by: Be-ing If the issue can be reproduced by upgrading settings from Mixxx 2.3 then there is a bug. Otherwise there is no problem. |
Commented by: daschuer Did you change something lately, that make the preset incompatible? However I have switched between 2.3 main and this branch many times. This will be the common case for many contributors after merge like rons0 so I do not longer consider this bug as invalid. |
Commented by: Be-ing The XML format for the presets has not been changed recently, at least not intentionally. |
Commented by: Be-ing I tested creating new settings directories with 2.3 then using it with effects_refactoring and could not reproduce this. I also could not reproduce it with a fresh settings directory created by the main branch. |
Commented by: daschuer It is normal in such cases that the original author is not able to reproduce it. Ronso0 and I experienced the issue and when have no explaination why. Please reconsider your latest status change. |
Commented by: ronso0 For me, the issue vanished when I also deleted effects.xml which I have been using for testing 2.3.x, various PRs targeting main as well as the effects_refactoring branch. If we approach the issue from the other side: |
Commented by: daschuer Could it be caused by a previous debug assert crash? What is the rule that creates these chains? |
Commented by: Be-ing
I presume you mean the autogenerated chain presets with a single effect. Those would not be added to the chain preset lists if effects.xml has a list that does not include them. |
Commented by: daschuer There is something fishy we need to investigate. I have set this to confirmed that it does not fall from the shelf. |
Commented by: Be-ing There is nothing to investigate if it cannot be reproduced. |
Commented by: daschuer We have two reports confirming the issue. This is sufficient to put a bug into a confirmed state.
For my understanding the opposite is true, to deliver a rock solid software. |
@daschuer I understand your position here, but there have been a few instances where you'd prefer to keep a bug open that we cannot even reproduce. These bugs clutter up the bug system and make it hard to know what are even real problems and what was a one-time mistake. For cases like these, where years have gone by and nobody can reproduce the issue, we should close the bug. If, one day, someone finds this problem again, we can reopen the bug easily and we'll still have all of the discussion recorded. Closing this bug as non-reproducible until someone can come up with a predictable way to reproduce it. |
fixing status |
Reported by: daschuer
Date: 2021-10-19T23:15:14Z
Status: Confirmed
Importance: Medium
Launchpad Issue: lp1947807
Single effect chains are created during the first start of Mixxx.
However they are not shown in the Effect preferences.
A restart of Mixxx fixes the issue.
The single effect chains should be visible instantly after start.
The text was updated successfully, but these errors were encountered: