Vienna Symphonic Library Forum
Forum Statistics

193,964 users have contributed to 42,904 threads and 257,885 posts.

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

  1. Home
  2. Software
  3. Vienna Ensemble Pro 7
  4. Vienna Ensemble 7.3 update DP 11.32 crashes

  • Vienna Ensemble 7.3 update DP 11.32 crashes

    B
    B

    I got Prompted to upgrade my Vienna Ensemble Pro in MOTU DP 11.32 yesterday. Not sure if it was E-Licencer or Ilock. But when it updated. I can no longer use ensemble pro in MOTU DP without DP crashing! Cant do my projects. I used Vienna assistant to update to new release too. Problem is really bad!

    If i add Instrument in DP "Ensemble" or "Ensemble 35 out, or Ensemble pro" it crashes DP every single time

    I tried clearing prefs in DP, and removing Vienna software and Removing DP but boy am I SOL i sent it in as a bug but no one has solved it yet. Below is the crash! Is it possible that the VST2 was switched back to E-licencer So DP crashes because it no longer has VST2 for Ilock?

    Here is the error! I really need my Vienna products to work. I am in a major project and deadline is Friday.

    Any help i would be so happy! In thread 26 below it says nahlem which my computer is not. Also notice the MAS and Vienna Ensemble ref invalid Segment! Should NEVER happen on VST init. Any thoughts?

    I run Catalina 10.15.7 , Mac Pro 128gb ram,

    Dp 11.32 and Current version of VSL according to Vienna Assistant.

    Kind Regards

    B

    Crashed Thread: 29 MAS Job Queue

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
    Exception Note: EXC_CORPSE_NOTIFY

    Termination Signal: Segmentation fault: 11
    Termination Reason: Namespace SIGNAL, Code 0xb
    Terminating Process: exc handler [21967]

    Thread 29 Crashed:: MAS Job Queue
    0 libsystem_platform.dylib 0x00007fff6f8848aa _platform_memmove$VARIANT$Nehalem + 138
    1 at.co.vsl.viennaensemble 0x000000041883f108 VENetThread::process(VFServer::ProcessData&) + 824
    2 at.co.vsl.viennaensemble 0x000000041884182d VEPlugin::process(float**, float**, int) + 1149
    3 at.co.vsl.viennaensemble 0x000000041884e683 AudioPluginFinal<VEPlugin>::process(float**, float**, int) + 515
    4 at.co.vsl.viennaensemble 0x000000041878dcdb VST2WrapperEffect::processReplacing(float**, float**, int) + 587
    5 com.MOTU.MAS.VSTSupport 0x000000016ab1465c MasVSTSupportProc::Process(MotuException*, float**, MasBufferInfo*, IMasEffectContext*) + 1428
    6 com.motu.MAS.framework 0x0000000103fe77c4 MasWriteStandardAutomatableSurroundSetting + 92324
    7 com.motu.MAS.framework 0x0000000103fb04f0 MAS83148 + 318816
    8 com.motu.MAS.framework 0x0000000103fb0354 MAS83148 + 318404
    9 com.motu.MAS.framework 0x0000000103fb0249 MAS83148 + 318137
    10 libsystem_pthread.dylib 0x00007fff6f890109 _pthread_start + 148
    11 libsystem_pthread.dylib 0x00007fff6f88bb8b thread_start + 15
  • R
    R

    I am seeing the same behavior as well if I add “Vienna Ensemble 32” out.
    m2 MacBook Pro / Sonoma
  • PaulP
    VSL Team
    PaulP

    Hi,

    Did the latest Sonoma update solve the situation?

    Paul Kopf Product Manager VSL
  • R
    R

    I have not updated yet …. Is it safe?