From the midi in module "out":
- go to a dispatcher "in"
- go to a midi filter "in" (set the midi filter to "note on")
from the midi filter "data 1" out (the note number) got to math A-B "a", set B to 23
from the A-B "out" go to the dispatcher "select" in.
the from dispatcher "out 1" go to Vsti 1, "out 2" to vsti 2, "out 3" to vsti 3
to avoid stuck notes you can go from A-B "out" to a Has Changed module "in" and connect the Has changed "out" to a Dashboard module "P" (panic button) in.
Should work without problems.
If you want to use some other notes to shift vst just change the B value in the A-B
Regards,
B.
Statistics: Posted by bmoussay — 03 May 2008, 18:03
]]>
Hey Madmage,
Thats very easy to do in Usine.
You have two possible strategies:
1) each of your vsti is in a different patch on the grid
or
2) all the vstis are in a single patch
then you simply use a combination of modules: midi input, data dispatcher, maybe a few maths modules to build the selector (extract the note number from the midi input and feed it to the dispatcher).
Then in the case 1) you can use a "select grid" module to determine witch vsti will be played, or you use some "send midi bus" modules in the "router" patch, and "get midi bus" modules in each of the vsti patch.
In the case 2) you just use some "pass event flow" connected to each of the "dispatcher" outs module to route the midi in to the vsti you want.
Hope it can help,
Regards,
B.
Thanks but... it's not so easy for a newbie...Thats very easy to do in Usine.
You have two possible strategies:
1) each of your vsti is in a different patch on the grid
or
2) all the vstis are in a single patch
then you simply use a combination of modules: midi input, data dispatcher, maybe a few maths modules to build the selector (extract the note number from the midi input and feed it to the dispatcher).
Then in the case 1) you can use a "select grid" module to determine witch vsti will be played, or you use some "send midi bus" modules in the "router" patch, and "get midi bus" modules in each of the vsti patch.
In the case 2) you just use some "pass event flow" connected to each of the "dispatcher" outs module to route the midi in to the vsti you want.
Hope it can help,
Regards,
B.
First of all: I need some module to keep a value (the value of the current selected patch/instrument), and this value changes according to some MIDI message (the buttons on my MIDI keyboard), what module should I use?
Second, talking about 1) solution: where the "select grid" should be? should I put it on a separate track?
Statistics: Posted by madmage — 03 May 2008, 00:53
]]>
Thats very easy to do in Usine.
You have two possible strategies:
1) each of your vsti is in a different patch on the grid
or
2) all the vstis are in a single patch
then you simply use a combination of modules: midi input, data dispatcher, maybe a few maths modules to build the selector (extract the note number from the midi input and feed it to the dispatcher).
Then in the case 1) you can use a "select grid" module to determine witch vsti will be played, or you use some "send midi bus" modules in the "router" patch, and "get midi bus" modules in each of the vsti patch.
In the case 2) you just use some "pass event flow" connected to each of the "dispatcher" outs module to route the midi in to the vsti you want.
Hope it can help,
Regards,
B.
Statistics: Posted by bmoussay — 02 May 2008, 21:22
]]>
It can be a changeable MIDI matrix, for example, i.e., a MIDI matrix that can be changed when trigged by a MIDI message.
I think that I will program a VST plugin that is able to do this, if it does not exist in USINE.
Statistics: Posted by madmage — 02 May 2008, 20:06
]]>
]]>
Things that would interest me (can't speak for anyone else) would be:
-live MIDI midi looper/recorder/manipulator .. with direct manipulation features something along the lines of Temper
-live midi performance tools (ala Karma, Zyklus, etc.)
I'd love to see a midi looper/beatbox tool as well.-live MIDI midi looper/recorder/manipulator .. with direct manipulation features something along the lines of Temper
-live midi performance tools (ala Karma, Zyklus, etc.)
Statistics: Posted by eimhin — 02 May 2008, 02:58
]]>
did you try the Echoplexx patch in the library?
Not yet, sorry!I'll try that and see if it does what I want.
As I haven't purchased Usine yet I don't know, maybe something in the add-ons is similar and even more advanced...
There in the link I posted, the main topic wasn't Echoplex per se, it just showed in the link name because I used this term in the search function.
This was more to the topic:
http://www.magicd.com/polar.html
But I'll try the Echoplexx
Statistics: Posted by Kaspar — 01 May 2008, 09:57
]]>
Because I might not be able to explain it better, maybe have a read at this thread of another forum:
http://www.cockos.com/forum/showthread. … t=echoplex
did you try the Echoplexx patch in the library?http://www.cockos.com/forum/showthread. … t=echoplex
Statistics: Posted by senso — 01 May 2008, 09:21
]]>
-live midi performance tools (ala Karma, Zyklus, etc.)
-live sequencers (analog/algorithmic.. Notron, Octopus, etc.)
-nice analog/thick sounding ringmod/flanger (like MXR)/comb filter/high quality vocoder (though this effect stuff could just be left to 3rd party kvr developers, as one could spend all their time developing a bloody vocoder..
..live midi stuff is higher on my wishlist) FWIW Statistics: Posted by lung — 30 Apr 2008, 23:53
]]>
I'm not sure, maybe something like this already exists in Usine library.
I'm thinking in the lines of RAM recording, looping overdubbing, making different independent loops, switching/manipulating them - sort of a live compositional tool.
Loop record lengths only limited by the amount of RAM. When that hits, then render to disk.
Because I might not be able to explain it better, maybe have a read at this thread of another forum:
http://www.cockos.com/forum/showthread. ... t=echoplex
Thanks!
Statistics: Posted by Kaspar — 30 Apr 2008, 23:16
]]>
- a beautiful woman dancing in sync with usine
That's my two cents.
Statistics: Posted by moody33 — 30 Apr 2008, 16:45
]]>
- loopers,
- delay fx,
etc.
Statistics: Posted by senso — 30 Apr 2008, 15:30
]]>