Hi.
I need to play different VSTi and Midi sampler with the same midi keybord. But not in, the same time.
I think to patch something with Midi ProgramChange.
For example :
PC-01 is send :
- Active the Patch Midi Sampler
- Select Sound Bank 1 in the patch Midi Sampler
- Bypass the Patch VSTi
PC-02 is send :
- Active the Patch Midi Sampler If i send an other trigger the patch will be OFF !?
- Select Sound Bank 2 in the patch Midi Sampler
- Bypass the Patch VSTi ? If i send an other trigger the patch will be ON !?
PC-03 is send :
- Bypass the patch Midi Sampler
- Active the Patch VSTi
The problem is to change Sound Bank in Midi Sampler without activating the VSTi or Bypassing Midi Sampler
Of course i can do it with two different Midi PC.
PC-01, 02 select sound bank
(But I need two gestures instead of one.)
PC-03 Active/Deactive Midi Sampler/VSTi
The more I watch the Joffo tutorials on Youtube, the more I understand that often I create complex Patches when the same thing can be done simply.`
That's why I'm asking for your advice from the very beginning of the design of this patch.
Thank you.
One Midi Keybord for several Synth
You can also maybe use Presets ( target =workspace ) ?
you can still use Program change to select them
other idea: use patch on/off module to save cpu when off
you can still use Program change to select them
other idea: use patch on/off module to save cpu when off
Thank you.
Of course Preset seems to be simple. But it is the begening of a new show with a street art company.
I usually create my presets a little later in the process. At first, the HH interface is very confusing and allows me to test different things fairly quickly. Then little by little it gets organized and simplified and presets become necessary.
That's why I hesitate a bit with this method.
Later, all this can even be managed with the grid.
Patch On/off save more CPU than patch Bypass ?
Of course Preset seems to be simple. But it is the begening of a new show with a street art company.
I usually create my presets a little later in the process. At first, the HH interface is very confusing and allows me to test different things fairly quickly. Then little by little it gets organized and simplified and presets become necessary.
That's why I hesitate a bit with this method.
Later, all this can even be managed with the grid.
Patch On/off save more CPU than patch Bypass ?
ok, i understand,
yesPatch On/off save more CPU than patch Bypass ?
Patch bypass is usefull when you want to desactivate a patch but you need the audio pass thru it, all the modules are not calculated, but the audio goes directly from in to out. With Patch On/Off, the audio output is muted.
Sylvain
Sylvain
-
sm_jamieson
- Member
- Posts: 553
- Contact:
I was going to start a new thread but this fits here.
I was experimenting with the patch on/off and and patch bypass modules, and I found that when one of these is connected
to the patch logic, it changes what the logic before it does. It is as if Usine knows there is a patch on/off module connected and still
runs the logic leading up to this module even though the patch is "off". This enables the patch to be switched back on despite the patch containing the logic being "off".
Is this intentional functionality in Usine, or is something else going on ?
Simon.
I was experimenting with the patch on/off and and patch bypass modules, and I found that when one of these is connected
to the patch logic, it changes what the logic before it does. It is as if Usine knows there is a patch on/off module connected and still
runs the logic leading up to this module even though the patch is "off". This enables the patch to be switched back on despite the patch containing the logic being "off".
Is this intentional functionality in Usine, or is something else going on ?
Simon.
Who is online
Users browsing this forum: No registered users and 38 guests
