switch decks that a controller manipulates without having to edit XML or JS

[Be]

It would be convenient if the decks that controllers manipulate could be changed from the controller settings in the preferences. This would be particularly useful now that Mixxx supports 4 decks because most controllers are designed for controlling only 2 decks. With this functionality, users could easily use two different controllers with each controller assigned to 2 of Mixxx's decks.

[Daniel Schürmann (daschuer)]

I think we have discussed it some times ago. I cannot find it yet.
We need and additional mapping layer, that maps deck COs to controller COs.

Related: We may also utilize the shift key, featured on sum controllers:
Bug #1398428

[Sébastien BLAISOT (sblaisot)]

I think the problem is a bit more complicated and specifications should be more discussed.

There is not only the ChannelX groups/sections. What about [master] and [playlist] controls that can be present on the two controllers ? (may also apply to effects, microphone, samplers, etc..., I don't know exactly by now what is the exact list of sections)

Probably crossfader can not be activated on the two controllers at the same time or you will always have on of the crossfader not in sync with the other and Mixxx interface. should we deactivate the [master] section of one controller ? so we need to be able to chose in preferences the controller on which the [master] will be deactivated.

On the other hand, It could lead to additionnal buttons/knobs/whatever that are redundant between two controller and you can use for other controls. Why not let the controller xml files define a primary (when master) and a secondary command for each button ?

In this cases, we need to :
- have a way for xml files to say how many channel they use
- let user assign each channel to a controller channel (which controller and which channel of that controller)
- let user choose which controller hold master, playlist, etc... sections/groups
- have a way in xml file to define the buttons primary assignation for master, etc... sections and other assignation if the controller doesn't have the "master", ... function

this way, you can imagine using four 1-channel controllers (one for each deck) and a "master" controller for mixing and common commands (but it seems to be an expensive setup).

[Be (be.ing)]

I think the most intuitive way to go about this would be implementing an abstraction for [ChannelX] that mapping files would use rather than [Channel1] ... [Channel4]. Some names I propose for these abstractions are [ChannelA/B/C/D], [ControllerChannelA/B/C/D], and [ControllerChannel1/2/3/4]. Which decks these abstractions map to could be selectable by users in the preferences. If scripts could change this too, it would be really easy to implement deck toggle buttons.

[Daniel Schürmann (daschuer)]

Related https://bugs.launchpad.net/bugs/1398428

[Be (be.ing)]

With a controller preference system this would be easy.

[Swiftb0y (swiftb0y)]

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