Further to this issue:

!! And all this only ocurrs if Event Input is the VE PRO chosen MIDI input method !!

I am using Altiverb on a Mac in Digital Performer and the Digital Performer is the master system connected using Vienna Instruments Vienna Ensemble PRO to a slave Mac Mini running instrument sounds.

I run Altiverb in a V-Rack in Digital Performer on an AUX channel insert across audio that is coming back from the Mac Mini via VE PRO.

My problem is that I am experiencing dropped and hung MIDI notes on my VE PRO instruments but only when Altiverb is the chosen plugin on the AUX channel in Digital Performer. If I use another reverb plugin the problem goes away.

The problem also goes away if I turn of automatic delay compensation if Digital Performer.

!! And all this only ocurrs if Event Input is the VE PRO chosen MIDI input method !!

So is it delay compensation bug between Evernt Input and what..?

Dean

There has been a suggestion from Altiverb that the problem might be due to an Altiverb bug involving tempo changes in the sequence affecting Altiverb. I have seen this with delays but never reverbs. I am going to try to test it.

I found a sorta quick fix for this when I experience it..  (it only happens every once in awhile with sessions.. kinda like a corrupted file case)

(I use DP 7.24 btw)

This is what I do:

Double click the Event Input

In the drop down menu where you can choose a different plug in --> Select "None"

Then in the same drop down menu, re-select "VSL Event Input"

Re-assign the midi channel and to the correct instance.

BOOM! back to normal.  Kept all the midi routings too!

Works for me.... hope maybe it works for you other folks!  Takes only about 10 seconds to do..

Just for the record I also have this. I'm building a new template with DP7.24 /8.01 and VL EP with 30 event inputs and I get loads of this. Only on the event input tracks when I have lots of them active. Midi over lan and external midi is a solution but the latency is horrible.

Actually this is all coming back to me now. I tried this when event input first came out and had the same problem with large numbers of event inputs. The only alternative is using midi over lan and external midi in VSL EP. The latency is horrible but you can insert a midi track plugin in DP called time shift and offset everything early by the same number of samples as the latency. Not perfect but it works. The logic environment layer solution apparently works really well and Cubase uses vst3 so doesn't have the problem so its just Pro Tools and us DP people out here!

We need VST3 support in DP then we'd be sorted. 

It works!

As an earlier poster said you turn off plugin delay compensation in DP (setup>configure audio system >configure studio settings and uncheck Automatic plug in delay compensation) 

Also you have to set the system to run all plugins in real time and turn off pregen in the preferences.

Then it works. You still get latency from the VSL EP system depending on the number of buffers. I'm getting 1200 samples with 2 buffers run on a macbook pro. But that's still a ton better than using external midi. Still working on the finer details of this but this is the first time I've got the thing up and running and I'm using 25 event input plugins, 250 midi tracks on a Macbook pro.

 I'm actually trying Event Input for the first time. Decided to try streamlining my main template, going from running several parallel VEP instances to two or maybe three at the most. I'm on Cubase 7.

Very first Event Input I create, and assign to a not too complex VEP instance running about 10 Kontakt libraries, and it drops/skips notes, some get stuck, etc. Everything worked perfectly as independent VEP instances running on the VEP x64 server and Cubase. I'm puzzled, and glad I found other people reporting the same, and not on Cubase. So must be something on the VEP side, no? For the record, I don't have any latency compensation enabled on Cubase.

@Gusfmm said:

 I'm actually trying Event Input for the first time.

Why? It would be better to use VST3.

DG

Daryl- well no special reason other than that being a method suggested in the manual to access addtl' ports. I'd use the VST3 version if I knew what the right VEP5 instance is. I dont see a x64 listed as VST3.

 After corresponding with VSL they confirmed the VEP plug-in listed as VST3 on Cubase is x64 although its name is not labeled as such. I've been consolidating several VEP instances under just one with multiple MIDI ports, and everything works great and flawlessly, without any extra/odd latency.

DP 8.02 and Event Inputs definitely do not work properly.  Stuck notes, galore.  Had to rebuild my VEP with multiple VI Frames..

Hi,

I'm running DP 8.03 (mac) connected to a PC (W8) via VEP. What is the purpose of using an Event input, as opposed to a normal one?

And also, what are the consequences of turning off the automatic-delay-compensation?

Thanks

Thanks for the info. Turning of the automatic delay comp in DP did make things much smoother here, and since I'm not running any comps, I might get away with it, at least till mixing.

Experienced this issue for the first time when updating to 5.12800.  I had actually deselected Plugin Delay Compensation over a year ago.  I was still getting dropped notes.  I toggled delay compensation on and off, and it worked again.  Would be great to get an MAS version and open up all those ports for real.  I hear this is pie in the sky but would change my experience for sure.

 edit: spelling

I'm spending this week trying to dive more into this situation, since I have a week off work..

I'm on DP8.04 and the latest VEP 5 (12808? something like that)  But I found that if you double click the VEP plugin (within DP) where you would assign the instance, make the buffer to NONE.  

Having it at NONE made things work perfectly for me.  Even with ADC turned on!!  If I make it any of the 1-4 buffer, notes drop immediatly.  So far i've been just randomly playing instruments, trying to get it to drop, and it's not!  yay!

Now, this made my session run a bit hotter CPU wise, so i'm going to try and see if I can reduce that a bit.  (I have a very large template)

DP8.05 causes big problems for me, and MOTU confirmed that something broke with that release.  So, if you're at 8.05, i'd go back down to 8.04 if you can.

I'm giving MOTU this info as well to see if it helps them fix things for the next 8.06 release!

Hope this helps some of you...