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

Automatically detect optimal waveform settings (wizard) #8639

Open
mixxxbot opened this issue Aug 22, 2022 · 3 comments
Open

Automatically detect optimal waveform settings (wizard) #8639

mixxxbot opened this issue Aug 22, 2022 · 3 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: Pegasus-RPG
Date: 2016-09-07T15:35:25Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp1621141
Tags: preferences, waveform


It can be confusing for new users to know what waveform settings to use. I propose adding a simple auto-detection process that basically automates current best-practice:

  1. Try each available waveform option for a few seconds each in succession with frame rate slider at max, noting frame rates.
  2. Select the one that provides the highest frame rate.
  3. Lower the slider little by little until there are no (or minimal) dropped frames.

This should run silently and automatically at first-run (i.e. no Mixxx preferences found,) and should be available to re-run from the Waveform preferences pane.

After this is in place, we should separate the waveform options into appearance (RGB, HSV, Filtered, etc.) and rendering method (software, GL, etc.) so that users can choose the appearance they like and let the wizard determine the best rendering method.

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2017-04-18T15:05:02Z


A quick bandage solution would be to present a dialog on first startup advising users to try the different renderers and adjusting the framerate.

@mixxxbot
Copy link
Collaborator Author

Commented by: pander
Date: 2017-04-18T15:44:04Z


Good default/suggestion for PINE64 at the moment (missing GPU acceleration) is RGB with Filtered.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2017-04-18T19:50:00Z


What happens with the default settings on the PIN64?
Do we have a chance to detect it and fall back to RGB with Filtered?
Could you provide a mixxx.log file from such faulty first start or in case of a crash a backtrace?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant