No, it doesn't.  I'll be running MidiMonitor in the background today to see what kind of messages are involved, maybe that'll help get to the bottom of this.

Is there anyone out there that has experienced this and has tips?

This is driving me crazy AND KILLING MY WORKFLOW!

I'm about ready to ditch this, as much as I don't want to.

How about using the panic button inside Kontakt 4? Does that help? Also, is multithreading enabled in Kontakt? If so, try disabling it.

Yes, of course, the panic button works, but the mere fact that its happening at all and so frequently, makes it a real productivity issue.

Yes I have multithreading and the Memory Server disabled.

I definitely recommend disabling multithreading in Kontakt. VE Pro already spreads processing ideally over cores, and Kontakt could interfere with this. Also, if you're using Kontakt in a 64bit Server, you might want to disable the memory server as well to increase stability.

Karel, did you read my prior post?

Sorry, misread "disabled" for "enabled". This is strange though. VE Pro receives the MIDI from the master host. It doesn't remove or add extra MIDI messages, so it should behave identical to using it in the master host. However some libraries for Kontakt seem to be an exception to this, possibly related to bad timing implementations used in Kontakt. I'll try to find a way to circumvent this, but so far haven't even been able to reproduce this behavior.

i'm wondering if there is any more info about this problem. i've got a sequence that i can hardly start without notes hanging, while playing, or after stopping.it seems to affect mostly two plugins, broadway brass (on an i7, windows 7, kontakt 4.1.1) and sample modeling trumpet/trombone and all saxes,(on a slave 2.8, 8 core mac 10.6.4, kontakt 4.1.1). the host is logic 9.1.2 on a 3.0 quad core mac 10.6.4.

thanks for any help!

dan

I have still the same problem too, playing Kontakt samples from a slave, but only on playback, not while recording or playing midi. When I run the same template in VE Pro standalone, and send midi via MidiOverLan, or hardware midi, there are no hanging notes, only in server mode via ethernet audio. Most of the time it's fine, but then suddenly some notes start to hang. One odd thing that I noticed is that it only happens to me when I do 4-5 part writing with quite independent voices. Block chords are never a problem. The slave also runs a lot of VSL instruments with no problems. 

host: Logic 9.1.1 (in 32 bit mode), VE Pro 6150, Mac Pro Intel 8 core, 10GB RAM, Mac OS 10.5.8

slave: 11 instances of VE Pro 6150 (64 bit server, multiprocessing 1 thread per instance) , Kontakt 4.1.0 (multiprocessor support disabled) , running Spitfire Audio library, Windows XP64, quad core Xeon 24GB RAM

Karel, would it help if I sent you the Logic file in question (I could mark where notes hang) and the corresponding Vi frame file (you'd have missing Kontakt instruments though)? 

@Gubik said:

I've noticed that the hanging notes mostly takes place during playback in cycle mode and within identical MIDI channels from differnet MIDI port. For example if I playback a musicial phrase using MIDI Port 2/Midi channel 1, an unwanted hanging notes appears randomly at MIDI Port 1/Midi channel 1. This might suggest that the "Micro" used to identify the "Port" might not functional properly in Logic Pro.

Very interesting. This is the likely cause of my hanging notes too, as each string instrument has its own port, e..g  ch1 solo violin, ch2 violin chamber strings, ch3 violin sord chamber strings etc etc. This makes it very likely that most parts share the same midi channel. For me it happens just as much when not in cycle mode.

I am still using VE Pro 4.1.8008, each 'port' is in a separate instance, but you seem to be using VE PRo 5's new multi port facility? What's a "Micro"?

Another side effect of what you're describing is a problem with Mackie Control Universal. The MCU doesn't recognise separate tracks with the same midi channel, even if they are cabled to different VE Pro instances. This results in a weird duplication of fader channels on the MCU. My workaround is to always send to some unused MidiOverLan ports at the same time, ie sending midi into blank space, just so that the MCU can distinguish between tracks.

Dom

Did you try using IAC  ?

Did you look how much memory is left in Activity monitor ?

This has solved my hanging notes problem

I have this issue often with Morphestra.  I definitely think certain libraries are problematic with this.  All notes off does not kill it, you have to hit panic in Kontakt.