Vienna Symphonic Library Forum
Forum Statistics

196,017 users have contributed to 43,014 threads and 258,388 posts.

In the past 24 hours, we have 4 new thread(s), 22 new post(s) and 132 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VE PRO - Kontakt 5 Crash ....Looking For Vienna to Look into this!

  • VE PRO - Kontakt 5 Crash ....Looking For Vienna to Look into this!

    D
    D

    I thought I would repost this under its own category to try and get Vienna to help and respond.

    A couple more observations.....

    I have 6 slave machines.  2 of them do not have any Kontakt's and they have never crashed or froze up. 2 of them have a lot of Kontakt 5's and freeze about once a day.  1 of them has a few Kontakt 5's, lots of Kontakt 4's and freezes about once a week.  1 of them has maybe 1 or 2 Kontakt 5's, lots of Kontakt 4's and freezes every now and again.

    It seems obvious that the more Kontakt 5's on the machine inside VE PRO 5 the more frequent the crashes.  The crash once again is no audio or midi  coming from that Vienna project.  The transport play button still functions but nothing else.  If I try and turn the project off Ve pro goes all white and locks up.

    I believe Cubase is part of the equation as I am not sure I have seen anyone have this problem that does not use Cubase.

    This has been a problem for over 2 YEARS......I wish Vienna would chime in and take this serious and try to solve this. Telling us to contact Native Instruments does not seem to be a solution....Vienna needs to figure out what is going wrong.
  • D
    D

    I just talked to another composer who has not upgraded to VE PRO 5 and is still using VE PRO 4 with Cubase and Kontakt 5 and is having NO issues.

    I think my problem lies with VE PRO 5, Kontakt 5 and Cubase.  Not sure if Cubase is part of the equation but it might be.

    I am going crazy wasting so much time with this problem.  Can Vienna please try to jump in and help solve this?
  • marnixM
    VSL Team
    marnixM

    Hello dlpmusic,

     

    Please send a support request with a description of the problem to , along with crash logs/dump files, your system specs and screenshots of your VE Pro Preferences, so we can better look into your issues!

     

    We successfully use the combination VE Pro 5/Kontakt 5/Cubase 7 on a daily basis here, so I am positive we will be able to sort out what might have gone wrong on your system.

     

    As a first trouble shooting step, please disable Kontakts Memory Server (/Options/Memory/) and Kontakts Multiprocessor Support (/Options/Engine/) when using Kontakt in VE Pro 5 if you haven´t done so yet - does that already make a difference?

     

    Best, Marnix
  • G
    G

    Did those adjument but the bug remains...I will send a ticket but so other user can track similar isue here is the situation :

    When alternating from Nuendo 5.5 to VEP sometime VEP switch in split mode for the GUI (mixer or edit VI is separate from the instance) and then VEP crashes...
  • D
    D

    Here was the email I sent to support.

    There are no repro steps.  I have 6 slave machines....4 of them running lots of Kontakt 5's.

    Every day I get random projects becoming unresponsive within a Metaframe that has 2 to 3 projects.  When this happens the other projects are working with in the same metaframe.  
    The freeze causes no midi and audio to pass through to Cubase....in fact no midi or audio is working inside VE PRO in that project.  The transport button still works but nothing else.  In task manager usually the processors are peaking the machine do to this freeze.  If I try to disconnect VE PRO from inside Cubase 7 then Cubase locks up.  
    I have to force quit VEPRO 5 and then reload and reconnect.
    There are never any crash logs as VE PRO never totally crashes it just locks up.  I have turned off multiprocessor supprt...no difference, and no memory server as these are all Windows 7 PC's.
    Most notably this NEVER happened on VE PRO 4 and I know a composer that has a very similar setup and still does not have this problem as he is still using VE PRO 4.  I know several others that all have the same issues when Kontakt 5, VE PRO 5 and Cubase/Nuendo are in the equation.
    This has been happening since day 1 of VE PRO 5 for me.

    A couple more observations.....

    I have 6 slave machines.  2 of them do not have any Kontakt's and they have never crashed or froze up. 2 of them have a lot of Kontakt 5's and freeze about once a day.  1 of them has a few Kontakt 5's, lots of Kontakt 4's and freezes about once a week.  1 of them has maybe 1 or 2 Kontakt 5's, lots of Kontakt 4's and freezes every now and again.

    It seems obvious that the more Kontakt 5's on the machine inside VE PRO 5 the more frequent the crashes.  The crash once again is no audio or midi  coming from that Vienna project.  The transport play button still functions but nothing else.  If I try and turn the project off Ve pro goes all white and locks up.

    I believe Cubase is part of the equation as I am not sure I have seen anyone have this problem that does not use Cubase.

    Thanks,
    Danny
  • D
    D

    Support can not seem to help as of yet as there are no definitive repro steps that cause this freeze and no crash logs are ever created.

    Can anyone else confirm that they are seeing this problem?  If so any other ideas to add on what might be causing this?
  • L
    L
    I'm having a problem as well but Sonar X2 DAW. Kontakt 5 error crashing VEP when I load my session. working on getting my crash details together. Not always a snap to gather crash data from slave machines. I fell ya re: wasting time. >:(
  • A
    A

    Can the OP post here if he/she was able to solve the problem? I am having issues with Cubase 8.0.0 VEP 5.3.13407 and Kontakt 5.3

     
  • S
    S

    Bump!

    I'm having the same issue but I'm also a n00b at this so that might explain it.

     

    I'm trying to run 2 multioutput instances of Kontact and 1 multi-instance of PLAY. VE pro runs PLAY and 1 Kontact instance nicely, but once I start loading instruments into the 2nd Kontact instance, I get slow-death crashing like I've not experienced since the mid-90's. It's not consistant though, and the slow-death can happen in the other 1st Kontact instance (if I don't talk nicely to it, that is).

     

    It's gotten to the point where as soon as I see the beach ball, I have to force restart the machine because it never recovers, and thus, no crash report either.

     

    What could I be doing wrong? It works so fast when it's working (which is not often for me at this point...)
  • P
    P

    "... but once I start loading instruments into the 2nd Kontact instance, I get slow-death crashing like I've not experienced since the mid-90's."

    I'm in Logic. My Kontakt crashes are immediate when I load, but like you, it's the second instance. Over a year ago, I contacted VSL, and they directed me to Kontakt. Kontakt never replied. 

    Listen, maybe this will help you: if I open VSL before Logic, and I load a successfully saved metaframe with Kontakt instruments built in, it's fine. Then I load Logic, it connects to the instances, and there are no more issues. 

    But, if I try to launch the very same Logic file without Vienna pre-loading -- so Logic drives the load -- then I crash on the second attempted instance load. 

    So I'm just throwing out a thought here that you could try a pre-loaded metaframe, then launch PLAY. 
  • S
    S
    last edited
    last edited

    @plowman said:

    "... but once I start loading instruments into the 2nd Kontact instance, I get slow-death crashing like I've not experienced since the mid-90's."

    I'm in Logic. My Kontakt crashes are immediate when I load, but like you, it's the second instance. Over a year ago, I contacted VSL, and they directed me to Kontakt. Kontakt never replied. 

    Listen, maybe this will help you: if I open VSL before Logic, and I load a successfully saved metaframe with Kontakt instruments built in, it's fine. Then I load Logic, it connects to the instances, and there are no more issues. 

    But, if I try to launch the very same Logic file without Vienna pre-loading -- so Logic drives the load -- then I crash on the second attempted instance load. 

    So I'm just throwing out a thought here that you could try a pre-loaded metaframe, then launch PLAY. 

     

    Hi - Thanks for your response. Logic for me as well... I'll give what you suggest a try, see what happens.

     

    Was also thinking about running Kontakt on the main machine and PLAY on the slave, maybe having it in it's very-own-country would help. We'll see.

     

    Thanks again for the advice!
  • P
    P

    Cool. Let me know. I saw "PLAY" and mistook it for a DAW. So since you're in Logic, absolutely give this a try. 

    To this day, if I try to let Logic load my Vienna Ensemble Pro Server, it crashes on the second instance. And I know it's Kontakt because A. the crash log, B. non-Kontakt loads are fine, and C. Dietz told me so. :-)  

    So finangle a complete metaframe, pre-load it (Kontakt and all), and then see if Logic can connect to it without incident. Kontakt within VEP has never crashed for me once I'm in Logic and the handshake has been made. 
  • H
    H

    I've been having the same issues ever since upgrading my system to VE Pro 5, although my entire machine locks up so there is no way for me to know whether VE Pro (Play/Kontakt) is causing the crash or Nuendo (my DAW).

    Does anyone else have issues with their entire machine(s) locking up? It has been happening to me 3-4 times a day and I am wasting so much time dealing with it. I have to do a hard reset everytime it happens and wait to reload my VE Pro metafile again. I have been think about rolling back to OSX 10.9, I'm currently on 10.10 and am too scared to try El Capitan. Help!
  • PaulP
    VSL Team
    PaulP

    Hello hanantownshend, 

    Try eliminating PLAY from your template and see what happens. Then do the same with Kontakt. 

    Unfortunately that´s the only way to find out what´s wrong when you get lock-ups.... 

    Best, 
    Paul

    Paul Kopf Product Manager VSL