If it's driver-related, does the problem go away if you use WDM instead of ASIO or vice-versa?

Anderton
If it's driver-related, does the problem go away if you use WDM instead of ASIO or vice-versa?

I can't really go the WDM route as I use a VS-700 plus an Octa-Capture in VS EXP mode.
 
Anyway, the weirdness continuous: I did reinstall VS-700 drivers (just to be sure) and now that project I started off the template works (i.e. my reproducible crash when opening melodyne is gone), but the original crash still persists.
 
I did browse NI forum and others - It appears that Kontakt is not the most stable piece of software when used inside a DAW. It seems to be crashing PT a whole lot ... well, I doubt I'll ever find the real reason for the crash, but I'll let you know if I do...
 

I use Kontakt EVERY day, ALL day, and it never crashes on me - and this has been the case for forever.
 
There MUST be something else going on ( I hope), 
 
Bob Bone
 

robert_e_bone
I use Kontakt EVERY day, ALL day, and it never crashes on me - and this has been the case for forever.
 

It was like that with X2a (no problems in 9 months) ... but now it's X3b, K5 updated to latest version, plus more WAVES plugs in use ...
 
@Bob: Which version of Kontakt are you using (build no?)? What are you using as your settings for multi-processor support for K5 (not Sonar): all cores, a few cores or no multi-processing? It's not the source of the crash, but I've read different advice in different places, so I don't know what to believe ...

I use 5.2.0.6361, and have done NOTHING to change any default of Kontakt.  It just works, and causes no trouble at all.
 
Bob Bone
 

I've been using Kontakt since it was released, now on v5 and I'm not having any problems on either win 8.1 or win. 7 x64 with Sonar from 8.5 every version through X3b. It's one of the most stable pieces of software I use. Stand alone, Studio One, Reaper 4, PT9HD,

Also using kontakt5 here on win8 with a quadcapture never had a hint of a problem.

I would start by doing a disk integrity check.

The mystery saga continues. This is sort of my personal warfare against a non-behaving project ...
 
Disk integrity checking did not find anything. Neither did other system checks and tweaks (on/off). Same applies to special Sonar settings in AUD.ini etc.
 
So then came X3c - but still the same crash when opening the project. It looks like I can only open it (at a 50% chance of success) right after a reboot. 0% success if I used Sonar with a different project before.
 
Project corruption may be the most likely reason for this ... so once I got it to open, I started freezing synths to see if that helps ...
 
Well, it does. After freezing one Kontakt instance, the project opens without crash. However, the next weirdness appeared: I cannot freeze the other Kontakt instance (which contains several synths in the rack, but only 2 are fed by unmuted MIDI tracks). I can see in the background that the wave file is written to the audio directory, but when the first of two tracks is bounced, freezing just stops and reverts to the unfrozen state (with the wave file being deleted again). Anybody seen that before ...??? Something odd between Sonar and Alicia's Keys or Heaviocity going on ...
 
 
 
 

UPDATE:
 
Since that last post above I had that problem (which was really the only one with Sonar X3) a few times and somehow I noticed that (a) it only happens when Kontakt 5 is being used in the project and (b) Kontakt 5 tracks are not frozen ... so I developed the habit of freezing whenever possible ..
 
About a year later I could successfully track that problem down to only happening with the Roland Octa-Capture interface (no crashes with the VS-700) ... so this was clearly a NI / Roland issue and I reported it to both  ... not expecting anything from Roland (from past experience) ... but I got the reply from NI saying this is a known issue (but no mention whether this will be fixed or not) ...
 
So I kept the Octa-Capture off when doing Kontakt work ... and voila no more crashes ...
 
Anyway, today I was surprised to find a Kontakt 5.4.3 update which actually lists "a fixed crash with the "Roland Quad Capture Driver" audio interface ... so maybe this resolves the last issue I had on my studio system :-)
 
<<yet I won't be able to test until next week ... need to finish a client project first>>
 
 

I've had similar issues with Kontact 5, especially using Alicia's Keys and Session Horns - I have the Quad-Core. Freezing is a work-around which helps but obviously not useful if I'm developing a piece. I've been on to NI and they state a known issue - this is a known Bug (KT5-2224) and apparently - 'The Prio is set to HIGH now. So i think a fix will be released soon.'