Quote:
Originally Posted by mschnell
Dud you take a look at the XControl compact ?
Faders have just numbers 1 .. 9.
Rotaries also have just numbers (1 .. 16)
Most buttons have no names.
some have unprintable symbols.
I suggest using
F1 ... F9 for Faders
FP1 ... FP9 for Fader Touch
R1 ... R15 for Rotaries
RP1 ... RP15 for rotary Push
BA1 ... BA8, BB1 ... BB8, BC1 ... BC8, BD1 ... BD9, BE1 ... BE2, BF1 ... BF2, BG1 ... BG2, BH1 ... BH2 for Buttons (the two "H" buttons are not accessible in the current firmware release)
-Michael
|
Yeah, that one does require some thinking
Of course you are free to map any way you wish with any widget, anytime.
However, the new design requires naming conventions to facilitate sharing templates.
Yes, it is not perfect.
Yes, there will be issues.
The hope is overall we do OK.
So, in that vain, I would do the following:
I would just take a stock MCUStrip.rst template, automatically giving you:
Rotary
RotaryPush
RecArm
Solo
Mute
Select
Fader
FaderTouch
I would then add an MCUTransport.rst giving you:
Rew
FF
Stop
Play
Rec
To complete your setup you would have to manually map:
Loop
and the Rotaries, which I would name:
RotaryA1
RotaryA2
RotaryB1
RotaryB2
RotaryC1
RotaryC2
RotaryD1
RotaryD2
and:
RotaryA1Push
RotaryA2Push
RotaryB1Push
RotaryB2Push
RotaryC1Push
RotaryC2Push
RotaryD1Push
RotaryD2Push
Voila, you're up and running, now you can take time, get used to using it, and change whatever you want, as you incorporate it into your workflow.