Xone K2 effects mappings
Bug #1733218 reported by
Be
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Medium
|
Be |
Bug Description
We have a 4 deck mapping for the Allen & Heath Xone K2. We should have a 2 decks + 2 effect unit mapping as well as a 4 effect unit mapping.
Changed in mixxx: | |
milestone: | none → 2.1.0 |
Changed in mixxx: | |
importance: | Undecided → Medium |
assignee: | nobody → Owen Williams (ywwg) |
Changed in mixxx: | |
status: | In Progress → Fix Committed |
Changed in mixxx: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I've started refactoring the make_xone script to do this work. I am not sure what the best way is to map the effects units.
The xone has multiple configurations for how to configure the "layers." Depending how it's configured (hardware-side), the xone can either have three layers for just the buttons, or for all of the controls. For the original mapping, I have the user put the xone in the mode in which the just buttons at the bottom of the device can have three different functions depending what page the device is on.
But for FX, I could imagine using the mode where the knobs do different things on different pages. If each column is a separate effect unit, I'm thinking of mapping like this:
Red Page: Each knob is the Meat knob for each effect
Orange Page: Knobs are individual parameters for effect 1 of the chain
Green Page: Knobs are individual parameters for effect 2 of the chain
As for buttons:
Red Page: Enabling per-deck
Orange Page: Enabling per effect?
Green Page: ???
(We could also repeat bindings so every page has the same bindings for the buttons)
Sliders: dry/wet mix on all pages
spin knobs: chain selection
When doing 2 deck 2 fx I'll have to dupe all of the knobs on all the pages so the decks behave predictably.
(I could also imagine setting it up so that the whole Xone operates a single effect unit)