Vienna Symphonic Library Forum
Forum Statistics

202,795 users have contributed to 43,310 threads and 259,518 posts.

In the past 24 hours, we have 6 new thread(s), 29 new post(s) and 65 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. VE Pro 5.2.12785 on Mac OS, VERY crashy
  • W
    W

    I'm not sure the crashing is isolated to MAC OS either.  I'm running windows 7 and I'm getting crashes as well.  At first I thought it was with Finale but the same thing happens with Reaper. 

    Does VSL dump some log or is it whatever the OS dumps that support wants to see?
  • S
    S
    last edited
    last edited

    @Paul said:

    HI Sam,

    Please send the crash-log to

    @Sami: I´d repair permissions on the system drive and check if there is another eLicenser protected plug-in loaded in your VE PRO, which could cause this error. 

    Best,

    Paul

    I sent the crash-log to your support. For some reason MIR Pro has been giving me a hard time for a while now. It now and then fails to load and ingorms me that there is a problem with it's license.
  • R
    R
    Hello, PLEASE Help me!! I am using a mac OSX 10.6.8 I updated two programs PLAY 4 and VEPRO 5 to 5.2.12785 on saturday and now cubase 6 will not open it crashes before start up. It gets to ominfliter and crashes this is terrible. I was going through help advice with PLAY 4 tech today but cubase 6 still does not open. I am starting to think VEPRO might have caused some errors now. Something has gone wrong can anyone help me. It was working fine before any updates to any of the programs. Cubase 4 opens and works why does that work and not cubase 6. Who can help me fix this quickly.
  • R
    R
    Here is part of the log Process: Cubase 6 [1238] Path: /Applications/Cubase 6.app/Contents/MacOS/Cubase 6 Identifier: com.steinberg.cubase Version: 6.0.7.364 (6.0.7.364) Code Type: X86-64 (Native) Parent Process: launchd [143] Date/Time: 2013-10-01 15:08:44.930 +0100 OS Version: Mac OS X 10.6.8 (10K549) Report Version: 6 Interval Since Last Report: 45529 sec Crashes Since Last Report: 13 Per-App Interval Since Last Report: 388334 sec Per-App Crashes Since Last Report: 13 Anonymous UUID: 413C7087-D70A-479B-8B9C-39BB2C6507E3 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000124189d9f Crashed Thread: 0 Dispatch queue: com.apple.main-thread Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 ??? 0x0000000124189d9f 0 + 4900560287 1 dyld 0x00007fff5fc0c839 ImageLoader::link(ImageLoader::LinkContext const&, bool, bool, ImageLoader::RPathChain const&) + 201 2 dyld 0x00007fff5fc04d48 dyld::link(ImageLoader*, bool, ImageLoader::RPathChain const&) + 118 3 dyld 0x00007fff5fc08f68 dlopen + 490 4 libSystem.B.dylib 0x00007fff87a9be40 dlopen + 61 5 com.apple.CoreFoundation 0x00007fff8223eef7 _CFBundleDlfcnLoadBundle + 231 6 com.apple.CoreFoundation 0x00007fff8223de97 _CFBundleLoadExecutableAndReturnError + 1191 7 com.apple.CoreFoundation 0x00007fff822cb30e CFBundleLoadExecutableAndReturnError + 14 8 com.steinberg.cubase 0x00000001011e8e55 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 69941 9 com.steinberg.cubase 0x00000001011e93f0 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 71376 10 com.steinberg.cubase 0x0000000100402690 0x100000000 + 4204176 11 com.steinberg.cubase 0x00000001011d8e77 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 4439 12 com.steinberg.cubase 0x00000001011e86b7 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 67991 13 com.steinberg.cubase 0x00000001011e892e CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 68622 14 com.steinberg.cubase 0x00000001011e8a64 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 68932 15 com.steinberg.cubase 0x00000001007c68ab 0x100000000 + 8153259 16 com.steinberg.cubase 0x0000000100d149c0 0x100000000 + 13715904 17 com.steinberg.cubase 0x0000000101277b99 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 654969 18 com.steinberg.cubase 0x0000000100d16dbd 0x100000000 + 13725117 19 com.steinberg.cubase 0x000000010116b048 0x100000000 + 18264136 20 com.steinberg.cubase 0x00000001000d39c4 0x100000000 + 866756
  • S
    S
    last edited
    last edited

    @MDesigner said:

    I'm getting plenty of crashing when instances change (either deleting instances, or when the sequencer project changes and I tell VE Pro to load incoming data). I hope this is a known issue and it's being worked on! I can supply a crash log if needed.

    Also having a very crashy experience with VEP5...  AND i just updated to the latest version and my AAX64 VEP plugin is gone!  (and this was after touble shooting why it would not open my latest mframe).  How do I get it back?  reinstalling it is not adding it to the avid pro tools plugin folder and my sessions are not finding it.  Man this program used to be so stable....more stable than any of my other software.    What happened?  is it a mountain lion issue?  
  • S
    S
    last edited
    last edited

    @studioj said:

    How do I get it back?  reinstalling it is not adding it to the avid pro tools plugin folder and my sessions are not finding it.

    Ok third reinstall seems to have added the plugin back to the avid aax folder.  Weird!   PLEASE vsl, make stability a top priority on MAC....  It is currently my most unstable piece of software.  But so Vital!  I have do a little prayer everytime I do anything in an instance 😊

    Mac OS 10.8.4

    Mac Pro 12 core 3.33

    64 gigs RAM

    RME interface
  • S
    S

    update...  it seems that the latest installer adds it but crashes on open and the one previous REMOVES it but will open and let me open my mframes.  hoping i can find someone to email me the file and it will work...   is the installer broken then?  I'm watching the folder as it installs and it literally just erases the AAX plugin and does not put anything back in its place.  PT users beware!
  • PaulP
    VSL Team
    PaulP

    UPDATE: 

    VE PRO 5.2.12794 has just been uploaded, the crashes should be fixed. 

    Best,

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • S
    S

    it works!  THANK YOU THANK YOU
  • M
    M

    Nope, new version still crashes every time I select an instance from the list and click "delete" (from within the VE Pro Server window). But if I uncheck the "preserve" checkbox, it removes the instance without crashing. I'll do that for now as a workaround. I'm in touch with support.
  • S
    S
    last edited
    last edited

    @MDesigner said:

    Nope, new version still crashes every time I select an instance from the list and click "delete" (from within the VE Pro Server window). But if I uncheck the "preserve" checkbox, it removes the instance without crashing. I'll do that for now as a workaround. I'm in touch with support.

    Bummer, hopefully they get that sorted soon.  i had a few crashes today also...  they all seem GUI related... clicking around doing something in the interface seems to trigger the crash.  BUT it was a huge step up from NOT opening my mframes at ALL.  So thanks VSL for getting the update out quickly.  
  • M
    M

    I haven't heard back from support. This thing is still very unstable when updating VE Pro with sequencer project changes. Paul, do you know anything about bugs still existing in this latest version?
  • A
    A
    still crashes can i downgrade to ve pro 4 ? this is rediculous :(
  • PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hi arturek,

    I have already answered your mail to .

    We´d be happy to receive crash reports and more details about your system. I couldn´t find any previous reports from you, so maybe that´s something our developers can fix quickly.

    And as a user of VE PRO 4 who upgraded to VE PRO 5, you can install VE PRO 4 anytime.

    Only catch: You cannot open VE PRO 5 projects in VE PRO 4 (it only works the other way around).

    Best,

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support