Vienna Symphonic Library Forum
Forum Statistics

202,920 users have contributed to 43,312 threads and 259,536 posts.

In the past 24 hours, we have 2 new thread(s), 11 new post(s) and 68 new user(s).

  • How to debug crashing server project

    last edited
    last edited

    I have a server project composed of 16 instances returning between 2 and 5 stereo output pairs each (for multiple mics), with VSL Synchron player, OT SINE (AU). The fully loaded server project is 160 GB on a 192 GB RAM M2 Ultra. If I load only the VSL Synchron player instances and connect from the DAW (same behaviour either with Logic or Cubase), it does not crash. When I load only the OT SINE instances, it does not crash. When I load both, it crashes. I have tried removing mics and reducing RAM, removing full libraries which reduced the RAM to 140 GB. I have tried switching from AU to VST3 for OT SINE (using AU at VSL's advice). At this point I really don't know what to do and I am starting to suspect that the issue may not be in the plugins (OT SINE) but in some channel configuration that has gone corrupted over time with copy and paste across projects. I can manually load channel by channel, and it will work just fine. But if I let VEPro load the full server project it will eventually crash. Maybe in 2 mins, maybe in 20 mins ... but it will crash 100% of the times.

    It's very frustrating as it's very hard to nearly impossible to debug. I am really close to giving up, and just wait till VSL releases an update, hoping this may fix whatever is happening (and this is assuming it's a VEP issue and not OT SINE's ...).

    How are folks here debugging these problems? Are there logs one can take a look at? I am on macOS Sequoia.


  • last edited
    last edited

    I assume that you already sent a crash log to VSL and they could not help.

    Just a question is VEP crashing when the instances of an already opened VEP project with all instances you need loaded connects to the DAW or when you first open e.g. Cubase with coupled instances included and then let it open VEP and create the required instances? This second way of working might create a fresh version of you VEP project eliminating all legacy issues. It works with simple single output instruments but I am not sure if it also works with multiple outputs per instrument.

    In most cases debugging VEP issues remains try and error. Especially if one is no expert in how different aspects of the whole combination of VEP, plugins and DAW influence memory usage. Based on what you write it does seem a memory overload maybe just on a specific area or core. According to some demos on Youtube surprisingly Cubase seems to be better in using all performance and efficiency cores than Apple’s own Logic.

    Some small observations I made. There seems to be a memory peak higher than the sum of all loaded instances when one or more instruments start playing especially for the first time in a VEP session even if all VEP instances seem to have been loaded and show activity after connecting That might be the point the crash occurs.

    Anther point is that instrument focus button in VEP. The circle with the cross. It makes the VEP view jump around from one instrument plugin to another based if it starts playing I think. I am not sure but if this might also give a small memory increase. I usually put it off.

    Another point to try, have you tried putting the OT and VSL instruments on different ports in VEP? The crash might occur if OT tries to use a memory area already used by a VSL instrument or vice versa. Maybe using different ports might avoid this.


  • @Mavros said:

    I assume that you already sent a crash log to VSL and they could not help.


    Just a question is VEP crashing when the instances of an already opened VEP project with all instances you need loaded connects to the DAW or when you first open e.g. Cubase with coupled instances included and then let it open VEP and create the required instances? This second way of working might create a fresh version of you VEP project eliminating all legacy issues. It works with simple single output instruments but I am not sure if it also works with multiple outputs per instrument.


    In most cases debugging VEP issues remains try and error. Especially if one is no expert in how different aspects of the whole combination of VEP, plugins and DAW influence memory usage. Based on what you write it does seem a memory overload maybe just on a specific area or core. According to some demos on Youtube surprisingly Cubase seems to be better in using all performance and efficiency cores than Apple’s own Logic.


    Some small observations I made. There seems to be a memory peak higher than the sum of all loaded instances when one or more instruments start playing especially for the first time in a VEP session even if all VEP instances seem to have been loaded and show activity after connecting That might be the point the crash occurs.


    Anther point is that instrument focus button in VEP. The circle with the cross. It makes the VEP view jump around from one instrument plugin to another based if it starts playing I think. I am not sure but if this might also give a small memory increase. I usually put it off.


    Another point to try, have you tried putting the OT and VSL instruments on different ports in VEP? The crash might occur if OT tries to use a memory area already used by a VSL instrument or vice versa. Maybe using different ports might avoid this.

    I have shared a few logs already, but no luck. I think because it's likely one of the plugins or channels. I have OT and VSL running on separate ports.

    I had MIDI activity focus, I have switched it off now and see how it goes.

    VEP crashes either when loading the server project by itself (80% of the times), when opening an empty session and loading a Cubase/Logic project (coupled) (100% of the times), and if I manage to get over that point when I start playing it crashes again (50% probability). So all in all, after 20 mins of loading samples I have like a 10% probability that it will actually play anything.

    I hope I am starting to narrow it down to one particular instance with OT SINE plugins, and the one with the biggest consumption of RAM. I don't know yet if it's the routing (sometimes I see that the aux outputs from channels having plugins get disconnected from the plugin channel itself) or if perhaps it's one of the SINE instances loading too many samples in RAM (I have all Ben Wallfisch Strings loading 6 mic positions in a single instance of 28 GB).


  • Yes It is most probably related to the Sine instances. I have a VEP project with 18 instruments with 7 and for some 8 microphones activated without issues but close to the max I think for an M1Max with 64 GB.

    I switched to MIR 3D now and can easily have 50 or more instruments and can replicate the SY Stage specialization in Dolby Atmos very well using only the SY Library close microphones.