Vienna Symphonic Library Forum
Forum Statistics

182,209 users have contributed to 42,210 threads and 254,708 posts.

In the past 24 hours, we have 3 new thread(s), 28 new post(s) and 51 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Crazy high CPU load with VEP + Cubase

  • Crazy high CPU load with VEP + Cubase

    G
    G

    Working on a new system, and running into big problems on my main template.

    I'm experiencing very high CPU load when idling in VEP. The CPU monitor in VEP flickers around 70-90% in most of the loaded instances when nothing is occuring, and similarly in Activity Monitor, 300% + CPU usage from VEP. Naturally, pops clicks and dropouts on playback.

    Here are more details -

    SYSTEM SPECS (single machine, no slave)

    OS - Sierra
    Mac Pro (Mid 2010)
    3.46 GHz 6-Core Intel Xeon
    64GB 800 MHz DDR3
    SSD Startup disk, and samples streamed off SSD
    ATI Radeon HD 5770 1024 MB

    Cubase 9.5
    VEP 6
    Latest Kontakt
    UAD Apollo Quad Firewire

    • I run 3/4 instances within my main orchestral template (Winds, Perc, Strings, and optional Synths).
    • Exclusively Kontakt libraries (barring the synths)
    • Most instances using under 50 audio returns, except drums which are higher. I have preferences typically set to 300 Audio Outputs in VEP preferences, but I've experimented lowering this considerably and to not much effect.
    • No FX used in VEP server/mixer
    • 2 buffers. Cubase at 512.
    • Pre-load buffer size set to 60kb (once again, have experimented raising/lowering this but to not much avail)
    • All samples purged from outset
    • Maximum Voices optimised to each instrument

    Trying to think of what else to include, please let me know if there's anything else you'd need to know.

    I've had 2 separate engineers look at this remotely over Teamviewer and gone through the motions of various fixes, but nothing worked and both are stumped. Both also agreeing that with my specs and the size of my template I should be running this no problem.

    It should be noted that the CPU/Audio performance meter in Cubase runs within the optimal range you'd expect, which narrows down the problem to within VEP I believe.

    Once again to summarise - once VEP template is loaded and then connected to its corresponding Cubase template, the CPU meter in the bottom right shoots up to anywhere between 60-90% depending on the instance. During playback of even a small handful of MIDI parts, the GUI grinds to a halt (laggy playhead etc.) and audio pops, clicks and dropouts occur throughout. Activity Monitor shows VEP using anywhere between 200-300% CPU when idling, and shoots up to 400-500% or whatever during playback.

     

    Any and all feedback gladly welcomed at this stage - thanks in advance
  • prodamuP
    prodamuP

    Hi,
    I have a similar problem on Mac. In my case the CPU usage for VEP is normally around 90-100% when idling, but if I leave the template running overnight the VEP-CPU usage next day is at crazy 900-1000% when idling. If I shut down the template and restart it the VEP-CPU usage is back at 90-100%.

    I have started a support case about this (case 278666), but after sent requested Activity Monitor samples to Paul three weeks ago I haven't heard anything.

    Paul wrote:

    "We have been thinking in the past, that perhaps Kontakt scripts might run into some integer wrapping - since I believe they lack 64-bit integers to use for samplestamps. A signed integer can have the max value of 2,147,483,647 - or 48696 seconds at 44.1kHz - or 13.5 hours."

    but I do not use Kontakt in this template, only Vienna Instruments Pro and MIR Pro.

    I also run a VEP on a slave computer (Win10) with VIP, Synchron Player and Synchron Pianos, but there I do not have this problem, there is the problem instead that VEP crash quite often because of Synchon Player after playback from the DAW (but not when playing "live" from my MIDI keyboard).

    I hope Paul will give some feedback soon.
  • G
    G

    Hi mate,

    Thanks for this - that's interesting. I don't have the 'growing' CPU issue myself - it's high from the off. I use almost exclusively Kontakt within my template.

    Nobody I know seems to have experienced this issue. I'm gonna raise it officially with VSL and hope they don't pass the buck as a Kontakt/Cubase issue.