deactivate a patch in rack/all mode

manecante · Unread post by **manecante** » 11 Oct 2010, 18:30

Hello,
is there a module or a way to talk to the button on/off in grid mode (rack/all) to activate or deactivate the patch?

YouTube · Unread post by **senso** » 11 Oct 2010, 18:34

Only a midi learn on the 'on' button or more simply use the /Interface Control/patch ON/OFF module?

manecante · Unread post by **manecante** » 11 Oct 2010, 18:37

The "patch on/off "module would do the job but i would prefer to see the state of the patch through this button if possible...

manecante · Unread post by **manecante** » 11 Oct 2010, 18:48

Here is the reason why i need it, maybe it will be more clear.
Actually as my wkp are constantly evolving, i add some patch on a track but i don't want to rewrite all presets in conductor each time i add a new one. So i was thinking to make a logical decision like if nb of conductor<X then deactivate the patch.
Can i do this with midi learn?

YouTube · Unread post by **senso** » 11 Oct 2010, 18:53

just create a switch on the 'on' inlet ?
add a conductor module to test the line number?

nay-seven · Unread post by **nay-seven** » 11 Oct 2010, 19:00

you also can use the module send midi to usine to send your midi learn ..?

manecante · Unread post by **manecante** » 11 Oct 2010, 20:12

@senso : do you mean the "on" inlet of the "patch on off " module? If yes that is what i wanted to avoid.

@nay : i don't know that much about the "send midi to usine", and don't see how to do it.

Otherwise i thought about using the keylearn like this :
-make a keylearn on the on button
-make a patch on another track :
num outlet of conductor --- A>B-----switch---passIfChange---pressed inlet of keyboard (putting the nb of the key of my keylearn inside the keyboard)...But no success neither...

nay-seven · Unread post by **nay-seven** » 11 Oct 2010, 20:48

something like this..? ( where you use midi learn on the on button of your patches
midi to usine module is in modules/ inputs_outputs

manecante · Unread post by **manecante** » 11 Oct 2010, 23:02

sorry i feel very stupide...

does that mean that i need a midi controller to do a midi learn on the button then (no virtual possibility?)?

I tested it with my controller (and of course the midi learn is working) but not the patch, when i change the nb in the conductor it does not change the activation of the button...

maybe it is something with the "control change nb x" because i did not understand what that means in your patch, apart from that i think I reproduce your patch without errors..

nay-seven · Unread post by **nay-seven** » 11 Oct 2010, 23:34

control change number x mean that you assign (for example ) number 70 to code1 of the 2 midi create message
then 2 solutions to make your midi learn
_ the midi hardware ( as you've done )
_ add a button to the create inlet of the first create midi module and press it

one think i've forget to say , sorry, you have to use toggle mode for the midi learn mode ( right click on the on button and remote mode toggle

you can also do a right click and choose find in remote panel to check it's correctly assigned

then, the midi send to usine module act as a midi hardware , sending midi informations directly in Usine ( you can check the blue led in the dashboard )

be also careful to connect the conductor after to avoid conflict or bad recall

manecante · Unread post by **manecante** » 12 Oct 2010, 00:54

I tried the two methods and none of them work...i put the nb 116 (which is the first nb of my controller i used to do the midi learn) in code 2 of the create midi module. And i also used the toggle mode....
What's wrong?

i also realised that i should put a A<=B module instead of the A<B, otherwise the "split" number is ignored.

There is also a strange behaviour when i am moving the button of my controller if i am in the patch mentionned above, usine switch in the patch where the "on" button (i try to control) is. And this is not very handy to check what is happening in the patch.

nay-seven · Unread post by **nay-seven** » 12 Oct 2010, 08:08

not the code 2 , the code 1..
the code 1 is the controller number , the code2 is the value ( here as we need an on/off i use 0 and 127 )
here an example
on this one , if preset < 5 the bit crusher patch is turned off ( off course you're right about using A<=B )

manecante · Unread post by **manecante** » 12 Oct 2010, 15:24

sorry i made a typo writing the message, i had put the number of controller in the code 1 and not 2...
But i found where comes the problem. It was because you have to set, in the "create midi" module, the message type to "control change" and not "note on "as it is by default.
Thank's Nay!

nay-seven · Unread post by **nay-seven** » 12 Oct 2010, 15:44

ok, cool !

Welcome to %s forums

deactivate a patch in rack/all mode

Who is online

Login • Register