Kontakt 5.4.1.221 crashes when loading ASIO Quad-Capture driver

I have been running fine for ages and ages, but since I updated to the latest Kontakt, I can no longer use the Quad Capture ASIO driver. As soon as I select it, a box appears saying Kontakt has had a major problem and has generated a crash dump. I have sent NI the dump today, but just wondered if anyone else was having issues? WSAPI works, but the latency is way too big to be usable.

 

Exactly the same problem here. On windows 8.1 I should add.

 

At least I am not alone then! I am also using Windows 8.1. I haven't had any response from NI tech support yet.

 

Have you heard anything back yet? I just submitted a report today, so hopefully it will get looked at soon.

 

I have a problem with Roland Duo-Capture ASIO (presumably a close relative of Quad Capture) and the latest release of Kontakt 5 (also Battery and Komplete Kontrol) under Win 8.1 64-bit. Standalone K5 will not start because it wrongly reports that the Roland driver is stopped. Other NI apps (and any others that I use) work fine. NI tech support is providing nothing useful and tells me that "this issue is not known in general".

 

I have had a telephone conversation regarding it with support and the crash dump was being passed up to the appropriate dev engineers last week to look at. I will try and get an update tomorrow.

Regarding the Duo-Capture ASIO issue...With the Quad-capture driver, if Kontakt crashes, it brings down the driver until I reboot the computer. When it is down, Kontakt reports it is "not running". Then after a reboot, the first attempt to run Kontakt causes a crash again.....second and further attempts "not running".

 

Hmm ... interesting. The Quad- and Duo- behaviours seem to be similar, but not identical. In my case, the driver is not actually stopped or stalled, and Kontakt does not crash, so no reboot is needed. But it sounds like NI and Roland need to compare notes here.

FWIW, some time ago, when I did have problems with my DAW that were stalling the Roland driver, I was having to reboot (very tedious). I then discovered that if I physically powered down the Duo- , changed its sample rate, then powered it up again, the driver would restart, thereby avoiding a reboot. I know that the Duo- is different to the Quad- in that Duo- has a hardware sample rate switch, but maybe you can find a similar way of persuading the driver to restart for the Quad-. HTH

 

Thanks - glad to hear that things are progressing.

 

In my case selecting the QC asio driver causes Kontakt to display a warning message and to write a crash dump. I am able to continue using Kontakt switching to higher latency wasapi drivers, but the QC driver is subsequently locked and unavailable to all other programs, entailing a reboot. All previous versions of Kontakt 5 and 4 were fine and I can still use the same driver with the latest version of Reaktor.
It would interesting to hear from anyone in the same circumstances who can run the QC driver with no problems.

 

Well, at least NI has acknowledged there is an issue now. I don't think I'll be laying out for Komplete 10 until there is a solution, because I am concerned that as each app is updated, each will show the same problem.

 

Has anyone got any help with this? I just updated to Komplete 10, Kontakt 5.4.1 and I'm having the exact same issues with my Quad-Capture.

 

I contacted support over a week ago but have yet to get a reply. I'm sure these things take a while though. I'd suggest that you submit a support request as well - assuming you haven't already done so. The more the merrier

 

I am having this exact same issue, quad capture driver 1.52, latest kontakt, current win 8.1 64bit.

 

Yep, same problem.
Not sure who's problem it is, but got sick of waiting for a fix.
Just got a Steinberg UR22, and all is fine with the latest Kontakt and Cubase 8.

 

Same issue here, and with the latest patch (5.4.2.245).

If it helps anyone (or indeed NI support), this is the crash summary I get, and it's very specific to opening the Quad Capture ASIO audio driver in standalone mode. If I run inside Sonar, it's fine, presumably because Kontakt 5 isn't directly opening the audio device. I have the identical issue with Battery 4.

Code:

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    Kontakt 5.exe
  Application Version:    5.4.2.245
  Application Timestamp:    545a6d87
  Fault Module Name:    MSVCR120.dll
  Fault Module Version:    12.0.21005.1
  Fault Module Timestamp:    524f83ff
  Exception Code:    c0000005
  Exception Offset:    000000000003c963
  OS Version:    6.3.9600.2.0.0.256.48
  Locale ID:    2057
  Additional Information 1:    4d24
  Additional Information 2:    4d245b520caa05791c1c41c9e8364bd8
  Additional Information 3:    8034
  Additional Information 4:    803413ef78555e0b9d2becb696e97bea

I wait in keen anticipation for Native Instruments to wake up and investigate...

 

The new 5.4.3 update has fixed the issue for me -

 

It sure has fixed the issue - for Kontakt at least

I hope Battery is getting fixed too. I wonder if NI just copy and paste the code around between their products

 

That's weird. It hasn't fixed the issue for me.

 

To owners of the Duo-Capture EX and Quad-Capture interfaces- have you tried increasing the size of the sample buffer on your interface as part of the troubleshooting process? About a year ago I started having problems with the UVI Workstation plugin crashing pretty regularly when I used the Duo-Capture interface (it was either after a UVI Workstation update or a Cubase update). I was able to eliminate the crashes by bumping my buffer size one notch in the Duo-Capture control panel. I always use Direct Monitoring, so buffer size/latency is generally pretty transparent to me.

Someone mentioned the Steinberg UR22 though- I can confirm that its drivers are a little more stable, and perform a little better than the Duo-Capture, although I think the Roland is a generally fine little interface.