Vienna Symphonic Library Forum
Forum Statistics

196,700 users have contributed to 43,030 threads and 258,429 posts.

In the past 24 hours, we have 6 new thread(s), 10 new post(s) and 91 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. [SOLVED] Significant CPU Load Issue with VEP 6 and Cubase on Mac OS

  • [SOLVED] Significant CPU Load Issue with VEP 6 and Cubase on Mac OS

    J
    J

    Having performance issues using Cubase on Mac OS X 10.10.5 or MacOS Sierra and Cubase Pro 8.5 or Cubase Pro 9. Tested with all combinations, which result in the same issue with VEP 6. The CPU load goes through the roof with version 6.x, which did not happen with version 5.x.

    I have a project that connects to three slave computers using VEP. Prior to updating to VEP 6 there were no issues. Using VEP 6 is unsuable at the moment due to the CPU load issue.

    Still tracking down the source, but at this point it solidly points to VEP 6 as being the culprit.

    Anyone experiencing similar issues? Anyone found a remedy?
  • PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Didn´t I just read that somewhere? ðŸ˜Š

    Paul Kopf Head of Product Marketing, Social Media and Support
  • J
    J

    Quick update:

    The culprit seems to be a arbitrary resetting of the buffer settings for each VEP instance in Cubase. The template is rather large with 64 instances of VEP connecting to three workstations. I noticed that a significant number of instances were reset to using the "none" setting for the Latency Buffer in VEP. This resulted in the extremely high CPU load and makes perfect sense. After setting them back to using 2 buffers, the CPU load has moved back into the range it was before.

    Additionally, save time in Cubase increased to a tremendous amount. I noticed that "Decouple from Instance" had also been reset.

    So, all that to say that the issue has been resolved by checking that all instances are using the previous (2) buffers and that all instances are decoupled.

    Note: I assume at this point that this was caused by upgrading to Cubase Pro 9, which must have reset some of the VEP instances, and upgrading to VEP 6, which may have confused tracking down the issue at first.
  • J
    J

    Yes, you did, Paul. :-) My bad. I thought I had removed the comment on another thread. 

    Read my follow-up. The issue has been resolved.
  • PaulP
    VSL Team
    PaulP

    Hi Jurgen, 

    Thanks for the update, I will investigate the behaviour of Cubase 9 concerning the plug-in settings tomorrow!

    Best, 
    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • E
    E
    last edited
    last edited

    @Jurgen Beck said:

    Having performance issues using Cubase on Mac OS X 10.10.5 or MacOS Sierra and Cubase Pro 8.5 or Cubase Pro 9. Tested with all combinations, which result in the same issue with VEP 6. The CPU load goes through the roof with version 6.x, which did not happen with version 5.x.

    I have a project that connects to three slave computers using VEP. Prior to updating to VEP 6 there were no issues. Using VEP 6 is unsuable at the moment due to the CPU load issue.

    Still tracking down the source, but at this point it solidly points to VEP 6 as being the culprit.

    Anyone experiencing similar issues? Anyone found a remedy?

    I'm having similar issues here..

    Cubase pro 9, VEP 6 (both latest version) + OsX Sierra (latest version), on a Macpro 2013 6 core 64Gb RAM.

    VEP server on the same computer with 20 instances. VEP preferences set with 1 thread per instance.

    I'm having some random cpu spikes. (Asio Guard is inactive for all VSL plugins). Even if I'm  not playing anything, just in pause/idle. Those spikes make audio silence per 1-2 seconds, and they are random. The lower the ASIO buffer the more spikes appear even in stop mode. Sometimes, when I've connected to a particular vep instance I got 100% cpu like there were something wrong. After close everything and open again..sometimes it´s solved. So it seems that there is something hidden in the code. 

    Also, I've realized that when I quit VEP, I got a VEP crash.. I'm always using same VEP server template, and sometimes it happens and the others not.

    I could send the crash file to VSL if needed..