Vienna Symphonic Library Forum
Forum Statistics

181,740 users have contributed to 42,180 threads and 254,564 posts.

In the past 24 hours, we have 1 new thread(s), 12 new post(s) and 61 new user(s).

  • After VEPro 7 install - all NI VST's crash!

    last edited
    last edited

    Hello,

    All of NI's instruments crash after installing VSL pro 7; they won't open in standalone mode either. I can only attribute this problem to the new install since I've been running all previous versions for years without any problems.

    Here's the crash log for Battery 4 but again to be clear none of NI's VST's are working (kontakt 6, Absynth, FM8, Massive, Reaktor 6) :

    Log Name: Application

    Source: Application Error

    Date: 5/13/2019 10:50:47 PM

    Event ID: 1000

    Task Category: (100)

    Level: Error

    Keywords: Classic

    User: N/A

    Computer: Owner-PC140969

    Description:

    Faulting application name: Vienna Ensemble Pro.exe, version: 7.0.0.17966, time stamp: 0x5cd577ab

    Faulting module name: Battery 4.dll, version: 4.1.6.27, time stamp: 0x59789ba1

    Exception code: 0xc0000005

    Fault offset: 0x0000000000d404bc

    Faulting process id: 0x1b8c

    Faulting application start time: 0x01d50a18c78a05bb

    Faulting application path: C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe

    Faulting module path: C:\Program Files\Native Instruments\VSTPlugins 64 bit\Battery 4.dll

    Report Id: 37fa845e-760c-11e9-bc93-a0369f509c1e

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-05-14T05:50:47.000000000Z" />

    <EventRecordID>41777</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Owner-PC140969</Computer>

    <Security />

    </System>

    <EventData>

    <Data>Vienna Ensemble Pro.exe</Data>

    <Data>7.0.0.17966</Data>

    <Data>5cd577ab</Data>

    <Data>Battery 4.dll</Data>

    <Data>4.1.6.27</Data>

    <Data>59789ba1</Data>

    <Data>c0000005</Data>

    <Data>0000000000d404bc</Data>

    <Data>1b8c</Data>

    <Data>01d50a18c78a05bb</Data>

    <Data>C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe</Data>

    <Data>C:\Program Files\Native Instruments\VSTPlugins 64 bit\Battery 4.dll</Data>

    <Data>37fa845e-760c-11e9-bc93-a0369f509c1e</Data>

    </EventData>

    </Event>

    event_crashReport-5132019.txt-1696338389378-pkxfy.txt

  • Hi iBeatz, 

    It is a bit of a mystery, NI plug-ins work on most systems with VE Pro 7, and we're doing our best to find out what is the cause of those troubles for a few unlucky users. 

    Stay tuned for an update that will hopefully be available soon, we're sorry about the inconvenience.

    Best,
    Paul


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @iBeatz said:

    Hello,

     All of NI's instruments crash after installing VSL pro 7; they won't open in standalone mode either. I can only attribute this problem to the new install since I've been running all previous versions for years without any problems. 

    Here's the crash log for Battery 4 but again to be clear none of NI's VST's are working (kontakt 6, Absynth, FM8, Massive, Reaktor 6) : 

    Log Name:      Application

    Source:        Application Error

    Date:          5/13/2019 10:50:47 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      Owner-PC140969

    Description:

    Faulting application name: Vienna Ensemble Pro.exe, version: 7.0.0.17966, time stamp: 0x5cd577ab

    Faulting module name: Battery 4.dll, version: 4.1.6.27, time stamp: 0x59789ba1

    Exception code: 0xc0000005

    Fault offset: 0x0000000000d404bc

    Faulting process id: 0x1b8c

    Faulting application start time: 0x01d50a18c78a05bb

    Faulting application path: C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe

    Faulting module path: C:\Program Files\Native Instruments\VSTPlugins 64 bit\Battery 4.dll

    Report Id: 37fa845e-760c-11e9-bc93-a0369f509c1e

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Application Error" />

        <EventID Qualifiers="0">1000</EventID>

        <Level>2</Level>

        <Task>100</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2019-05-14T05:50:47.000000000Z" />

        <EventRecordID>41777</EventRecordID>

        <Channel>Application</Channel>

        <Computer>Owner-PC140969</Computer>

        <Security />

      </System>

      <EventData>

        <Data>Vienna Ensemble Pro.exe</Data>

        <Data>7.0.0.17966</Data>

        <Data>5cd577ab</Data>

        <Data>Battery 4.dll</Data>

        <Data>4.1.6.27</Data>

        <Data>59789ba1</Data>

        <Data>c0000005</Data>

        <Data>0000000000d404bc</Data>

        <Data>1b8c</Data>

        <Data>01d50a18c78a05bb</Data>

        <Data>C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe</Data>

        <Data>C:\Program Files\Native Instruments\VSTPlugins 64 bit\Battery 4.dll</Data>

        <Data>37fa845e-760c-11e9-bc93-a0369f509c1e</Data>

      </EventData>

    </Event>

     

    Hi, do they crash even with VEP7 not running?

    Cause I'm not having crash but it seems that something went wrong after I installed VEP7, I've some strange issues loading some libraries in Kontakt inside Reaper.

    I also have some other problems that VSL already knows and they are working on it as Paul said.


  • Hi,

    Yes, after installing VEPro 7; All of NI's VST's suddenly stopped working even in standalone mode without VEpro 7 running. It's as if something was over-written or corrupted during the upgrade to VEpro 7. I'm still awating an update from Paul as he mentioned but in the meantime -- I'm trying different test and methods to get things up and running again. I'll be sure post my progress if any. 


  • last edited
    last edited

    @iBeatz said:

    Hi,

    Yes, after installing VEPro 7; All of NI's VST's suddenly stopped working even in standalone mode without VEpro 7 running. It's as if something was over-written or corrupted during the upgrade to VEpro 7. I'm still awating an update from Paul as he mentioned but in the meantime -- I'm trying different test and methods to get things up and running again. I'll be sure post my progress if any. 

     

    This is interesting! So the strange behavior I noticed in my Kontakt could be really VEP related. I noticed a general slow down of my libraries loading time and the UI hangs on some of them.

    But this only happens in Reaper, not in standalone mode. Like something has broke Reaper, I don't know how it could be possible but maybe VEP is the key.

    Did you try to uninstall it?


  • last edited
    last edited

    @DANIELE-ES said:

    This is interesting! So the strange behavior I noticed in my Kontakt could be really VEP related. I noticed a general slow down of my libraries loading time and the UI hangs on some of them.

    But this only happens in Reaper, not in standalone mode. Like something has broke Reaper, I don't know how it could be possible but maybe VEP is the key.

    Did you try to uninstall it?

    Yes, I've uninstalled everything (Kontakt 6, FM8, Absynth, Battery 4) and reinstalled about 10 times with the same behaviour. I've also uninstalled VEPro 7 completely to test without it in the OS but I still have the same problem. It's the most strange update I've ever encountered and nothing seems to work. I'm running out of options in hopes that VSL's team can come up with a solution. 

    Note: I've attached a photo of the screen showing "Absynth" not opening. 


  • last edited
    last edited

    @DANIELE-ES said:

    This is interesting! So the strange behavior I noticed in my Kontakt could be really VEP related. I noticed a general slow down of my libraries loading time and the UI hangs on some of them.

    But this only happens in Reaper, not in standalone mode. Like something has broke Reaper, I don't know how it could be possible but maybe VEP is the key.

    Did you try to uninstall it?

    Yes, I've uninstalled everything (Kontakt 6, FM8, Absynth, Battery 4) and reinstalled about 10 times with the same behaviour. I've also uninstalled VEPro 7 completely to test without it in the OS but I still have the same problem. It's the most strange update I've ever encountered and nothing seems to work. I'm running out of options in hopes that VSL's team can come up with a solution. 

    Note: I've attached a photo of the screen showing "Absynth" not opening. 

     

    Are the other no NI-VSTs you have working fine?

    Maybe something in the registry written by VEP. I'm really out of solutions and explanations...

    I hope too that they find a "cure" as soon as possible.


  • last edited
    last edited

    @DANIELE-ES said:

    This is interesting! So the strange behavior I noticed in my Kontakt could be really VEP related. I noticed a general slow down of my libraries loading time and the UI hangs on some of them.

    But this only happens in Reaper, not in standalone mode. Like something has broke Reaper, I don't know how it could be possible but maybe VEP is the key.

    Did you try to uninstall it?

    Yes, I've uninstalled everything (Kontakt 6, FM8, Absynth, Battery 4) and reinstalled about 10 times with the same behaviour. I've also uninstalled VEPro 7 completely to test without it in the OS but I still have the same problem. It's the most strange update I've ever encountered and nothing seems to work. I'm running out of options in hopes that VSL's team can come up with a solution. 

    Note: I've attached a photo of the screen showing "Absynth" not opening. 

     

    Are the other no NI-VSTs you have working fine?

    Maybe something in the registry written by VEP. I'm really out of solutions and explanations...

    I hope too that they find a "cure" as soon as possible.

     

    Yes, all other VST's are working fine. It's only the NI's VST's crashing. Finger's crossed that this gets fixed! 


  • Hello Paul,

    Below is an excerpt from a "Dependency Walker" report of Kontakt crashing behaviour. I've sent the full report to you via email. Hope it helps your team determine the cause for all of the NI VST's failing to validate in VEpro 7 and crashing when opening in standalone mode. Thank you!

    Best,

    Jorge

    Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.

    Error: Modules with different CPU types were found.

    Warning: At least one delay-load dependency module was not found.

    Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.


  • Hi iBeatz, 

    Thanks, hope we'll get there soon. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @Paul said:

    Hi iBeatz, 

    Thanks, hope we'll get there soon. 

    Best, 
    Paul

    Thank you Paul, I know you and your team are working hard on this. 

    As a side note; I've upgraded to Windows 10 pro but like before. Every VST app works great except

    for all Native Instrument VST's which don't open / launch in standalone mode and crash within VEpro 6 & 7.