]]>
Another thought I had, was to save pitches of note-ons, and send them when a trigger key was hit--so you could do quick rhythms on full chords like a guitarist. I guess if you really wanted to emulate guitar, you could have one trigger delay notes as they went from low to high, and another delay them high to low, to simulate strumming.
Statistics: Posted by woodslanding — 28 Oct 2008, 16:45
]]>
With for example three outputs and C3 selected as the first switcher key, hitting D3 will send the following NoteOns out through the third MIDI output, but using the some logic as in the transposer any NoteOffs received after key switching could be routed to the same output as the preceding NoteOn.
Anyone interested?
Statistics: Posted by bsork — 28 Oct 2008, 13:00
]]>
]]>
CODE:
//////////////////////////////////////////////////////// transpose midi note// 2008-10-24: @Bsork, first version // 2008-10-26: @amiga909, 'wrap around' added //////////////////////////////////////////////////////VAR pIn, pOut, pTransp, pWrapAround : tParameter;TYPE tTransp = ARRAY OF integer;VAR transp : ARRAY OF tTransp;VAR tmp : tMidi;VAR len, transpose, i, tempTransp : integer;PROCEDURE Init;BEGIN pIn := CreateParam('midi in', ptMidi); SetIsOutput(pIn, FALSE); pOut := CreateParam('midi out', ptMidi); SetIsInput(pOut, FALSE); pTransp := CreateParam('transpose', ptDataFader); SetIsOutput(pTransp, FALSE); SetFormat(pTransp, '%.0f'); SetMin(pTransp, -127); SetMax(pTransp, 127); pWrapAround := CreateParam('wrap around', ptSwitch); SetIsOutput(pWrapAround, FALSE); SetArrayLength(transp, 16); FOR i := 0 TO 15 DO // A two-dimensional array; [16 channels][128 transpose values] SetArrayLength(transp[i], 128);END; // expects a noteOn msg with velocity > 0; outputs the transposed note value [0-127]FUNCTION calcTranspose (t: integer; wrap: single): integer;BEGIN IF wrap > 0 THEN BEGIN // IF (t > 127) THEN result := t - 128 ELSE IF (t < 0) THEN result := t + 128; END ELSE BEGIN IF t > 127 THEN result:= 127 ELSE IF t < 0 THEN result:=0 ELSE result:=t; END; END;// mainBEGIN len := GetLength(pIn); IF (len > 0) THEN BEGIN transpose := trunc(GetValue(pTransp)); SetLength(pOut, len); FOR i := 0 TO (len - 1) DO BEGIN GetMidiArrayValue(pIn, i, tmp); tempTransp := transpose + tmp.data1; IF (tmp.msg = 144) AND (tmp.data2 > 0) THEN BEGIN // NoteOn tempTransp:= calcTranspose(tempTransp, GetValue(pWrapAround)); transp[tmp.channel - 1][tmp.data1] := tempTransp; tmp.data1 := tempTransp; SetMidiArrayValue(pOut, i, tmp); END ELSE IF (tmp.msg = 128) or ((tmp.data2 = 144) and (tmp.data2 = 0)) THEN // NoteOff tmp.data1 := transp[tmp.channel - 1][tmp.data1]; SetMidiArrayValue(pOut, i, tmp); END; END ELSE BEGIN SetLength(pOut, 0); END;END.I'd like to add a little "party trick" if someone else is testing your rig: Add an LFO or random generator to the transpose value as I did when testing, it's quite confusing when the same key changes notes all the time!
Statistics: Posted by amiga909 — 26 Oct 2008, 15:26
]]>
how did you know this? thought this to be right http://www.midi.org/about-midi/table2.shtml
thanks.
Of course the MIDI table is right, it's just that it specifies the messages as it is transmitted. In practical use, the first (status) byte of channel messages can be called a compound message since it contains both the channel and the message type. As the byte has to be "split" into two parts, one call just as well add 1 to the channel part of the message as the MIDI channels are defined as 1 to 16, even when it's mathematically 0 to 15.thanks.
To be honest, I have always thought the definition of channels as 1 to 16 has been silly. I guess the explanation is a "psychological" or "political" one in that a lot of people actually find counting from 0 instead of 1 hard to swallow.
I'd like to add a little "party trick" if someone else is testing your rig: Add an LFO or random generator to the transpose value as I did when testing, it's quite confusing when the same key changes notes all the time!It's turned the transpose (especially the octave control) into a performance tool!
Statistics: Posted by bsork — 26 Oct 2008, 08:37
]]>
It's turned the transpose (especially the octave control) into a performance tool!
So here it is if anyone is interested.... rather specific application, but useful stuff maybe.
CODE:
//// take input from two keyboards and assign one or both to a vst. also split and transpose.TYPE tNoteArr = ARRAY OF boolean;TYPE tStatus = RECORD low : integer; max : integer; sus : boolean; bend : boolean;END;TYPE tTransp = ARRAY OF integer;VAR transpositions : ARRAY OF tTransp;// parameters declarationvar input : Tparameter; // midi inputvar output : Tparameter; // midi outputvar key1 : Tparameter; // output notes from keyboard 1var key2 : Tparameter; // output notes from keyboard 2// these are not implemented yet....soon.var volKey1 : Tparameter; // send out a volume control signal for keyboard 1, if enabled as a sourcevar volKey2 : Tparameter; // send out a volume control signal for keyboard 2, if enabled as a sourcevar enable : Tparameter; // boolean control out for disabling VST if no keyboard is controlling itvar outCH : Tparameter; // rechannelize input. Value of 0 leaves output channel unchangedvar semi : TParameter; // transpose by semi-tonevar octave : TParameter; // transpose by octavevar split : Tparameter; // pitch below or above which notes are not sentvar upper : Tparameter; // send pitches above the split if on. otherwise send pitches below.var bytecount : integer;var midiLen : integer;var midi : TMidi;var transpose : integer;var splitVal : integer;var upperVal : integer;var key1Val : single;var key2Val : single;var key1ch : integer;var key2ch : integer;var i : integer;var channel : integer;// initialisation PROCEDURE init;BEGIN output := CreateParam('MIDIout',ptMidi); SetIsInput(Output,false); volKey1 := CreateParam('volK1',ptMidi); SetIsInput(volKey1,false); volKey2 := CreateParam('volK2',ptMidi); SetIsInput(volKey2,false); enable := CreateParam('vstEnable',ptDataField); SetIsInput(enable,false); input := CreateParam('MIDIin',ptMidi); SetIsOutput(Input,false); semi := CreateParam('semi',ptDataField); SetIsOutput(semi,false); octave := CreateParam('8va',ptDataField); SetIsOutput(octave,false); split := CreateParam('split',ptMidiNoteFader); SetIsOutput(split,false); upper := CreateParam('upper',ptSwitch); SetIsOutput(upper,false); key1 := CreateParam('key1', ptSwitch); SetIsOutput(key1,false); key2 := CreateParam('key2', ptSwitch); SetIsOutput(key2,false); outCH := CreateParam('outCH', ptDataField); SetIsOutput(outCH,false); key1ch := 1; key2ch := 2; SetArrayLength(transpositions, 2); FOR i := 0 TO 1 DO // we are going to ignore midi data on any but the 2 keyboard channels... SetArrayLength(transpositions[i], 128); //default values and formats SetDefaultValue(upper,1); SetDefaultValue(key1,1); SetDefaultValue(key2,1); SetFormat(split,'%.0f'); SetMin(split,1); SetMax(split,127); SetDefaultValue(split,1); SetFormat(semi,'%.0f'); SetMin(semi,-7); SetMax(semi,7); SetDefaultValue(semi,0); SetFormat(octave,'%.0f'); SetMin(octave,-4); SetMax(octave,4); SetDefaultValue(octave,0)end;PROCEDURE processNoteOns;BEGIN writeln('in noteon loop'); IF (((channel = key1ch) AND (key1Val = 1)) OR ((channel = key2ch) AND (key2Val = 1))) AND (((midi.data1 >= splitVal) AND (upperVal = 1)) OR ((midi.data1 < splitVal) AND (upperVal = 0))) THEN BEGIN transpositions[channel - 1][midi.data1] := transpose; // only works if keyboard ch's are 1 and 2.... midi.data1 := midi.data1 + transpose; SetMidiArrayValue(output, bytecount, midi); END; END; //process NoteonsPROCEDURE processNoteOffs;BEGIN midi.data1 := midi.data1 + transpositions[channel - 1][midi.data1]; // Retrieve stored transpose and add to NoteOff SetMidiArrayValue(output, bytecount, midi);END; //processNoteoffsPROCEDURE processSustain; // untestedBEGIN IF (midi.data1 < 64) THEN //send sus up on all instruments, selected or not... BEGIN SetMidiArrayValue(output, bytecount, midi); END ELSE IF (((channel = 1) AND (key1Val = 1)) OR ((channel = 2) AND (key2Val = 1))) THEN BEGIN IF (midi.data1 >= 64) THEN //send sus down only on selected instruments BEGIN SetMidiArrayValue(output, bytecount, midi); END; END;END; // process sustain // mainBEGIN midiLen := GetLength(input); IF (midiLen > 0) THEN BEGIN SetLength(output, midiLen); // set variables from inputs transpose := trunc(GetValue(semi) + ((getValue(octave) * 12))); splitVal := trunc(getValue(split)); upperVal := trunc(getValue(upper)); key1Val := trunc(getValue(key1)); key2Val := trunc(getValue(key2)); // process midi FOR bytecount := 0 TO (midiLen - 1) DO BEGIN GetMidiArrayValue(input, bytecount, midi); channel := midi.channel; IF ((midi.msg = 144) AND (midi.data2 > 0)) THEN BEGIN // Noteon processNoteons; END ELSE IF ((midi.msg = 128) OR ((midi.msg = 144) AND (midi.data2 = 0))) THEN BEGIN // NoteOff processNoteoffs; END ELSE IF (midi.msg = 176) THEN BEGIN processSustain; END; ///ELSE IF ((midi.msg = 224) pitchbend, etc. END; END // no midi in this block.... ELSE BEGIN SetLength(output, 0); END;END.Statistics: Posted by woodslanding — 26 Oct 2008, 02:01
]]>
made a little test script and fed midi notes on various channels into it.
CODE:
//////////////////////////////////////////////////////// TEST: midi message 1st byte + midi channel filtering//////////////////////////////////////////////////////// Paramters declarationvar input, txt : Tparameter;var tmp : TMidi;var len, i: integer; // initialisation procedureprocedure init;begin input := CreateParam('input',ptMidi); SetIsOutput(input,false); txt := CreateParam('txt',ptTextField); SetIsInput(txt,false);end;procedure writeMidi(m: TMidi);var s: string;beginsetLength(txt,50);s:= '[msg: ' + intToStr(m.msg) +'] [chn:'+ intToStr(m.channel) + ']';setStringValue(txt,s);writeln(s);end; // Main Loop procedurebegin len := getLength(input); if len > 0 then begin for i:=0 to len-1 do begin getMidiArrayValue(input,i,tmp); if (tmp.msg = 144) or (tmp.msg = 128) then writeMidi(tmp); if ((tmp.msg > 144) and (tmp.msg < 160)) or ((tmp.msg > 128) and (tmp.msg < 144)) then writeMidi(tmp); end; end;end.thanks.
Statistics: Posted by amiga909 — 25 Oct 2008, 14:47
]]>
The reason that all channels are recognized, is that the first (status) byte is being handled before it enters Usine. A typical channel MIDI message like a NoteOn going down a MIDI cable consists of three bytes: 1) channel and message type NoteOn, 2) note number, and 3) velocity.
Statistics: Posted by bsork — 24 Oct 2008, 22:12
]]>
3 - Absolutely. Basically try something like:
IF (ReceivedMidi.msg = 144) AND (ReceivedMidi.channel = 0) THEN...
Note that in the scripting environment midi channels go from 0-15, not from 1-16.
why do you expect no noteOn's on channels 2-16 (erg. 1-15) with code 145 to 159?IF (ReceivedMidi.msg = 144) AND (ReceivedMidi.channel = 0) THEN...
Note that in the scripting environment midi channels go from 0-15, not from 1-16.
Statistics: Posted by amiga909 — 24 Oct 2008, 15:55
]]>
1 - writeln works, yes. It writes to the trace window.
2 - I don't think there exists a full reference for the Usine scripting environment. Most basic pascal stuff seems to work. And the help-tab gives an idea (but not a full idea) of which commands it can take. Olivier will be better at answering this one.
3 - Absolutely. Basically try something like:
IF (ReceivedMidi.msg = 144) AND (ReceivedMidi.channel = 0) THEN...
Note that in the scripting environment midi channels go from 0-15, not from 1-16.
Others can elaborate more on the parts I missed.
Have fun!
antwan
Statistics: Posted by antwan — 24 Oct 2008, 15:23
]]>
got 3 newbie questions regarding scripting:
1- writeln works? where is the line being written to? to the scripting window?
only very roughly tested it yesterday. but its also possible I did not realize assignements in pascal script have "pass-by-value" instead of "pass-by-reference" (like Java) (so writeln(array[0] returned nothing cause I read the variable out before)?
2- can smby recommend a full reference website/pdf for the script module?
3- both of you ask for noteOns with 'IF (ReceivedMidi.msg = 144)' and for noteOffs with 'IF (ReceivedMidi.msg = 128)'
looking at this table http://www.midi.org/about-midi/table2.shtml , is it possible you will only take care of midi notes on channel 1, channels 2-16 will be passed?
Statistics: Posted by amiga909 — 24 Oct 2008, 14:57
]]>
It's definately a cleaner script, that's for sure. Plus I had forgotten to take care of note on with 0 velocity.
But incase anyone ever needs a script for "delete index from array", they can find that hacked within my mess!
Well this made for another interesting thread
Thanks bsork!
antwan
Statistics: Posted by antwan — 24 Oct 2008, 11:12
]]>
-e
Statistics: Posted by woodslanding — 24 Oct 2008, 06:45
]]>
CODE:
VAR pIn, pOut, pTransp : tParameter;TYPE tTransp = ARRAY OF integer;VAR transp : ARRAY OF tTransp;VAR tmp : tMidi;VAR len, transpose, i : integer;PROCEDURE Init;BEGIN pIn := CreateParam('midi in', ptMidi); SetIsOutput(pIn, FALSE); pOut := CreateParam('midi out', ptMidi); SetIsInput(pOut, FALSE); pTransp := CreateParam('transpose', ptDataFader); SetIsOutput(pTransp, FALSE); SetFormat(pTransp, '%.0f'); SetMin(pTransp, -24); SetMax(pTransp, 24); SetArrayLength(transp, 16); FOR i := 0 TO 15 DO // A two-dimensional array; [16 channels][128 transpose values] SetArrayLength(transp[i], 128);END; // Init// mainBEGIN len := GetLength(pIn); IF (len > 0) THEN BEGIN transpose := trunc(GetValue(pTransp)); SetLength(pOut, len); FOR i := 0 TO (len - 1) DO BEGIN GetMidiArrayValue(pIn, i, tmp); IF ((tmp.msg = 144) AND (tmp.data2 > 0)) THEN BEGIN // NoteOn transp[tmp.channel - 1][tmp.data1] := transpose; // Store transpose value used for NoteOn tmp.data1 := tmp.data1 + transpose; END ELSE IF ( (tmp.msg = 128) OR ((tmp.msg = 144) AND (tmp.data2 = 0))) THEN BEGIN // NoteOff tmp.data1 := tmp.data1 + transp[tmp.channel - 1][tmp.data1]; // Retrieve stored transpose and add to NoteOff END; SetMidiArrayValue(pOut, i, tmp); END; END ELSE BEGIN SetLength(pOut, 0); END;END.If you have any questions, feel free to ask. I'm not as good as you to write comments.
Statistics: Posted by bsork — 24 Oct 2008, 01:07
]]>
Thanks for comments. I'm not sure I understand this part though:
Hence, I'm having trouble understanding the rest of itHowever, instead of using lots of temporary arrys, loops etc, I think it's a lot easier to use the MIDI data for array lookups.
But I sure would like to understand! Could you elaborate?
Thanks a million,
antwan
Statistics: Posted by antwan — 23 Oct 2008, 16:33
]]>
However, instead of using lots of temporary arrys, loops etc, I think it's a lot easier to use the MIDI data for array lookups. Eg when a NoteOff is received, store the current transposition value together with the channel and note number and send the transposed note out. When a NoteOff is received, use ch/note to retrieve the original transposition value. I can't be sure, but I think it not only makes for less programming, but will in most cases be more efficient. The drawback in most cases is a bit more RAM used, I suppose.
Statistics: Posted by bsork — 23 Oct 2008, 14:19
]]>
Here's a modified (in a big way) version of the midi transpose script that takes care of note off's even if the transposition has changed since the note on. Seems to work alright after a quick test.
CODE:
// ADVANCED MIDI TRANSPOSE// Parameters declarationVAR input : Tparameter;VAR output : Tparameter;VAR transpo : TParameter;// Global variablesVAR i, j, x : integer;VAR nbOfMidi : integer;VAR transpoVal : integer;VAR arrLength : integer;VAR ReceivedMidi : TMidi;VAR notesArray : Array of integer; // This holds the note numbers that are waiting for note offsVAR transpoArray : Array of integer; // This holds the transposition value that was in place when each of the notes in notesArray was addedVAR tempNotesArray : Array of integer; // A temp array used in proc DelArrayIndicesVAR tempTranspoArray : Array of integer; // A temp array used in proc DelArrayIndices// Initialisation - create parametersPROCEDURE init;BEGIN Input := CreateParam('In',ptMidi); Output := CreateParam('Out',ptMidi); transpo := CreateParam('transpo',ptDataFader); SetIsInput(Output,false); SetIsOutPut(Input,false); SetIsOutPut(transpo,false); SetFormat(transpo,'%.0f'); SetMin(transpo,-24); SetMax(transpo,24);END; // initPROCEDURE DelArrayIndices;BEGIN SetArrayLength(tempNotesArray, (arrLength-1)); SetArrayLength(tempTranspoArray, (arrLength-1)); FOR x := 0 TO j-1 DO BEGIN tempNotesArray[x] := notesArray[x]; tempTranspoArray[x] := transpoArray[x]; END; IF j <> arrLength-1 THEN BEGIN FOR x := j+1 TO arrLength-1 DO BEGIN tempNotesArray[x-1] := notesArray[x]; tempTranspoArray[x-1] := transpoArray[x]; END; END; SetArrayLength(notesArray, (arrLength - 1)); SetArrayLength(transpoArray, (arrLength - 1)); notesArray := tempNotesArray; transpoArray := tempTranspoArray; SetArrayLength(tempNotesArray, 0); SetArrayLength(tempTranspoArray, 0); END; // DelArrayIndices // MainBEGIN nbOfMidi := GetLength(input); // get the number of incoming midi codes IF nbOfMidi > 0 THEN BEGIN SetLength(outPut,nbOfMidi); // set the number of output codes transpoVal := trunc(getValue(transpo)); // get the transpo value FOR i := 0 TO nbOfMidi-1 // loop for all input codes, for polyphonic data (chords) DO BEGIN GetMidiArrayValue(input,i,ReceivedMidi); // get each code arrLength := GetArrayLength(notesArray); // Refresh how many notes are waiting for note off // If received midi is NOTE ON then add note to array and current transposition to another array IF (ReceivedMidi.msg = 144) THEN BEGIN SetArrayLength(notesArray, (arrLength + 1)); // Expand note array for new note SetArrayLength(transpoArray, (arrLength + 1)); // Expand transposition value array for new note notesArray[arrLength] := (ReceivedMidi.data1 + transpoVal); // Add note number to newest slot transpoArray[arrLength] := transpoVal; // Add current transposition to newest slot // FOR DEBUGGING // writeln('ADD: ' + intToStr(ReceivedMidi.data1) + ' WITH: ' + intToStr(transpoVal)); ReceivedMidi.data1 := ReceivedMidi.data1 + transpoVal; // Adjust midi with transposition value SetMidiArrayValue(output,i,ReceivedMidi); // Set transformed midi to output END; // If received is NOTE OFF then take current transposition into account, find the note in array and remove from array IF (ReceivedMidi.msg = 128) AND (arrLength > 0) THEN BEGIN FOR j := 0 TO arrLength-1 // Go through all stored notes DO BEGIN IF notesArray[j] = (ReceivedMidi.data1 + transpoArray[j]) THEN BEGIN ReceivedMidi.data1 := (ReceivedMidi.data1 + transpoArray[j]); SetMidiArrayValue(output, i, ReceivedMidi); // Send note off to midi outlet // FOR DEBUGGING // writeln('REMOVE: ' + intToStr(notesArray[j])); DelArrayIndices; // call proc to remove note from arrays BREAK; // Break for-loop END; END; END; END; END ELSE SetLength(outPut,0); // nothing received, set out length to 0END. // mainAlso, since I'm not a pro, perhaps bsork for instance might be able to point out things that aren't optimal, but I did my best!
antwan
Statistics: Posted by antwan — 23 Oct 2008, 13:36
]]>
I'm not in front of my laptop/usine so can't check on the midi transpose script specifically but in general wherever you see a GetValue (or GetMidiArrayValue etc.) is when the input is read. If the value is assigned to a variable that's when the variable gets updated. I'll have a look at the script in question later today unless someone else makes it first.
Concerning note offs, I believe both work alright (code 128 and vel 0).
antwan
Statistics: Posted by antwan — 22 Oct 2008, 07:33
]]>
I have successfully modified and compiled a script, and read the helpfile, and I am starting to understand. Here's a question:
I am assuming (okay, I haven't checked!) that in the midi transpose script, if you change the transpose value while holding down notes, they will stick. I'm trying to figure out how the main event loop is going to recognise that the transpose value has changed, in order to fire off the requisite note-offs. Do I just get the value of transpose with each loop, and compare it with a stored version of the value? What happens if it changes during the loop? Or does the script not see any changes until the next loop?
Also, I'm wondering: does Usine use noteons of vel 0, or true noteoffs? Or seamlessly respond to both??
Thanks!
-eric
Statistics: Posted by woodslanding — 22 Oct 2008, 05:52
]]>
In the scripting window there's a tab ("help" I think) with most of the available commands. That list together with all the examples an user add-on scripts around (and of course help here at the forum) has gotten me quite far personally. Anyways, I've been following the thread and will be glad to join in on helping you out in the process. I've just been very busy lately. I too am interested in similar scripts. Bsork is the proven master of scripting (and patching for that matter) but as mentioned, I too will do my best to help you out.
Best regards,
antwan
Statistics: Posted by antwan — 21 Oct 2008, 21:48
]]>
Yes, by API, I actually meant 'documentation'. Bad word choice! Thanks for tips on more example scripts. I've done scripts in 'kontakt' and it wasn't too hard, although they did have a good chunk of manual on it. Is there even a list of commands somewhere??
The CPU tip is also helpful--I'm less worried now. I'll see what I can turn off in the background. Eventually, if I'm using this computer live, I'll be dual-booting, but my live computer is super clean, so those figures should go down on that machine.
I found out where to disable processing on subgroups. I'm still not clear if 'bypass' on a vst bypasses processing as well as signal, but I should be able to figure that out.
I may try replacing most of my midi management with a script, as I think I could replace an awful lot of modules with it. It would have a lot of data ins and outs though!
Thanks as always for the support!
-e
Statistics: Posted by woodslanding — 21 Oct 2008, 18:31
]]>
]]>
I'm concerned because I'm running at 30% with less than one incomplete channel of midi input processing, and no VST's at all yet.
not totally sure , but i think cpu indicator in Usine is not only Usine but all processus running...so maybe something else running in the background...?Statistics: Posted by nay-seven — 19 Oct 2008, 22:44
]]>
As far as I've understood, your MIDI setup is quite complex, but 30% before any audio?!? That seems VERY strange... Without knowing any details, it's of course hard to tell why this is so. Jus for the record, you can turn off processing on every (sub-)patch when it's not needed.
If you mean sub-patches (not subgroups), there shouldn't be much extra drain using those instead of having everything exposed within the (top) patch. Of course a tiny bit of extra CPU is used since there are more connections, but I've never found that I've noted any difference. As using sub-patches also makes complex patches tidier, it might even give some CPU gains because of a better constructed program. In most cases, scripts are using more CPU than modules, but it isn't always so. Most modules are "cheap", but with very complex calculations, script might be the better way od doing things. Not only will it often be simpler to create a script when you have a lot of IF..THEN...ELSE type of things to consider, but with a script it's easier to make sure that only the needed calculations are being performed.
I'm not quite sure what you mean by an API for the scripts. There's an API if you want to create you're own compiled user modules, otherwise the script language is sort of an API in itself. Check out some of supplied scripts, and I suppose you soon get the hang of it. (And I know: It's about time that a manual or quick-start for scripts was made...)
The idea of accumulating NoteOns without NoteOffs is a good one and clearly something best done with a script. In fact I've had in the back of my mind to create an add-on similar to what you describe. If you want to have a go at it, you could do worse than take a look at the script you'll find in http://www.sensomusic.com/forums/viewtopic.php?id=1027. Also so take a look at the various MIDI scripts that's included with Usine.
You can send MIDI through the same wires as everything else within Usine, only that it doesn't always make sense because of MIDI's variable data structures... As long as there are MIDI specific varieties of a module (like buses), you should use those, though. To stop a MIDI stream, you can use the Event Control/Stop Event Flow module.
You don't have to turn on all the in- or outputs, neither audio nor MIDI, if you don't want to. Go to setup - it's quite easy. You might also want to check whether the dual core optimization has been turned on, and that the right ASIO driver is selected.
You can use the dispatcher module to select where to send your audio (or any other data). If it's audio, you should turn on the reset to 0 option as explained in the manual.
Hope this helps!
Statistics: Posted by bsork — 19 Oct 2008, 22:04
]]>