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

Sound Hardware preferences should auto-select next free channel #10163

Open
mixxxbot opened this issue Aug 23, 2022 · 2 comments · Fixed by #11859
Open

Sound Hardware preferences should auto-select next free channel #10163

mixxxbot opened this issue Aug 23, 2022 · 2 comments · Fixed by #11859

Comments

@mixxxbot
Copy link
Collaborator

Reported by: Holzhaus
Date: 2020-10-13T22:39:15Z
Status: Confirmed
Importance: Low
Launchpad Issue: lp1899703
Tags: easy, preferences, usability


When configuring sound hardware in the preferences, Mixxx currently always assigns the first channel of a soundcard to every input or output instead of using the next free available channel.

For example, if you want to configure the main and headphones output, the workflow is the following

  1. Select soundcard A in the main output's soundcard combobox. The channel combobox automatically picks channels 1-2.
  2. Select soundcard A in the headphone output's soundcard combobox. The channel combobox automatically picks channels 1-2. (the configuration is now invalid because both outputs use the same channels)
  3. Select channels 3-4 in the headphone output's channel combobox.

Mixxx should automatically pick channels 3-4 in step 2, because channels 1-2 are already in use. That would make step 3 unnecessary.

@Rohan-Dah
Copy link

Heyy... Is this issue still open? I'll be happy to work on it...

@daschuer
Copy link
Member

daschuer commented Mar 7, 2023

Yes. just try it out. If you are on it a review about the whole first time user experience would be also nice. Maybe you find related issues that you can file in an here like this. Thank you.

@ronso0 ronso0 linked a pull request Aug 24, 2023 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants