Vienna Symphonic Library Forum
Forum Statistics

180,788 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 68 new user(s).

  • SOLVED VEP 7 + Cubase FX Rack Trouble

    Hey there,

    i have a problem, getting Audio piped through my VEP 7 Pro Slave machine and hope, that somebody has any idea.

    My setup should be like:

    - having 8 EFX Channels for reverbs, delays and rooms, etc.

    - These will have individual Send faders and Returns in cubase

    So far so good. So i started to create a new Instrument with 8 Stereo outs and liked it to an instance called EFX64.

    Now i add 8 EFX Channels to cubase, each with a VSL Stereo In and link em to EFX64 with the correct input numbers.

    Worked good once, the other day it stoped working. Now if i have more than 4 EFX Inputs linked to VEP 7, no audio is processed at all. Audio isnt even showing in the VEP mixer. If i just use 4 Input instances and delete the other 4 it works.
    What am i doing wrong?

    My Setup is: Cubase 10.5 Host (core i7 4770) 16 gb Ram. Asio guard turned off as well as Asio guard on all Vienna plugins

    Slave machine is a xeon e5- 8 core 16 threads. I also switched between the thread usage in VEP7, no change. Turned off and on the hyperthreading etc... No change.

     

    I am talking in 96khz to my audio interface. Might this be  a problem?

    One thing i have noticed. If i start/stop the DAW's playback, i sometimes get audio back from the effects.

     

    Drives me nuts.

     

    Thanks in advance,


    Geronimo


  • Hi Geronimo,

    please double-check that you have disabled ASIO Guard in Cubase for all VSL plugins:

    https://www.vsl.info/manuals/vep7/vep-server#asio-guard

    Best, Ben


    Ben@VSL | IT & Product Specialist
  • Thanks Ben. Especially for taking your time scrolling through the manual, i already found that page.

    As i mentioned i deactivated the Asio guard especially for the VSL Plugins.

    It simply isn't imply isn't possible (so the support says), at least not in a reliable way.

    I am on to find out why the audio send function via vst instrumet is possible at such a high amount of channels, if this feature actually isn't supported.

    PLEASE VSL guys... Force to feature this well! This would be a killer feature because some Reverbs, delays, pretty much all parallel plugis that have pre-delay functionality have high amount of cpu load. It would be great to have them on a slave machine. I produce rock / metal with symphonic elements and specially rooms and delays take alot of cpu on the host machine.

    Ben, have a great day!

    Geronimo


  • Do we still need to disable ASIO Guard for VSL Plugins?

    I thought that was addressed a while ago...


  • Unfortunately the ASIO Guard is doing it's own latency compensation and is making trouble with VSL's internal ones. But if you ask me, you want to have the asio guard turned off, at least for the VSL plugins.

    In my case some new insights came up. I am pretty sure, that some people have exactly the same problem.

    The audio lag was not only coming through audio loopbacks. In my case, even normal midi to vsl -> audio back got stuck every 20 to 40 seconds, causing high drop outs.

    After messing around with my host, becaus i thought the problem was there, i focused on my slave machine. Then i installed all the tools on a very different machine with a different chipset and the problem was gone. Even my FX chain works perfect now.

    I bought two exactly same computers (used but powerful) and spent 1500 Euros into it. I dont know if this is just a bad combination of Hardware or both computers are junk.

    No good:

    EVGA X79 Dark and X79 SLI - Xeon E5-2687W - 32 Gig - ASUS GTX780 WIN 10 1909 or Win 7 (full blown) - Samsung Pro SSD 1TB

    The Xeon is not on the CPU list of the mainboards (Dark and SLI) so i got myself an I7-3820 with exactly the same issue. I also tried various different Broadcom and Intel Network adapters, Bios versions, Bios settings and even another ASUS Mainboard with X79 Chipset. Always troublish... Sometimes more, sometimes less. I spent at least 3 to 4 days of installing windows and tools because i know about bad config after hardware changes.

    It looks like, that either the sandy bridge-e is haveing its issue with VSL or maybe the Intel X79 Chipset which would be a bummer. Even if the EVGA Mainboards are still quite expensive, they are pretty reliable and powerful machines. I am sad, that i cannot use the because i got stuck on one machine with less power.

     

    Works great but could have more power:

    ASUS Z87 - CORE I7-4770 - 32 Gig - ASUS GTX780 - WIN 10 1909 - Samsung Pro SSD 1TB

    Hope this helps somebody dealing with his dropouts.

     

    Geronimo


  • I am also unable to send more than 4 audio inputs (44.1K) from cubase to a single instance of VEP reliably. VEP stops processing the audio channels with any more than that. I have an intel i9-9900k connected to a Ryzen 3950x over 1gig LAN so I would expect this to work but it seems like it is a broken feature?

    Id like to be able to have multiple instances in VEP hosting VST instruments on the slave machine with another hosting VST send effects that can be routed back from cubase, But right now this doesnt seem to be possible (at least not using a single instance of VEP for more than 4 send effects - it could probably work if I split up the effects over several instances, but this becomes messy to manage.

    Stuart