View Single Post
Old 12-31-2017, 03:45 PM   #423
Geoff Waddington
Human being with feelings
Geoff Waddington's Avatar
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,090

Originally Posted by Freex View Post
I'm starting to understand the direction you guys a re coming at this, universal map vs surface specific map.

What if you had a term in the middle that was universal, that maps could be written in.
Fader1 = C1 = MCUfader1,

Maybe if on every device strating top left,
Pots were P,
Button/switches S
Faders F

So on a MCU and XT you'd have
Vpot(pan) P1-8
RecArm button S1-8
Solo button S9-16
Mute button S17-24
Select button S25-32
Faders F1-8

On C4
Vpot P1-32
Vpot(push) S1-32 (as the vpots are also buttons/swtiches.

Button S1-8
Faders F1-8
Vpot P1-8
Button S9-16

So a switch would always be a switch, a fader always a fader etc.

But for any fx you would get a working map, right out the box.
It might not be to your liking but it would be instantly usable.

Just trying to think outside the box.
It is most like completely impractical, just throwing to see if anything
Take a look at the following maps:

FXMap -- file is named
// Associate the widgets with FX params
Fader1 Threshold
Fader2 Gain
Fader6 Meter
Mute6 Bypass

FXMap -- file is named
// Associate the widgets with FX params
Fader3 LoFreq
Fader4 MidFreq
Fader5 HiFreq
Mute6 Bypass

Surface map named "MCU1"

// Name the widgets, state their type, and indicate which midi message they send
Fader1 Fader14Bit e0 7f 7f
Fader2 Fader14Bit e1 7f 7f
Fader3 Fader14Bit e2 7f 7f
Fader4 Fader14Bit e3 7f 7f
Fader5 Fader14Bit e4 7f 7f
Fader6 Fader14Bit e5 7f 7f
Fader7 Fader14Bit e6 7f 7f
Fader8 Fader14Bit e7 7f 7f

Fader1Touch PushButton 90 68 7f
Fader2Touch PushButton 90 69 7f
Fader3Touch PushButton 90 6a 7f
Fader4Touch PushButton 90 6b 7f
Fader5Touch PushButton 90 6c 7f
Fader6Touch PushButton 90 6d 7f
Fader7Touch PushButton 90 6e 7f
Fader8Touch PushButton 90 6f 7f

Mute1 PushButton 90 10 7f
Mute2 PushButton 90 11 7f
Mute3 PushButton 90 12 7f
Mute4 PushButton 90 13 7f
Mute5 PushButton 90 14 7f
Mute6 PushButton 90 15 7f
Mute7 PushButton 90 16 7f
Mute8 PushButton 90 17 7f

// Associate the widgets with actions
Fader1 TrackVolume
Fader2 TrackVolume
Fader3 TrackVolume
Fader4 TrackVolume
Fader5 TrackVolume
Fader6 TrackVolume
Fader7 TrackVolume
Fader8 TrackVolume

Fader1Touch TrackTouch
Fader2Touch TrackTouch
Fader3Touch TrackTouch
Fader4Touch TrackTouch
Fader5Touch TrackTouch
Fader6Touch TrackTouch
Fader7Touch TrackTouch
Fader8Touch TrackTouch

Mute1 TrackMute
Mute2 TrackMute
Mute3 TrackMute
Mute4 TrackMute
Mute5 TrackMute
Mute6 TrackMute
Mute7 TrackMute
Mute8 TrackMute

// filename list

See where the type is mentioned ?

That's right, ONLY the widget (Fader14bit, PushButton).

There is no need to differentiate between switches, vpots, faders etc,. EXCEPT right at the widget definition.

Putting a term in the middle doesn't do much except make things more confusing, at least to me.

The final maps really will look this simple, there is no need for any more than that to fully describe the system.
Beta software Donate
Installation / documentation / source
Geoff Waddington is offline   Reply With Quote