How to bypass a VST when switching to another?
-
MikeyJ
- Member
- Posts: 16
Hi All,
I'm pretty much a Usine noob. I'm a guitarist and am setting up to run amp simulators from a laptop. I currently have an instance of Amplitube2 on track 1 and an instance of Guitar Rig 3 on track 2. I'll be using Preset Managers with them and there are times where I'll need only one active, but sometimes both. How do I automagically bypass one when switching to the other? I'm assuming this saves CPU like it does in Bidule?
Thanks!
Mike
I'm pretty much a Usine noob. I'm a guitarist and am setting up to run amp simulators from a laptop. I currently have an instance of Amplitube2 on track 1 and an instance of Guitar Rig 3 on track 2. I'll be using Preset Managers with them and there are times where I'll need only one active, but sometimes both. How do I automagically bypass one when switching to the other? I'm assuming this saves CPU like it does in Bidule?
Thanks!
Mike
- nay-seven
- Site Admin
- Posts: 5684
- Location: rennes France
- Contact:
hello and welcome !
you can use the data bus for this and and a math / logical/ not (a ) :
the 2 bus module must have the same name


you can use the data bus for this and and a math / logical/ not (a ) :
the 2 bus module must have the same name


- nay-seven
- Site Admin
- Posts: 5684
- Location: rennes France
- Contact:
here a way , inspired by 23fx on an other topic...
built this one ( can be adapted to more switch )

23xx say about it :
this might not be the only/best solution but this seems to work well for 2-15 switches.
each switch will output 2-3-4-5-6 to the selector that keep the last pressed switch number and send back to the dispatcher that have "set to 0" enabled, so it will switch off all the others, (add constant 1 on input).ps( I don't use input 1 because it will be the default output when switch are off, that's also why it's need to start from 2 , for the selector to select the 2nd
and put this one in each track ( just rename bus as : track 2 , track 3 and so...

here , the bus are linked to the mute , but you can use it to bypass a vst or what you want..
built this one ( can be adapted to more switch )

23xx say about it :
this might not be the only/best solution but this seems to work well for 2-15 switches.
each switch will output 2-3-4-5-6 to the selector that keep the last pressed switch number and send back to the dispatcher that have "set to 0" enabled, so it will switch off all the others, (add constant 1 on input).ps( I don't use input 1 because it will be the default output when switch are off, that's also why it's need to start from 2 , for the selector to select the 2nd
and put this one in each track ( just rename bus as : track 2 , track 3 and so...

here , the bus are linked to the mute , but you can use it to bypass a vst or what you want..
- nay-seven
- Site Admin
- Posts: 5684
- Location: rennes France
- Contact:
can you explain more ethnix...?
-
ethnix73
- Member
- Posts: 604
- Location: France, Caen
Yes, my answer was rather minimal 
the first button (send msg1) triggers the first Usine msg module. A value of 1 is sent to the first bus, and 0 to the others.
the second button (send msg2) triggers the second Usine msg module. A value of 1 is sent to second bus, and 0 to the others. aka:
TARGET_PATCH SEND_PATCH
SET_VALUE 1 1 0
SET_VALUE 2 2 1
SET_VALUE 3 3 0
SET_VALUE 4 4 0
And so on, for the others button and Usinemsg...
Then, you can put a getbus module in each track (as in your second screenshot in your last post), or link a getbus module directly linked to a vsti...
So each button activate a vsti and bypass the others.
the first button (send msg1) triggers the first Usine msg module. A value of 1 is sent to the first bus, and 0 to the others.
the second button (send msg2) triggers the second Usine msg module. A value of 1 is sent to second bus, and 0 to the others. aka:
TARGET_PATCH SEND_PATCH
SET_VALUE 1 1 0
SET_VALUE 2 2 1
SET_VALUE 3 3 0
SET_VALUE 4 4 0
And so on, for the others button and Usinemsg...
Then, you can put a getbus module in each track (as in your second screenshot in your last post), or link a getbus module directly linked to a vsti...
So each button activate a vsti and bypass the others.
Seb.Dub
- nay-seven
- Site Admin
- Posts: 5684
- Location: rennes France
- Contact:
great ! thanks , works fine !
will add this to the next "utils compilation " for sure .
and to add a little precision for those who want different name or want understand more :
be careful to understand the difference between the name of the in of the module and his proper name for IML :

will add this to the next "utils compilation " for sure .
and to add a little precision for those who want different name or want understand more :
be careful to understand the difference between the name of the in of the module and his proper name for IML :

-
RoyG
- Member
- Posts: 17
Are you sure? I did exactly what's shown on your posts but I get nothing when I push the buttons. I'm also getting a message saying: "Error - you can't edit sub patches and scripts in the free version" when I double click the usine-message module even though it enables me to write the text you told me to.
What am I missing?
Should the modules be in a saparate track from the vsts?
Again it seems like everything is going into an endless loop where I cant press any button. Does the order in which I do things matter?
Thanks again
Roy
What am I missing?
Should the modules be in a saparate track from the vsts?
Again it seems like everything is going into an endless loop where I cant press any button. Does the order in which I do things matter?
Thanks again
Roy
- nay-seven
- Site Admin
- Posts: 5684
- Location: rennes France
- Contact:
or use the 23fx method with dispatch and selector....

