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.

William,

Why are you so confrontational? We are all here to help each other.

As I already said, there is a but relating specifically to dp's plugin handling code tripping up in scenarios where the event input plugin and certain effects plugins are in the same project.

I know this as I have had word from the team at Vienna and motu. It is being fixed and it is motus issue

I know your issue is unrelated beacause it's yours is exhibiting issues under a different scenario.

All of us here are happy to support each other but you need to stop being so aggressive and confrontational and trust that there are guys here who know what they are talking about.

Your issue is specific to your system beacause, let's be honest, you're not the only one using vep for complex projects, and if everyone's setup was broken then there would be 1000s of complaints. You need to methodically eliminate things one by one and you will solve it.

I've just finished scoring a tv series using vep locally and on a slave machine running many many instances of kontakt... No note dropping issues.

You might want to also eliminate specific kontakt instruments as kontakt 5 has some known issues with certain types of scripts, utilised by both ni and third parties. 

And if you haven't already, get in touch with support if your troubleshooting is inconclusive.

i know beyond any doubt that your issue isn't the same as the one myself and others on this thread have identified beacause our issues are solved by taking ether dp,  event input or the offending audio plugin out of the equation. In fact I made up a project that exchiits the behaviour on one track and not on another routing to the same instrument track within vep, just to demonstrate the issue.

if you want help, explain your issue in detail including all software versions, libraries and plugins running when the problem occurres.

What irritates me is you act like your problem is a real one but the one I have is just my screwed up system - it isn't.  There is no more troubleshooting to be done.   And  I already did everything you suggested, listing system details etc. - you didn't see that on the other thread -  but NOTHING has been addressed or changed.   Other people using the standalone system have had this problem also - something else you were not aware of with your assumption that it is a problem unique to my system which is not messed up at all except for this specific error which never occurred until the last two versions of VE Pro. 

William. I sympathize with your headaches, but this thread is specifically for those having issues with stuck notes in DP as the thread title suggests.

You may want to start another thread to discuss with other users solutions to stuck notes with the standalone version. If there are many others out there with the same issue, I'm sure they would appreciate discussing solutions and findings with you.

Let's keep the threads on topic though so that those experiencing this specific issue with DP in particular can share information and findings that will be more likely to be specifically helpful since they will have similar setups.

Thanks so much!

We are discussing a specific issue, the source of which has been identified. You are saying that this is not the case. It doesn't help anyone. These have to be two different problems, both are very real but there is a specific dp bug. 

Are you saying that the motu and Vienna developers are both wrong.

We are all trying to get to the bottom of out issues and your language from your first post here has been argumentative. 

A few of us have spent many hours troubleshooting the dp / event input issue and I've personally worked with audio ease on this to help identify the plugin handling code that was being tripped up. As a result the latest version of altiverb works around this issue.

i don't know why you are calling me a liar on this, I can show you all the correspondence and test results.

Just a thought.... Has everyone with the dp issue made sure they've contacted motu? The ball is in their court to fix the problem code... They have identified it but I've heard that the fix isn't easy. If we all make sure we stay in contact with motu they may well prioritise it.

I emailed MOTU last week, referencing this thread and got this reply.

"There was a separate issue with the VEP Event Input plug-in that was resolved in DP 8.04 (most likely the issue that Dave was referring to), but there is still an ongoing issue with stuck notes when using Event Input plug-in. 

Hope that gets everyone here on the same page at least. I'm glad they were striaght with me about it (which they always are).

I've actually been doing exactly what is recommended in this reply. For now, a lot of my percussion section is in DP (I use MIR Pro for those if needed), and some solo instruments and various other things that would require the Event Input, I have either moved them to DP (but I try to keep DP under 6GB of Real Mem usage), or I create a new instance (which I've done for the brass section). Since I'm using the ARC in LASS almost exclusively right now, I can get away with one instance of VEPro for the string section.

Please keep sharing any info or updates. 

Thanks!

I was actually unaware of the VST3 option in Cubase until recently. By using the vst3 plugin I can avoid the Event Input instances, which solves the issues I was having.
But the bug still exists when using Event Input in Cubase.

According to someone I know that does custom VEPro installs, his opinion is that the Event Input issue (the overall frozen note issue part of it at least) could be due to two things -

1) OSX needs some CoreAudio maintenance work, (comparable to the work Mark Russinovich did for Win 7 - although Apple did their own in ML and Mavericks*). I don't buy this theory personally. DP seems to run about the same on OSX and Windows, whereas Cubase seems to be heavily coded in favor of Windows to be getting the kinds of speed gains I read it gets. (*from an article on dawbench.com about cross platform MP performance). Also, this has nothing to do with part of the actual issue being reported concerning certain reverb plugins and the Event Input plugin.

2) The Event Input plug-in just needs work, and that affects non VST3 users on OSX systems.

I don't know about that claim either. I only present these claims because they come from someone of decent reputation, and I thought perhaps they might make discussion points.

I have no desire to get into a war of words with anybody about these claims (I use OSX, DP/Logic and VEPro and have no intentions of switching anyway - so I'm not biased one way or another because my rig works for me).

Any thoughts on these comments? Keep the discussion going guys. I'm confident between these two great companies (MOTU and VSL), this will get fixed.

Cheers!

I am Windows based, so neither of those explainations apply to me.

I am using MOTU ASIO if that means anything to anybody.

Thankfully I am primarily Cubase based, but I do hope for everyone here that it gets fixed soon, as I have experienced the issue first-hand and have seen how frustrating it can be.