Extended Mapping

[krimen_sp]

Hello, First I have to greet the developers for the new scratching algorithm, because the old one was not very good and the new one (1.10) is great!

I have an Idea for future versions.


It would be nice to include flags in the mapping, to be able to change controller keys functionality depending on the flags

I own a vestax vci-100, and now I cant acces to hotcues from it since the mapping in mixxx does not let me change the keys function depending on a flag.

The process would be the following:

- I have a controler key assigned to a flag (example: If key_is_pressed; flag_a=1; else flag_a=0)
- all the mapping lines contain a column for each flag
example:

MIDI note | Flag_a | Flag_b | Flag_c | Action | value
--------------------------------------------------------------------------------
0x16 | 1 | 0 | 0 | Flag_a | 1 (flag_a=1)
--------------------------------------------------------------------------------
0x16 | 1 | 0 | 0 | hotcue1_deck | 1 (on deck 1)
--------------------------------------------------------------------------------
0x16 | 0 | 0 | 0 | play_deck | 2 (on deck 2)

(if flag_a...)
(if flag_b...)
(if flag_c...)

having 2 o 3 system flags it would be possible to change the functionality of the mapping completely


This is a feature that so far only traktor includes, and by allowing key mapping functionality change, Mixx could give a big step.

ps: I would contribute but my level of C++ programing is null

[Pegasus]

You can do this already with scripting, which has been present since Mixxx 1.7.0. It takes a bit more work than a simple mapping but allows you complete control of how the controller works.

You would map your flag/shift button to a script function that sets a global state variable when the button is pressed, and clears it when the button is released. Then in the other functions for other buttons, they check to see if that variable is set or not and do something different depending on that.