Midi out dispatcher
I've uploaded a simple add-on i needed to improve my live workspace.
It's a simple patch with 1 midi in and 4 midi out. Simply choose towards wich midi out the midi flow will be pass through...
Changing the selection will send an "all note off" message to the four midi out.
In the midi tools section
It's a simple patch with 1 midi in and 4 midi out. Simply choose towards wich midi out the midi flow will be pass through...
Changing the selection will send an "all note off" message to the four midi out.
In the midi tools section
Seb.Dub
Nice little patch. Smart using the Dispatcher instead of a lot of A=Bs!
Bjørn S
nice use of the dispatcher indeed 
added 2 small scripts that do something similar:
switch1-2: 1 input, 2 outputs
switch2-1: 2 inputs, 1 output
they both make use of bsorks note closer technique once again. means: hanging noteOffs will be passed thru (if the input or output is not selected)
added 2 small scripts that do something similar:
switch1-2: 1 input, 2 outputs
switch2-1: 2 inputs, 1 output
they both make use of bsorks note closer technique once again. means: hanging noteOffs will be passed thru (if the input or output is not selected)
cool ethnix73 !
always useful !
@ amiga909 , what about the same for data...?
could replace toggle +dispatch in some case
Thanks guys
always useful !
@ amiga909 , what about the same for data...?
could replace toggle +dispatch in some case
Thanks guys
fixed a bug in the 2-1 midi switch script (same notes on both midi inputs could interfere).
@nay: hmmm.. we could try it. but i fear i couldnt make a script faster than the non-script module way.
for data streams a C++ or Delphi module would be better.
senso said about this:
"C++ is 20x faster than script language but for midi manipulation it's not a problem: the midi rate is generally few midi events per second. Scripting does a good job."
@nay: hmmm.. we could try it. but i fear i couldnt make a script faster than the non-script module way.
for data streams a C++ or Delphi module would be better.
senso said about this:
"C++ is 20x faster than script language but for midi manipulation it's not a problem: the midi rate is generally few midi events per second. Scripting does a good job."
ok ! no problem...
thanks for the fix..
thanks for the fix..
just for info: the script engine of the V5 will be 50x faster than in the V4.
It's not an hallucination ... really 50x faster....
It's not an hallucination ... really 50x faster....
Olivier Sens
www.brainmodular.com
www.brainmodular.com
??? wow!!!senso wrote:just for info: the script engine of the V5 will be 50x faster than in the V4.
It's not an hallucination ... really 50x faster....
any more info on this? just wondering cause i believe scripts are interpreted by the native machine code and thus necessarily slower?
however its done, v5 will surprise us in so many ways, i dont want to bother u with questions of what ought to be impossible
50 times faster!?! Yet another reason for me to being lazy with delving into Delphi or C++ user modules... 
Bjørn S
-
martignasse
- Site Admin
- Posts: 611
- Location: Lyon, FRANCE
- Contact:
Well...cant 'not answer' one this onebsork wrote:50 times faster!?! Yet another reason for me to being lazy with delving into Delphi or C++ user modules...
You'll not be surprised if the SDK go a step ahead too
Not especially in term off speed (apart Usine core optimisation), but there will be some very deep end cool functions to access Usine core engine... don't know if all of them will be reflected in script.
Anyway, it will not change the complementarity between script (easy access and development) and SDK (deeper, faster, harder but complete freedom on what you code).
And on the script side... you are a master and we need you
Martin FLEURENT - Usine Developer - SDK maintainer
Who is online
Users browsing this forum: No registered users and 6 guests
