Vienna Symphonic Library Forum
Forum Statistics

193,849 users have contributed to 42,898 threads and 257,858 posts.

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

  • Asio Guard and VE Pro 7

    Does Asio Guard in Cubase 13 work with VE Pro 7? If I understood correctly, it didn't work when VE Pro didn't support vst3. Now that it does, can I activate Asio Guard for Ve Pro 7?


  • You should still disable ASIO Guard for VEP7 plugins, but you don't have to disable it globaly.

    In Cubase' plugin manager there is an option to disable ASIO Guard just for specific plugins.


    Ben@VSL | IT & Product Specialist
  • Thank you for the info Ben. Any chance that it will be compatible in the future? Asio Guard saves resources quite effectively in Cubase. It would be a boost to have it for VE Pro.


  • last edited
    last edited

    We have it on wish-list, but it will most probably not improve performance since VEP already adds an additional buffer.


    Ben@VSL | IT & Product Specialist
  • Hello, I'm using VEP7 Pro and Nuendo 13. I've built a template with over 1000 MIDI tracks. 68 racks are loaded, most of them enabled, depending on the required plugins on the VEP server.

    If ASIO Guard is disabled for VEP7:

    and if enabled:

    Finally if ASIO Guard is enabled my system runs better, just because Nuendo (or Cubase) uses more CPU power respectively performs better by using more CPU threads.

    Vice versa I cannot say, that it runs worse - everybody should try both ways.


  • Same for me better performance when ASIO Guard enable


  • Although it is not official advice, I find ASIO Guard is best ON and set to LOW for VE Pro. Any higher setting and there's big problems when switching tracks, if set to off performance suffers.


  • @PeterH said:

    Hello, I'm using VEP7 Pro and Nuendo 13. I've built a template with over 1000 MIDI tracks. 68 racks are loaded, most of them enabled, depending on the required plugins on the VEP server.


    If ASIO Guard is disabled for VEP7:



    and if enabled:



    Finally if ASIO Guard is enabled my system runs better, just because Nuendo (or Cubase) uses more CPU power respectively performs better by using more CPU threads.


    Vice versa I cannot say, that it runs worse - everybody should try both ways.

    I had a similar experience with the newly released Cubase 14 and VEPRO 7. I've always disabled ASIO Guard for VEPRO in Cubase, but I just wanted to test how it works when enabled. I had my buffer size set to 512, and both real time and peak dropped significantly. After playing my full orchestral track for a while, they dropped even more, and I could decrease my buffer size to 128!