Hi folks -
The other day I decided to try MIDIOverLAN to enhance my rig a bit. The goal is to sequence with all articulations of Hollywood Strings or Brass for a given section on one track, controlling articulation selection with keyswitches using TransMIDIfier. Since I have PLAY instruments quarantined on a slave machine due to their almost hilarious memory allocation scheme, the idea is that I could send a single track output from ProTools 12 to MIDIOverLAN and have that feed TransMIDIfier on the slave machine, which uses keyswitches or program changes to reroute the incoming MIDI to internal MIDIOverLAN ports that push External MIDI ins on VEPro and thus the PLAY libraries hosted therein.
I know External MIDI is a sort of "experimental" thing with VEPro, but I'm wondering if there is any information about how much worse the MIDI latency is when using external MIDI than when using the internal VEPro network MIDI.
I've always gotten great results from VEPro's embedded MIDI and am only using externals out of necessity. Using externals means that there's no offline bounce, which is a major drag (though not anyone's fault, of course, that's just how things work). See my earlier post regarding expanding VEPro Functionality about a potential future way around all of this nonsense. In any event, were I able to use MIDIOverLAN in a sufficiently low-latency mode it would allow me to build massive patches spanning multiple machines (for instance, I have huge one- and two-fingered patches that layer string, brass or wind sections, but would like to build meta-patches that control all sections on different slave computers simultaneously).
Thanks -
Richard