VIP 2.0 - Komplete Audio 6 ASIO crash

I'm using the VIP 2.0 Software Version 2.0.57 (build 2) x64 on Windows 10 with a Komplete Audio 6 Interface by Native Instruments. VIP constantly crashes when I try to switch to the ASIO driver. I tried to reinstall VIP as well as the driver but nothing worked. Visual Studio debugger says that happens because of an exception remaining unhandled, which is such a simple and absolutely unprofessional mistake that is definitely inacceptable and which can easily be found if the software runs through enough tests before it is released. If I pay so much money for it I can definitely expect that this does not happen while doing something common as selecting an ASIO driver. At the moment I am using the Advance at home but as I'm using it I'm constantly losing confidence that it will work stable enough during a live gig. For a someone who uses this product professionally, maybe even as his single keyboard this would be a disaster. It is a great idea but the realization is so bad that I think that I would now either buy something else or program the software myself.
4 people have
this problem
+1
Reply
  • Corey S (Official Rep) April 14, 2016 17:31
    Hi Summerbrain,

    Thanks for posting!

    I haven't seen this come up before and certainly haven't experienced it with any of the ASIO drivers I've tried thus far.

    I assume you don't have this problem with any other DAW on this computer?

    Is this interface in use by any other software at the moment? Even just as the default soundcard? If so, I'd recommend to set the default device to something different and even try disabling the Audio 6 in your Windows Sound preferences and trying again.

    Ensure that the Audio 6 is connected to a free USB port on your computer along with the Advance. In this case, avoid USB hubs while testing. Also, it may be a good idea to uninstall any conflicting ASIO drivers like ASIO4All.

    Let me know how this goes and tell me more about your setup and your process for re-creating this so we can look into it further!

    I hope this helps!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I works fine with Cubase Elements 6 and it uses to work with the standalone version before, especially while I was still on Windows 7 I didn't have any problems. I do not use any USB hubs. If I am starting the standalone version and the Windows default driver is selected I can switch it from Windows Audio to DirectSound but not to ASIO. In the first place it switched to ASIO and then no Audio Hardware was selected and then the usual message box that no device could be found appeared along with another one which said that VIP_x64.exe does not work any more. I could still select VIP and switch to my Interface but if I close the Window that says that VIP does not work any more VIP is also closed. Because I also have Visual Studio installed I could select it and see what's going wrong and there I could see among many other problems that there is a so-called exception which is thrown by the ASIO library I assume but which is not handled by in this case VIP so it is passed on to the operating system and then the application crashed. The system says that it is an access violation while trying to write at a certain position in the random access memory (RAM). I'll advice you to pass that on to your developer team.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Corey S (Official Rep) April 19, 2016 20:37
    Hi Summerbrain,

    I'll be happy to pass this to our team, but as I mentioned, this doesn't happen with any ASIO devices on our end. I'm not sure that the Audio 6 was tested specifically though. Does this have a dedicated ASIO driver or does it use ASIO4ALL?

    Could you recreate this with a second computer?

    Can you confirm any of the questions/troubleshooting I asked previously?

    Did you update to VIP 2.0 or install straight to the latest version?

    When you switch to ASIO, what is listed as the Device if not already set to your Audio 6?

    Any difference if you run VIP "as Administrator"?

    Thanks! Let me know!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Just a heads up. I had my Advance at a friends house this weekend who also has a K Audio 6. Although his system is running on Win 7 x64, we had zero problems and no crashes.

    Summerbrain, any chance that you have the log from the crash?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • 1
    Hi! I think I found a solution to this problem... First I have to say that I have the same setup and issue as the OP, I'm also on Windows 10. I've tried many things and did a lot of search on forums etc but never found an answer... Then for no reason I tried to open VIP but this time the 32bits version. To my surprise all the Asio options were available! I tried a couple sounds, tweaks, etc. Then when I opened the 64bits version everything was fine. I only get the same crash when I try to select the Asio DirectX driver... But all the other drivers are ok. (Asio of my Focusrite and my M-Audio works) I've tried a lot of things but pretty sure that was the fix. Hope this will help someone else... Martin ;)
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • This reply was created from a merged topic originally titled VIP2.0 crashes when attempting to swap to Scarlett 2i2 ASIO driver.

    Hello, Have just been trying a new USB audio device and VIP2.0 doesn't seem to like it. Whenever I try to use it as an audio device by selecting it within VIP then VIP will crash with the message VIP_x64.exe has stopped working.
    The 32 bit version of VIP2.0 works fine if I try to change to this audio device .Whenever the VIP2.0 (32bit bit version) is set to use the Scarlett (Focusrite USB ASIO ) , the 64bit version then won't launch at all from the desktop (in standalone mode).
    If it is set to another audio device first in the 32bit version of VIP2.0 ,exit the program and then the 64 bit version is launched it will now launch ok but immediately crashes if I attempt to change the audio device to Focusrite USB ASIO

    Is this a problem with VIP or the Focusrite USB driver or some other system setup problem?
    Swapping to this audio devices works fine in Windows10 enviroment in general and in any other VST that has a standalone mode (eg all the Arturia V collection any of the Native Instruments).Also works fine in Halion Sonic and Cubase8

    Martin
    • Corey S (Official Rep) July 11, 2016 15:05
      I'm merging you here because this is a similar topic and the user above was able to resolve it.

      Maybe it's a matter of which ASIO driver you are using for the focusrite?

      Have you tried running VIP as admin?

      I would ensure that no other software is using the device at the same time and make sure that the sample rates match up before switching. I'm not sure if the Focusrite has a control panel to assist with this or not.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited

  • Corey,
    I have tried your suggestions but it still crashes.How is ASIO /audio device switching handled in the 32 bit version of VIP compared to the 64bit version?The 64bit version crashes everytime wheras the 32bit version will switch everytime without an issue.The 32 bit version will also launch evrytime when set to Focusrite USB ASIO whereas the 64bit version won't.Admin makes no difference,setting the sample rate makes no difference also tried 3 versions of the Focusrite driver.I'm convinced it's a VIP2.0 64bit version issue as every other application works fine when trying to switch audio device.Either that or the way the Focusrite driver is implementing something that the 64bit version of VIP doesn't like.The device is the Scarlett 2i2 (new version),has it been tested?

    Martin
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I have a workaround for now and that's to run VIP as a VST within Cubase where cubase handles the audio device/ASIO but there is display issues with the lower display of VIP when used in VST mode ie where the control panel rotary controls and buttons are displayed

    Martin
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Just for info

    It would appear the problem lies with the Focusrite driver/ASIO . I've just been trying another USB audio device, the Presonus audiobox Ione which works faultlessly in 32bit and 64bit versions of VIP2.Can swap freely between devices without issue (with the exception of the Focusrite USB which always crashes the 64bit version of VIP)

    Latest Focusrite 2i2 driver used was 4.11.0.107 released on the 12th July
    Was hoping this might fix this issue but it appears not to.

    Martin
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Corey S (Official Rep) July 29, 2016 19:00
    Hi Martin,

    Thanks for being patient and testing all of that out.

    I can't say that the focusrite 2i2 was tested specifically with VIP, but I've passed this on to our dev team to see what they think.

    If you haven't already, try updating to the latest VIP 2.1 that was released yesterday and see if this improves the response at all.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Corey,
    Thanks.Already tried it with VIP 2.1 and does the same
    After a bit more messing and experimenting it is looking more and more like something in their driver might be the problem.I tried their latest 4.110.107 driver with Rapture Pro (64bit version) and it crashed it like it does with VIP.
    No problems though in 32bit versions of any program including VIP.

    Googling an older Focusrite windows 10 driver compatability page they show a driver version 2.5.1 which needed to be manually installed from the device manager after the initial installer has run and gives a windows warning "driver compatability cannot be guaranteed".
    This driver works with the 64bit version of VIP and Rapture Pro 64bit

    Martin
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • I have the same problem - I tried installing the older Focusrite driver 2.5.1 as suggested above but the 64bit version of VIP still fails, giving the same message that VIP_x64.exe has stopped working. 32 bit VIP works but then I can't access all my 64bit plug-ins. Starting to regret changing my old internal soundcard for Focusrite Scarlett 2i4. It seems to me that Focusrite drivers are not presently compatible with VIP 64bit presently. Any workarounds?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • HAve the same problem and want a fix...anyone else have any solutions???

    VIP_x64.exe
    1.0.0.0
    57d94d31
    focusriteusbasio64.dll
    4.12.0.141
    57c81db0
    c0000005
    00000000000021e5
    2c0
    01d2205863a1952f
    C:\Program Files\VST Plugins\VIP_x64.exe
    c:\program files\focusriteusb\focusriteusbasio64.dll
    4ae52a6e-2d47-4f77-9669-a7e7708542db
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • There sia major flaw in the Focusrite asio driver. I checked my Event Viewer on windows 10, and it is indeed the driver crashing VIP. :(
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • 1
    Focusrite have released a new driver version 4.14 for the 2nd gen in the last few days .Haven't tried it yet with VIP/Advance as i'm currently using my MX61 keyboard as a MIDI controller ,but Rapture Pro that used to crash now doesn't when I switch ASIO's to Focusrite .Also in their release notes it states it fixes 64bit standalone plugin problems

    Martin
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Hi Community, i have the same Problem. VIP Crashing on ASIO. I have the RME Fireface UC Interface and all other Apps have no Problems. This is a Challenge for Akai, i Understand that it may be difficult to get it Working with all vendors but on the other hand i have the impression that some Programmers must be under drugs. I could not afford this type of work in my job, i be workless immediatly. I dont know what to do, the idea of VIP is great, but to achive it seems to be impossible.
    • ...Just an observers thought here Harry/Corey/All,
      RME have apparently been independently performance tested to have some of the most robust, lowest latency drivers of almost any interface to date. This appears to (not coincidentally) be attributed to the fact that they still do their own driver development and testing "in-house". Not farmed out to a third party "indifferent" developer which most companies do now. I have heard it explained to me (from more knowledgeable and battle-wary audio folks than myself), that Focusrite do trade more heavily on their "reputation and name" over their modern day drivers robust coding and program design. But that alone is not entirely my point here...

      What I'm trying to get at is; if these issues are still happening even with RME drivers, we are possibly all screwed when it comes to potential VIP workflow killers with more generic driver centric systems!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated happy, confident, thankful, excited