Vienna Symphonic Library Forum
Forum Statistics

181,922 users have contributed to 42,193 threads and 254,632 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Correct procedure for when VEPro crashes?

  • Correct procedure for when VEPro crashes?

    R
    R

    What is the correct procedure I should follow when VEPro crashes?

    2 machines: VEPro on its own machine, DP7.21 on my main machine (both Mac OS 10.5.8, both with the very latest VEPro and VI software).

    The 32 bit server (metaframe) on the VEPro machine crashes a lot (it has 10 instances inside) and I am never certain what the correct procedure should be to bring it all back online. If I simply reload the metaframe with the 10 instance template, it crashes again upon playback of lots of tracks. I guess I need to restart everything (both machines)? This happens a lot so I was wondering it there might be a quicker solution to restarting. Thanks.
  • R
    R

    By the way, a complete restart (shut down both machines, start VEPro machine, load up the 32 and 64 bit metaframes, start DP machine and fire up teh sequence again) results in the 32 bit instances being loaded TWICE. The set up was all de-coupled during the crash.

    If I disconnect all instances from teh 32 bit server, then reconnect to the correct instances, then start work again, it all crashes again soon after.

    Interestingly, I don't ever have a problem with teh 64bit server. It's always the 32bit one that crashes, or reloads twice etc.
  • K
    K

    Could you send crash reports of this to ? Thanks.
  • R
    R

    How do I obtain the crash reports? Please note due to deadlines I must proceed with finding a way through this and getting back to work. As such I have rolled back to the original version of VEP, and this I am hoping now to not experience further crashes when I do. (Today is the first day of going back to the original version so we'll see.)

    Thanks.
  • K
    K

    You can find all recent crash reports in the Console application. Without them it's hard to tell why you are getting these crashes.
  • R
    R

    Thanks, I see the reports. Do I cut and paste all the text for each report or is there a way to save it as a file and send it?

    Lots of these by the way:

    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000bc020008

    Crashed Thread:  0

    etc.

    Also btw, went back to the old originally released version of VEPro, no problems so far but will know more after a few saves and new file opens etc. At least I'm back to composing for today.