Vienna Symphonic Library Forum
Forum Statistics

200,465 users have contributed to 43,198 threads and 259,087 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Ensemble Pro Instance Limit? Logic is crashing after about 20

  • Ensemble Pro Instance Limit? Logic is crashing after about 20

    D
    D

    I am using the Ensemble Pro with Logic 9 and it has been working pretty well, but now I am running into a problem where Logic crashes when I try to open the plug-in window and connect to an instance.  It seems to be related to the number of instances available to connect to, and I'm making out around 20.  Has anyone else run into this?  Is there a solution?

    The crash only happens when I open the plug in to browse the list of available instances.  If I just let a session load up the instances it's fine... but the plug-in window doesn't like to see more than 20 choices.

    The reason I'm using so many instances is because I've found that it much more straightforward to just load one plug-in or VI per instance instead of 16. This is makes control from within the session and when switching between sessions is easier...  ie volume faders control only the volume of that instrument, not every instrument on the instance, and you don't have to write plug in automation for every volume, not to mention reverbs and other controls.

    Even if I loaded up the Instances there would still be alot of instances showing up because I'm on a local network with several Ensemble Pro systems.

    Is this a Logic bug or a limitation of the Ensemble Pro?

    Is there another way to set up the session to make controls of the use of a Logic Multi Instrument more practical?

    Any help would be greatly appreciated, because the best I've come up with so far is just not to load more than 20... which is frustrating, because the plug-in/server idea can be so useful when switching between a bunch of similar sessions.
  • D
    D

    An update...

    The same thing happens in Digital Performer so it seems to be a bug/limitation with the VSL plug-in.  I've downloaded the most recent version and it's the same thing as the previous build.  It seems like it's really just a problem with the browser... which would seem like a relatively easy fix... but what do I know?

    if you're interested here are the condensed version of the crash logs from both Logic and DP:

    Thanks!

    Logic Crash Log

    Exception Type:  EXC_BAD_ACCESS (SIGABRT)

    Exception Codes: 0x000000000000000d, 0x0000000000000000

    Crashed Thread:  0  Dispatch queue: com.apple.main-thread

    Application Specific Information:

    abort() called

    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread

    0   libSystem.B.dylib             0x00007fff81a943d6 __kill + 10

    1   libSystem.B.dylib             0x00007fff81b34913 __abort + 103

    2   libSystem.B.dylib             0x00007fff81b34981 abort_report_np + 0

    3   com.apple.logic.pro           0x000000010039a486 std::_Rb_tree<short, std::pair<short const, CGRect>, std::_Select1st<std::pair<short const, CGRect> >, std::less<short>, std::allocator<std::pair<short const, CGRect> > >::_M_erase(std::_Rb_tree_node<std::pair<short const, CGRect> >*) + 97718

    4   libSystem.B.dylib             0x00007fff81aa635a _sigtramp + 26

    5   ???                           0x532d414c20372e31 0 + 5993518474313805361

    Digital Performer Crash Log

    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes: KERN_INVALID_ADDRESS at 0x00000000422d6ff5

    Crashed Thread:  0  Dispatch queue: com.apple.main-thread

    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread

    0   ...audiounit.viennaensemblepro 0x3e180613 GetPluginFactory + 135555

    1   ...audiounit.viennaensemblepro 0x3e16030e GetPluginFactory + 3710

    2   ???                           0x64757453 0 + 1685419091
  • K
    K

    This has been reported before, but we were never able to reproduce it on our side, so it might be related to your specific setup. Could you e-mail any information concerned to ? This way we can handle it as a proper support case. Thanks.