Mixxx should remember multiple audio configurations

[Owen Williams]

I don't always use mixxx the same way. Sometimes I launch it with no controller attached so I can manage my library. Sometimes I use my big controller. Sometimes I use my small controller. Unfortunately, mixxx only ever remembers a single audio setup, so when I launch it the program is likely to complain that it can't find the right audio device.

I propose an enhancement to have Mixxx remember multiple audio configurations and pick the right one on startup.

Storing multiple configurations won't be hard. The soundconfig.xml file could be extended to record more than one setuop. The tricky part is how to decide which configuration to pick. I think the best solution is to have mixxx say "given a list of presently-available audio devices, which does the user choose?" For instance, when my internal soundcard is the only option, I pick that. So the mapping is [internal] -> [internal]. But when I attach my controller, now mixxx sees my internal soundcard and the controller. In this setup, I always choose the controller sound card. So the mapping is: [internal, controller] -> [controller].

This wouldn't be right 100% of the time but it would be correct a lot more often.

[Daniel Schürmann (daschuer)]

Unfortunately there is an underlying portaudio issue that Mixxx can't even store one setting.
I think we have a bug for this.
Ups, this is a duplicate.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/9627