Buster Hemphill wrote:
I've read and understood the instructions (i will un-channelize my sets, very easy), but the source channel/ports thing is a bit unclear. Do i need to increment the range with EACH track? Or is each track brand new (= source ch 1)? The latter would be easier. In my case, i'd never have to worry about range. Each track in the tracks area corresponds to only one instrument and that instrument's articulations. I don't go above 16, at least for now. I've tried and seen that LPX only writes real time CC to MIDI CH 1
Also, this means i have to instantiate this in Scripter in the MIDI FX dropdown on each track, right? Suggesting again that range overlap wouldn't be something i would need to worry about with my above described method and limits.
So here are some diagrams which might help you understand various different ways that Channelizer could potentially be used..Let me know if it doesn't make sense..Single PLAY for each instrument.
in this example, each track feeds a single PLAY instance with up to 16 articulations. Articulation ID's 1-16 are used for both tracks.Two tracks feeding two instruments in one PLAY instance
In this example, there are two orchestral instruments being hosted in the PLAY instance with up to 8 articulations each. Articulation ID's 1-8 are used for both tracks.VePro
In this example, multiple tracks are feeding a single VePro plugin which connects to a VePro server that is capable of up to 768 midi channels on 48 ports. In this example there are 4 tracks with up to 8 articulations each... Its using 2 midi ports in VePro to handle up to 8 articulations per instrument. Articulation ID's 1-8 are used for all tracks.
Last edited by Dewdman42
on Sat Jul 11, 2020 10:04 pm, edited 2 times in total.
5,1 MacPro 3.46ghz x 12 128gb ram, OSX 10.15 on OpenCore, Logic Pro 10.5, Mainstage3, Cubase10.5, StudioOne4, Reaper, DP10, VEP7, VSL, too many plugins to list