193,943 users have contributed to 42,903 threads and 257,883 posts.
In the past 24 hours, we have 5 new thread(s), 21 new post(s) and 74 new user(s).
Is it still impossible to get external midi directly into VEP? It is for me.
VEP 4.0.4881, OSX 10.5.8, 8.5 G RAM, MOL CP 3.3.2.380
Attempting to run VEP on a Protools machine as a host. Audio goes to protools, midi from Logic on another computer.
MIDI gets to protools computer but does not make it to VEP. External MIDI enabled in VEP and chosen as input on kontakt 4.05 instance.
Apparently I have too many words in my email. [:P] (Inside joke)
I don't think I can use stand-alone for what I am trying to do.
Attempting to run VEP on a Protools machine as a host. Audio goes to protools, midi from Logic on another computer. So I think my only option for getting audio from VEP into protools on the same machine is using the VEP server and RTAS plugins in Protools. Right? I am trying to avoid making many midi tracks in Protools to route.
MIDI gets to protools computer but does not make it to VEP. External MIDI enabled in VEP and chosen as input on kontakt 4.05 instance.
I have it working at another location on one computer, but not another. Seems unpredictable. Maybe something to do with setting the exernal midi pref on a server instance, because it seems like the RTAS server that is receiving external MIDI did so without any VEP prefs settings.
Imagine this scenario:
Machine one: OSX 10.5.8, VEP server 4.0.4881 32bit, several kontakt 4.05 channels, external MOL input 85 enabled in VEP prefs and assigned to kontakt instance input, MOL 3.3.3.440
Protools 8.0.1cs1, one stereo aux input with VEP RTAS connected to the local server
Machine two: OSX 10.5.8, Logic 9.1, MOL 3.3.3.440
External midi track, assigned to MOL output 85
MIDI from Logic machine not getting to VEP server on Protools machine.
He was saying "send them screenshots to the email he provided you". I haven't ever tried posting screenshots here before so maybe it's possible. Just pointing out that they are asking you to email them pictures to the provided address.
EDIT - I guess it doesn't matter anymore I didn't notice the "solved" lol. Oh well I tried haha.
Maestro2be
Well not really solved. External MIDI is very unpredictable to get working, atleast for me it is. Paul
Hi, I thought I sent an email to you directly Paul, but guess I haven't.
I still cannot always get external midi working, both when there is a slave computer and locally with MidiOverLan local pipe.
Not working:
VEP 32 server, Logic 9.1, MOL CP local pipe. Local pipe works with Kontakt 4.05 standalone, just not with VEP. MacPro 10.5.8
VEP 32 server, Protools 8.0.1cs1, MacPro 10.5.8 (Note: I do have one computer exactly like this accepting external MIDI in VEP)
Working:
VEP 32 server, Protools 8.0.1cs1, MacPro 10.5.8 (Note: I do have one computer exactly like this NOT accepting external MIDI in VEP)
VEP 32 server, Protools 8.0.1cs1, G5 Quad 2.5 10.5.8
Paul - did you external midi to work properly? I am curious, as i am planning the same type of setup, as far as I can gather: Logic as main sequencer and a separate Pro Tools rig to record an mix on, with your slaves piping into Pro Tools via VE Pro rather than ADAT.
What are the implications regarding latency/buffer compensation when using external midi? Is it best to enter a negative delay into your midi outputs (ie instrument objects) from Logic?
Dom
My situation hasn't changed. I have some external midi working, some not.
I have tried VEP as RTAS, with VEP server local and remote. Remote does have latency, and seems like it must have VEP buffer of 1. I have protools set to 1024. Local VEP server and RTAS the best I can get is VEP buffer 1 and protools 1024 (lower works but eventually introduces artifacts.)
For MIDI in Logic, I currently have the global set to -60ms for the slowest "sounding" of the external midi which is VEP right now. That means I have to add positive delay to the not so latent MIDI, like Giga's. Ulitmately I would like to leave the global sync at 0 and use track based offsets. But, negative delay in ms on tracks does not work over here, L9.1, OSX 10.5.8, DAE 8.0.1cs1, DTDM, maybe it isn't intended to. Negative tick offset does work, but -99 is not enough to compensate for the VEP latency I have, dependent of course on tempo. Ideally the midi offset is best compensated with fixed (delay in ms) instead of ticks.
I know of an install with a VEP PC slave that is ADAT into protools and has no "out of the ordinary" latency issues.
Interesting. I just tried on my Logic 9.1 (and also 9.02) and indeed negative track delay in ms has no effect at all (positive delay and negative delay in ticks works). I reported the bug to Apple.
However, a 1024 buffer in Pro Tools is very high and that makes of course any other RTAS use in Pro Tools sluggish too. It's quite hard to play a tune with this much latency. I haven't tried VE Pro in Pro Tools yet, but I guess this massive buffer requirement is only when using external midi?
Going ADAT from VE on a PC into Pro Tools is the traditional method, but it's expensive. Every 8 stereo channels of ADAT input costs £1200 via a Digi 192 Digital IO. VE Pro would be so much better.
VSL- will VE Pro's external midi feature go beyond it's experimental stage?
