Support@MixVibes wrote:
What about this one ? (not tested)
There are 15 values from 0 to 14 and there are only 14 fx, so one of the value is surely for OFF, i guess it is 0.
I see what you are saying, however my specific challenge is as follows.
On a 4X4 pad array (16 pads).
Counting from top to bottom and left to right.
Pads 1-8 are for other purposes, that leaves pads 9 to 16 free to map.
I picked the 8 effects that I like the most to map
values/effect/pad#
4/Delay/9
6/X Phaser/10
7/Flanger/11
8/Jet/12
9/Transform/13
11/Crush/14
12/Bliss/15
14/Roll/16
When a pad is pressed the particular pad is lit and all other are not by using the code below.
(Example for Flanger on pad #11)
<mapping>
<control alias="fam(Fx)[0x1].SelectAndToggle" value="7"/>
<MIDI type="Note" parameter="0x9" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0xb" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0xd" channel="0x1" value="127"/>
<MIDI type="Note" parameter="0xf" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x1" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x3" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x5" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x7" channel="0x1" value="0"/>
</mapping>
The specific pad has to be pressed a second time to turn the effect off. This actions do toggle the output from
In&Out fam(Fx)[0x1].OnOff (Logic)
correcly, however the selection is still value 7.
The LED flickers momentarily because
<mapping>
<control alias="fam(Fx)[0x1].OnOff" value="false"/>
<MIDI type="Note" parameter="0x9" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0xb" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0xd" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0xf" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x1" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x3" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x5" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x7" channel="0x1" value="0"/>
</mapping>
turns the LED off but
<control alias="fam(Fx)[0x1].SelectAndToggle" value="7"/>
is still selected.
If the second time the pad is pressed the selection would reset to 0, then all the above logic would work.
Given your sugestion of
<mapping>
<control alias="fam(Fx)[0x1].SelectAndToggle" value="0"/>
<MIDI type="Note" parameter="0x9" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0xb" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0xd" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0xf" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x1" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x3" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x5" channel="0x1" value="0"/>
<MIDI type="Note" parameter="0x7" channel="0x1" value="0"/>
</mapping>
would only work if I assign assign another button to select the value 0 which defeats the purpose of just pressing one button.
In short my dode doesn't work because
press pad 1st time=selection is made + effect is turned on.
press pad 2nd time=selection stays the same + effect is turned off.
My code would work if
press pad 1st time=selection is made + effect is turned on.
press pad 2nd time=selection resets to 0 + effect is turned off.
I appreciate the support, however, given the conditions below,
press pad 1st time=selection is made + effect is turned on.
press pad 2nd time=selection stays the same + effect is turned off.
Your suggestion will only work by pressing a different button to reset selection to 0.
press pad 1st time=selection is made + effect is turned on.
press pad 2nd time=selection stays the same + effect is turned off.
press another buton or pad to change selection to 0
I hope this topic is as interesting to you as it is to me because I see this things as small but challenging puzzles that can be solved.