Kontakt 5 Audio Engine Reset every time I press "Stop" on Sonar. Help???

Hi guys, super annoying issue here.
I've installed the X1d patch on my Sonar Expanded and ever since I have issues on Kontakt 5.
Basically all instruments are loaded and I can play along (reharsing a take) or record on Sonar.
When I press "Stop" on X1 either on the screen or via the MIDI controller, Kontakt 5 stops all sounds and I'm forced to hit the Kontakt "reset audio engine", shown as a big exclamation mark.
 
I have already spend a week with Native Instruments support on the phone and they even took a log of my machine system configuarion (quite a clever tool those guys have actually).   And in the end the fault, according to them, sits with Cakewalk.
 
I've tried to downgrade to X1c but at this point my registries must have been changed for good and I really don't want to whipe Sonar from my machine and start over.
 
Any ideas anyone?  I can still do my work, but it's incredibly annoying having to reset the engine in Kontakt some 200 times a day!!!!
 
Thanks
Max

Can you test K4 and see if that works?  I run multiple instances of Kontakt with little trouble.  Sometimes I run K3.5, K4 and K5 in the same file because it is easier to find some instruments that way.  K5 is by far the most quirky.   

Cool!  i'm going to try that and see if it helps my notes getting stuck on...

After a night of more tests and installations I can tell you this:

- Blogman's suggestion on the "Play effects tails after stopping" has fixed the problem for all libraries but 1

- The issue still persists with Cinematic Strings 2.   Since this can't be installed on K4, I can't even make a comparison with that to see if it works.    So.....as an alternative, I'm thinking of downloading some demo version of another DAW and test Kontakt with that to at least see if the problem is being caused by Sonar,  K5 or the library itself.

I'll report on any progress and try not to shoot my PC.  

So much time wasted around issues and configurations these days instead of making music!

From another forum:



Jimbo 88 @ Wed Jun 20, 2012 10:04 pm wrote:
HEy I love Cinematic Strgs 2.0, but I'm having a problem with notes getting stuck on (mostly in legato mode). Anyone else have this and is there an answer?


YES! I'm having that same problem. Thought it was my controller. Thought my DAW wash't sending note off, thought it was a low memory condition. But it happens in stand alone too.

I haven't found an answer. Only time I remember it working was in Logic 64-bit mode. But I've been trying to solve this problem for months now and can't.

I reported it to CS2. Someone else suggested it was a script error. That might be right. But I know several people that's happening to. So, report it to CS please.

Hey I contacted Cinematic Strings and Alex (the big guy there) sent me patches that correct the problem...

So it is working fine for me now. 

Massimo Max send me a PM and I will send you these patches if you'd like.  They work great!  

Jimbo ...

New to Sonar X2, but having the same issue with Cinematic Strings 2.0 as well as East West's Hollywood Strings. What was the patch sent to you to correct the issue with note either hanging, or the software synth (Kontact 5) not playing any longer? Alex at Cinematic Strings is on-vacation for a few weeks, and I have a deadline to meet.

Any help you can provide would be great. Thanks.

Thank you, Jimbo ...
 
I contacted Cinematic Strings, and they have some great support there. They were not, however, able to yet identify the issue. But ... with some inability to sleep (yes, it worried me), I began thinking: could it simply be a controller within Sonar? Well ... it was! 
 
There is a section in MIDI in the Preference section that says to "ZERO OUT CONTROLLERS AT STOP" (or something similar to that). Somehow, someway, that got turned on while upgrading. What that does is turns ALL controllers volume to ZERO directly at the synth. This is especially common in the newer VSTs like East West's Hollywood Strings (PLAY mechanism for sound), and KONTAKT. How I noticed this was I happened to have been using the mod wheel while recording Cinematic Strings, but I noticed when I paused or hit STOP, the mod wheel went back to zero. After thinking about it, I realized it had to be a midi control ... and it was.
 
The article/notation is buried in the Sonar X2 online site at Cakewalk -- the article is here: 
http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X2&Lang=EN&Req=Playback.33.html
 
Should someone have the same issue, I would recommend reading all the articles that Sonar has online; it's a great resource.
 
Thanks for the help.
 
GManOC

Thanks a lot for finding and posting the solution to this problem, GManOC.  You just saved me a lot of time. I had the same problem running Cinematic Strings 2.11.  Unchecking the "Zero Controllers when Play Stops" option in Preferences - Project - Midi cleared it up for me.
 
My Kontakt Version is 5.2.1.6382. Sonar X3c.
 

Digging further into this, I found that the specific controller that is affecting Cinematic Strings 2.1 is CC 1 which is controlling Modulation.  Cinematic Strings uses modulation as an expression tool.  When Sonar resets all CCs to zero on stop, the Modulation goes to zero and you can't hear the strings.  
 
So probably the better solution is to leave the "Zero Controllers at Stop" checked and then to set up an envelope at the beginning of the strings track to initialize the controllers to whatever you want them to be.  I tried this and it works fine.
 
I don't think Sonar's default setting is much of a usability issue; it's just something that you have to know about the software.  Actually, I prefer having the controllers default to "zero at stop" so that when I restart I'm starting with variables initialized to known quantities rather that at whatever value they happened to have when I pressed the stop button.
 
 
 
 

That setting can expose a similar issue with Reaktor, depending on the ensemble that is loaded.
 
I drove myself NUTS trying to figure out why the pitch on a Reaktor preset was ending up playing a whole step flatter than when it started, and it ended up being something that the ensemble did because of the Sonar setting all controllers to zero, per that setting.
 
So, after going round and round and round on it, I finally stumbled across that zero controller setting and removing the check fixed that problem completely.
 
I think it is more of an issue with Reaktor than with Sonar, just in the way they set that preset up to react like that.
 
I think the same thing in Kontakt - that they could have set it up differently, so that simply zeroing out controllers in Sonar wouldn't cause such goofy problems.
 
Just my opinion on it, 
 
Bob Bone