I first experienced this issue when I purchased altiverb. Removed Altiverb from the busses, rebooted and all was well again. Altiverb are working on a fix but its not just altiverb that causes this issue - certain other reverbs do as well, spaces does not.... 

Magic dave from MOTU did email me and say that the fix was going to be included in dp8.04..... but this doesn't seem to have happened as the issue is still there for me at least. There should be another DP update soon, lets hope its fixed, in the mean time, as long as I'm carefull about what plugins I use in the same project as event input all is well. Not ideal.

Just adding my voice to the conversation and confirming that we have the same issue. 

After extensive testing we were able to confirm that the stuck midi notes were indeed an issue brought on my certain plugins being anywhere in the signal path with a VEPro instance. Altiverb was one of those. MOTU's proverb and the Waves verbs seem to operate correctly. We tried with both VST and AU getting the same results.

Hoping for a fix on either end to make it work. [:D]

If VSL would like, we have a session that almost 100% of  the time will exhibit stuck notes within a certain 8 bar stretch that we could send.

Just bumping this topic as it seems a lot of users are experiencing similar issues.  I recently experienced this going to DP8.05.  It hasn't really ever happened to me since this.. I can recall maybe a few times over the last few years that it did.. I blamed it on a possible currupt session as it only did it on a few files over the years..  

But just want to throw ou there that this topic hasn't been solved and I would love anyone's findings on how they perhaps solved it.

I do have altiverb so I'll try and see if that is the culprit.  Delay compensation is a must for me.. so the disable trick is not a valid option..

Cheers!

This issue has nothing to do with plugins, 3rd party reverb, etc.  because it is happening on a standalone VE5 instance with nothng but some MIR FX on it - no other plugins.  I have had it happen on sequences played by an external MOTU MIDI Express XT 8 port interface.   I am having stuck notes on string parts when I stop a sequence.  This stuck note problem never happened to me before with VE so it makes me think it is a new bug that has crept into the later upgrades?  I notice that it does not happen all the time - basically if you have several whole notes playing when you stop the sequence, they do not stick, but do when it is a more complex line you stop in the middle of.  Especially I had the impression that it was when the sequence was stopped just as notes were switching or transitioning rather than just sustaining.

@imzadim said:

or DP users then? It's been way to long….

I can replicate this issue easily if you'd like me to make a screen video. Usually it's Kontakt libraries with high voice counts or multiple mics (like Cinebrass or CS2). Happens A LOT. When I stop using my sample based WW libs and use WIVI, the issue almost goes away. Possibly a bandwidth, timing, sync or latency issue?

Would loved this fixed more than ANYTHING. I rely on DP everyday. Would be glad to help if needed. Do Logic users have this problem? I've tried using the VST version of some of the related plugins instead of AU, and maybe it helped?

Has there been any progress on this? I know VSL's stance has been that it's a MOTU issue, but it is still going on. Things seem to work fine as long as we only use certain plugins that come in contact with the VEPro returns. IE we can get away with sending a VEPro return to a ProVerb or Waves RVerb plugin, but instantly get stuck notes if we make it an Altiverb or Lexicon Plugin.

This has been going on ever since DP 8 and has been a real drag as we are limited in what we can mix with.

Any updates would be appreciated. Thanks!

You keep on ignoring what I said - that it happens WITHOUT DIGITAL PERFORMER IN VE PRO 5 STANDALONE.  How many times do I have to say that?  It is not a DP issue.  If it is - then explain why it happens in standalone also.

Stuck notes occur in the standalone version triggered externally REGULARLY whenever a large group of instruments is playing something complex.  So switching to another DAW is totally pointless.

William, you must have a different issue - the stuck notes issue that we are discussing is unique to DP - this has been confirmed by Audioease developers, Vienna and MOTU. The issue with plug in handling has been identified and isolated and MOTU devs are aware of it. A fix was due in the last DP update but for some reason it wasn't included. 

How are you using the event input plugin with stand alone VEP? This is surely a different issue.

Also - with regard to altiverb - with the very latest version, they have worked around this issue so it now works with out a problem. I've been using Altiverb along side VEP and Vienna Event Input in my last 3 projects and the note drop outs have not re occured. 

 It is not unique to DP, so that indicates it is something other than DP. Perhaps an interaction with that program and VE exacerbates it but the fact this happens in the standalone version - with no plugins other than MIR - indicates something else is causing it within VE Pro.  And this never happened with any previous version of VE/VI.  I have used it since it was first created and never experienced this until now.  

by the way I notice this happening only on one of three slaves I am using - two of the the same configuration exactly but one of them running strings alone.  Also, the number of instruments is not very large, just the complexity of the parts. For example on just a string section of five instruments, all of them have stuck notes if stopped in the middle of a sequence with some CCs playing, fast notes, etc.  So I am not talking about gigantically complex scores at all. 

William - 

Please don't be so confrontational.

The issue myself and others such as Labman are talking about IS DP SPECIFIC - this has been conformed by **extensive** testing and replication and has been CONFIRMED BY THE DEVELOPERS OF DP, VEP, AND ALTIVERB!!! The plugin handling code that gets tripped up in this case has been identified so PLEASE DON'T ARGUE. 

Your specific issue is not DP exclusive beacause it is a different issue manifesting in similar behaviour. I'd suggest that there is more troubleshooting for you to do locally as all of us can run very complex sessions here, even with the event input issues (utalising various work arounds).

You'll get to the bottom of your issue by methodically troubleshooting - not by blaming an unrelated bug which has already been identified and put on the list for developers to fix.

That's not confrontational.  That was my being nice. Also DON'T TELL ME PLEASE DON'T ARGUE.  You want an argument - that's how to get one.

However - An unrelated bug?  How would you know that? I seriously want to know that.    Also, it was put on the list by VSL?  Where did you get that information?   I heard absolutely nothing from them on the issue.