Skip to content
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

Changing settings makes Mixxx unusable #10559

Closed
mixxxbot opened this issue Aug 23, 2022 · 5 comments
Closed

Changing settings makes Mixxx unusable #10559

mixxxbot opened this issue Aug 23, 2022 · 5 comments
Labels
Milestone

Comments

@mixxxbot
Copy link
Collaborator

Reported by: uklotzde
Date: 2021-10-14T20:56:41Z
Status: New
Importance: High
Launchpad Issue: lp1947201


This happens on main.

When changing any settings in the preferences dialog while tracks are playing and applying the changes Mixxx resets certain configurations to defaults and becomes unusable.

  • The Moog filter settings are reset to defaults as already reported on Zulip.
  • The tempo goes nuts, i.e. is raised by an unknown amount. This happens while playing a track when closing the dialog.

A restart is required to resolve the pitch/tempo issues. It happened with the JACK API, I need to repeat the test with ALSA.

Soundtouch v2.3.1 was used for time stretching at 0 pitch.

@mixxxbot mixxxbot added the bug label Aug 23, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2021-10-14T22:56:17Z


Are you using Rubberband or SoundTouch? Can you post a screenshot of your Decks settings? Maybe that issue is specific to one of the keylock/pitchshift options.

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2021-10-14T23:05:23Z


The Moog filter settings are reset to defaults as already reported on Zulip.

This is due to the hacky way LV2 effect parameter hiding is implemented. Unfixable without a complete rewrite of the effects system which has already been done #2618

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@daschuer daschuer added this to the 2.4.0 milestone Nov 25, 2022
@daschuer
Copy link
Member

@uklotzde can you confirm that this issue is completed in main?`

@uklotzde
Copy link
Contributor

uklotzde commented Jan 6, 2023

Didn't notice this anymore lately 🤷

@ronso0
Copy link
Member

ronso0 commented Jan 6, 2023

So we can consider this fixed by #4467

Reopen if it occurs again.

@ronso0 ronso0 closed this as completed Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants