Vienna Symphonic Library Forum
Forum Statistics

180,797 users have contributed to 42,141 threads and 254,364 posts.

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

  • [SOLVED] VEP + many EW Play(ers) = VEP not responding (Searching for the bottleneck)

    Hey gals & guys,

    this is not a question, more a problem I tried to solve for weeks now & I solved it finally. I thought, some of you might suffer the same pain, so I want to share some experience I gathered out of it.

    The Problem was, that my Slave-PC (Win10) got more and more laggy the more EW Players I opened up in VEP 7 until it completly got stuck (while the CPU- and RAM-usage is totally fine).

    My framework was the following:

    • Master PC (Win10)
      • Sequencer
      • Several Effect-Plugins
      • Graphics Card (PCI-E Slot)
    • Slave PC (Win10)
      • Five less complex libraries
      • VI Symphonic Cube (more complex)
      • Onboard Graphics Card

    Now I started to include EW Stormdrum 3, a more complex library (different microphone positions etc.) into my template. And the more Play Engines i opened the more my Slave-PC was getting laggy until I had to wait for about 2 minutes from click to result.

    First I created one channel per instrument and it got stuck after a while, so I thought using the multi output (Play Engine) might solve the problem (less players to open). So I insert a Play Engine channel, stacked up 8 instruments and routed them to AUX-channels (in VEP). But at about the same amount of instruments i put into the template, my Slave-PC froze. I tried several routing chains and stuff. But I realized, two things:

    • Although my template was frozen, in my sequencer the sounds came up with almost no latency, as it should be, when I played my MIDI keyboard.
    • If I open other windows/programs on my slave machine, they work flawlessly. To cut it short:

    Opening the BIOS (on the slave machine) & assigning the onboard graphics some fixed amount of RAM did the trick. The standard preference was "AUTO", which is almost always a bad state for any preference, if you ask me. ;-)

    Hopefully it helped in some way.

    Stay healthy & creative!


  • Hey again,

    after a few months of research & testing it seems to be a windows problem handling big files. My template (about 500MB) had been rewritten many times while setting it up. It appears that this caused the "lags". After rebuild my template by saving the libraries seperate & merch them together again solved my problem. Now it's smooth again as it should be. Hope that helps.

    Greetings

    Chris


  • Hi Chris, 

    Thanks for the update, that's great to hear!

    Best, 
    Paul


    Paul Kopf Product Manager VSL