RFE: mapping MIDI knobs/faders to actions, per-session and per-plugin

[dmedri]

Hi, congrats for your incredible work on qtractor. From my point of view - a user focused on do-things at high level - there are few tips to enhance the usability of this app.

Platform: fedora 27, qtractor 0.8.5 MIDI device: Akai MPK mini 2

Problem: Of the available knobs for my device, only one (k7) can change volume settings. My single problem could generalized imho as follow:

• a manager to handle text files for MIDI devices and mapping configurations;
• these files should have some defaults for qtractor sessions and loaded plugins;
• customizations should be new text files.

Hope this helps.

[rncbc]

probably already landed there for years -- see View > Controllers... -- these refer to generic application-wide parametric MIDI controller assignments to track controls: volume, pan, monitor, record, solo, mute.

all edited configuration and mappings maybe saved/loaded to/from file (*.qtc);

[dmedri]

The View > Controllers is really low level and ask a many technically notions. It should be the edit stage for customizations. Lets me explain: how many top-rate MIDI device we have now on market? How many of these we will have next 10 years? ~10-40 mapping text files. In other terms, when I plug an Akai mpk mini 2 I should find his name in a list, with refs for the available 25 keys, 8 pad (x2 banks), 8 knobs. [1]

I'm sure this could be an ui/ux plus, a step before your powerful view>controllers configurator, with some really valuable defaults.

[1] a clone of akai editor exists, but is strictly close to that device https://github.com/PiOverFour/MPK-M2-editor

[dmedri]

Obviously -- with the minimal impact on your code and time -- an intermediate step could be a distribution of .qtc files, per-device.