Regards,
B.
Statistics: Posted by bmoussay — 15 Apr 2009, 20:55
]]>
Just want to say a big thanks again to bmoussay for his keyrange script. Had a gig with Usine lately and it worked flawlessly. (Basically my Usine setup relies on this script).
Statistics: Posted by nofish — 15 Apr 2009, 19:23
]]>
Haven't had time to test yet but will report back.
Statistics: Posted by nofish — 16 Mar 2009, 18:58
]]>
I've just posted a simple keyrange script, it works OK.
It's in the addons.
http://www.sensomusic.com/download.php? ... nge.script
regards,
B.
Statistics: Posted by bmoussay — 16 Mar 2009, 17:52
]]>
cool for wanting to help me out!
Not that I appear lazy or such, had a look at your Midi split script and just thought it would be quite difficult for me to figure all this scripting stuff out, never had done any programming before.
Anyways, what I want to do is quite simple in functionality, here's a plugin that does exactly what I need, unfortunately it sometimes didn't get properly updated with snapshots, that's why I was asking for an alternative solution.
Plugin can be found here:
http://www.niallmoody.com/ndcplugs/ndcmidi.htm
So, just inlets for left limit and right limit, Midi notes not fitting into the limit are ignored, that's just it.
Statistics: Posted by nofish — 16 Mar 2009, 14:58
]]>
Could you describe precisely the functions and behaviours and inlets-outlets of such a script?
I'll see if I can give it a try.
Regards,
B.
Statistics: Posted by bmoussay — 16 Mar 2009, 02:12
]]>
The solution in the end was (since I can't do scripting myself) to use two instances of bmoussay's script (one for lower limit and one for upper limit). Have tested a bit, seems to work, no more hanging or blocked notes, yay.
Have also uploaded the new version to add-ons (deleted the old one) in case anyone else finds it useful.
bmoussay or anyone of the scripting gurus, if you ever find the time to do a dedicated keyrange filter script, would be also much appreciated but I can live fine with this solution now.
Thanks again.
Statistics: Posted by nofish — 15 Mar 2009, 21:46
]]>
What I want to do is:
Track 1: Midi In -> range filter -> VSTi 1
Track 2: Midi In -> range filter -> VSTi 2
and so on, for creating keyboard splits. The range filters must get updated with snapshots, so for example on Snap 1 I can play VSTi 1 from C1 to C2 and on Snap 2 from C2 to C3, and also, like I've tried in my patch, a learn function would be nice, because I have to create lots of splits.
At the moment I'm stuck with this, wondering what's wrong.
Thanks.
Hi, Track 1: Midi In -> range filter -> VSTi 1
Track 2: Midi In -> range filter -> VSTi 2
and so on, for creating keyboard splits. The range filters must get updated with snapshots, so for example on Snap 1 I can play VSTi 1 from C1 to C2 and on Snap 2 from C2 to C3, and also, like I've tried in my patch, a learn function would be nice, because I have to create lots of splits.
At the moment I'm stuck with this, wondering what's wrong.
Thanks.
Have you tried a solution with buses.
What I would do if I were you would be the following:
Patch "splitter"
Midi IN ->
Midi split script out 1 -> Midi Transform (if would want to add a transposition or any other transformation) -> send to midi bus (let's name it "MIDI1"
Midi split script out 2 -> Midi Transform (if would want to add a transposition or any other transformation) -> send to midi bus (let's name it "MIDI2"
Don't forget to add a fader to the "split" inlet of the MidiSplit, and of the parameters of the Midi Transform you use, so that they will be stored in the conductor or preset Manager.
Then on the tracks where you put your vsts just do : Get Midi Bus "MIDI1 (or 2)" -> VST midi in
I think it should work, if I have some time tonight I'll test it.
Regards,
B.
PS: if you need more splits, just add one or more MidiSplit Scripts.
Statistics: Posted by bmoussay — 15 Mar 2009, 21:03
]]>
Statistics: Posted by nay-seven — 15 Mar 2009, 16:17
]]>
Will try the unpack function and report back.
Any further suggestions appregiated. This is essential for me to get working perfectly since most of my use with Usine is playing live VSti's (I'm a keyboarder in a band), often up to 5 splits on one Midi keyboard.
Personally I think creating keyboard-splits easily is an essential function for a live software, so I think something like this should be included in Usine. I know there's the Midisplit patch by moody33 in add-ons, but how if I need to define more splits than two, each VSTi getting his own keyrange?
Statistics: Posted by nofish — 15 Mar 2009, 14:11
]]>
about blocked notes , have you try to active the "unpack" function in your midi in , to avoid missing note off...?
there's also the now famous " ClearMidiNotes" bsork 's script in the midi tools addons , who can be a solution...
Statistics: Posted by nay-seven — 15 Mar 2009, 09:14
]]>
If I use it on two different tracks with two differnt VSTis I get hanging and blocked notes. Could somebody take a look at it or provide me with a better solution? What I want to do is:
Track 1: Midi In -> range filter -> VSTi 1
Track 2: Midi In -> range filter -> VSTi 2
and so on, for creating keyboard splits. The range filters must get updated with snapshots, so for example on Snap 1 I can play VSTi 1 from C1 to C2 and on Snap 2 from C2 to C3, and also, like I've tried in my patch, a learn function would be nice, because I have to create lots of splits.
At the moment I'm stuck with this, wondering what's wrong.
Thanks.
Statistics: Posted by nofish — 15 Mar 2009, 00:39
]]>