Vienna Symphonic Library Forum
Forum Statistics

181,995 users have contributed to 42,199 threads and 254,646 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEPro 5.1.12010 - Unhandled exception error? An unhandled exception was caught! A crash dump fi...

  • VEPro 5.1.12010 - Unhandled exception error? An unhandled exception was caught! A crash dump fi...

    O
    O

    ever since upgrading to version VEPro 5.1.12010 last week, I'm getting crashes regularly with the following error on my PC slave. Not sure why this is happening all of a sudden...
  • T
    T
    I too am getting the same consistant crashes on the PC slave with this update. Looks like I will be reverting all machines back to the last release.
  • PaulP
    VSL Team
    PaulP

    Hi, 

    Please send the crash-dumps to , with a reference to this thread. We´ll take a look. 

    Best, 

    Paul

    Paul Kopf Product Manager VSL
  • C
    C

    I've seen that and three or four other type of crashes since this update. Of course there might be other things in the sandbox not getting along, but reverting to the previous version has meant these crashes don't happen.
  • T
    T
    I am primarily a mac user. How do I provide you the crash dump you want via windows? Where do I find it?
  • G
    G
    last edited
    last edited

    @thedr said:

    I am primarily a mac user. How do I provide you the crash dump you want via windows? Where do I find it?

    Crash dumps are C:\Users\YOURUSERNAME\AppData\Roaming\VSL\Vienna Ensemble Pro\crashdumps\app

    I'm also having these crashes, and unfortunately, the previous version also has the same crashes for me. Just emailed support. VEP is for the time being unusable. 

    It crashes when the orchestration gets thicker - when many instruments are playing back simultaneously.
  • K
    K
    last edited
    last edited

    @thedr said:

    I too am getting the same consistant crashes on the PC slave with this update. Looks like I will be reverting all machines back to the last release.

    Has reverting to the previous version helped for you?
  • J
    J

    Any news on this problem? I'm having it myself, mostly when deleting unpreserved instances.
  • G
    G
    last edited
    last edited

    @jamiesalisbury said:

    Any news on this problem? I'm having it myself, mostly when deleting unpreserved instances.

    Had to revert to my old way of sequencing things since I was on a tight deadline and haven't done too much additional testing with VEP yet. 

    The problem seems to be with the event input plug-in and the play engine. Word I got from VSL was the problem is with Play. Word I got from Eastwest was wait for Play 4.

    However, you can try using multiple VEP instances instead of the event input plug-in with a single large VEP instance. You'll be limited to 16 instruments per instance, but it seems to be stable for other users. I'm planning sequencing some things this week using more VEP instances and not bothering with the event plug-in. 
  • J
    J

    Thanks for the response. Surprise surprise, it's PLAY! Sigh....

    I'm not using the event input plug-in though - in fact I'm not even sure what it is.

    I'm using several instances, mostly PLAY, but some Kontakt etc. and 16 instruments in each. 
  • G
    G

    Not encouraging to say the least. Is it crashing only when the orchestration gets thick? 
  • J
    J

    It's when I've loaded up a new project, and then delete some instances still up from the last project. 

    Probably should do it the other way around (delete, then load new project), but I don't always remember. 
  • G
    G

    That's a little different than the crashes I was encountering - mine were during playback and only when most instruments were playing simultaneously. It would run without problems when only a few instruments were playing. 
  • J
    J

    Well I see that PLAY 4 is around the corner (whatever that actually means) so I'll just wait and see what happens there I guess.
  • F
    F

    I'm afraid I've been struggling with similar constant crashes over the past couple of months or so. Can't seem to pinpoint exactly what leads to the crashes, but my my system is almost unusable at this point. I've got the latest versions of everything, but was experiencing these same failures before the recent upgrades (was hoping they would fix things). Had a two day run recently where things were stable (which felt like an amazing vacation), but that came to a grinding halt. With deadlines looming I am at wits end. Slave PC running VEPRO, using a combination of Kontakt and Play.

    I was unable to find the crash dumps as per the instructions above, but here's the windows crash report. Seems to be pointing at Play just like what others here mention.

    Problem signature:
      Problem Event Name:    BEX64
      Application Name:    Vienna Ensemble Pro x64.exe
      Application Version:    5.1.0.12337
      Application Timestamp:    51c88c82
      Fault Module Name:    play_VST_x64.dll
      Fault Module Version:    3.0.47.0
      Fault Module Timestamp:    516efbe7
      Exception Offset:    00000000001d796f
      Exception Code:    c000000d
      Exception Data:    0000000000000000
      OS Version:    6.1.7600.2.0.0.256.48
      Locale ID:    1033
      Additional Information 1:    c89c
      Additional Information 2:    c89c36c6beff87016eb6b2d31c344df2
      Additional Information 3:    ee53
      Additional Information 4:    ee530dd63ecda01d73831e271040ded3

    Attempting to rebuild templates using multiple instances of VEPro (versus one large one as I am currently) seems like a huge endeavor when some people are reporting questionable results even in that capacity. Anyone find a fix for this yet? Tech support, you've been great before (Marnix was working with me using Teamviewer in the past). Any possibility of snooping around my system again? Or is this something completely out of your hands given it may be an East/West issue? Thanks in advance.
  • P
    P
    Hi, I have encountered this problem using VEP in combination with Sibelius. I have noticed the problem goes away when you start your sequencer first, then open your VEP server and then connect the plug-in to the server. Not a permanent solution but at least it might help... Let's hope Play 4 will be here shortly Sincerely yours, Pieter
  • G
    G

    Play 4 has been out for a while and I haven't run into this problem for a few months. I'm happy to say everything has been pretty stable with VEP lately. 
  • B
    B

    Hi,

    I have encountered this problem in PLAY 4.

    My instance is large, and made up entirely of EastWest Samples.

    I solved the problem by opening a new instance, adding a play plugin, opening an instrument and adjusting a few settings inside of PLAY.

    First of all I unticked CPU load limiter.

    Made sure 'Stream from Disk' was ticked in the 'main menu' part (make sure you load an instrument to access this setting).

    In settings, lower the 'Maximum Voices' setting.

    Delete the instance before you try to open your main template.

    Before you open your big template, go to the VEP preferences, under Server -> Instances ensure an appropriate no. of threads is set under multiprocessing. If you are doing this on your Slave, and you want to run everything inside of one instance, just set it to the highest no. of threads. also make sure the midi ports are set to more than the no. you're going to use.

    Opening your Big Template should hopefully now work. I open my templates before opening my sequencer.

    Hope this Helps,

    Blake Bennett