Vienna Symphonic Library Forum
Forum Statistics

182,865 users have contributed to 42,261 threads and 254,942 posts.

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

  • CUBASE Pro 9.5 with VEP 6

    Just thought I would share that I have no issues (so far) with VEP after updating to Cubase Pro 9.5. There was a newer version of eLicenser: 6.10.6.2219. Not sure how old that is, but I installed it before upgrading Cubase to 9.5.  Of course...YMMV


  • I just loaded and played one of my last VE-Projects with Cubase 9.5 with no problem. While this does not mean to be an indepth testing. at least on the first glance there seem to be no problem with Cubase 9.5. here to.


  • Thanks to all for sharing these reports - do you notice any performance inprovement in Cubase 9.5 (versus 9.0), or any difference in sound engine quality/characteristics? Any comments regarding other updated features that may have an impact in your VSL projects?  


  • Cubase 9.5 seems to be just a little bit faster (in perticular the GUI). 
    The sound-engine is now available in 32-bit and 64-bit. Have not tested the 64-bit engine...
    Cubase automation now does have beziere-curves. Sadly not in the MIDI-editor. Hopefully they will integrate that in a future update. This would be great for programming VSL.
    There are also a lot of little improvements here and there (GUI, metronom, ...).

    IMO: If you are only working with audio I wouldn't recommend to buy this update. But if you are working with MIDI it is definitly worth the 60€.


    Ben@VSL | IT & Product Specialist
  • I was able to open up a large session done in Cubase 9.2 and VEP6 on a Windows 7 machine and multiple slave machines. The problem is that I'm having ASIO spikes even when the song is not playing. Same settings as my 9.2 install. If I turn off ASIO Guard the spikes go away in Cubase 9.5. May be a Windows issue, but I remember having a similar issue on an OSX 12 core machine after an update. I'm mentioning this here since all of my Cubase scoring sessions use VEP6. When I create a Cubase session without VEP instances, all is well. I don't think that this is a VEP issue since I can open large sessions in Pro Tools 12 HD with VEP and no problem. Until this gets worked out, I'm just using Cubase 9.02. Any suggestions?


  • I actually ran in to a problem running Cubase 9.5 on my MacBookPro running Sierra v10.12.6

    I can connect my VEP instance, and my Audio Inputs pair just fine, but as soon as I try to select the input, I get a "No Inputs Found" message. I like using Audio Inputs (i offload things like Reverbs). So, that is frustrating, as I really want to run on my MacBook. 

    I tell you, I get really sick of Cubase and Windows 10 some times. It is so frustrating to always be fighting software updates and unwanted features that complicate more than anything. I am super close to just going pure Logic X and Mac hardware. Actually, I sort of am in the middle of doing that and just using my big old PC's for Slaves. I am sure Logic has it issues, too. But it seems a bit more stable than Cubase. I really wish vendors would stop the constant updates, and just make something stable. 

    What good is a Christmas tree with fancy lights if the tree stand is constanly falling apart and lights blow fuses/breakers? Grrr!


  • I used Logic since it was on a PC and was on the beta team for years. It is still very solid. I was using Cubase on a 12 core mac pro when I had similar ASIO spike issues and VEP dropouts. It is a shame we all end up as unpaid beta testers for manufacturers these days.  Good luck with everything.


  • Deactivate ASIO Guard. Should solve some of the problems with ASIO spikes and VEP.


    Ben@VSL | IT & Product Specialist
  • Cubase 9.5 works with ASIO turned off. There is at least a 10% CPU usage increase in 9.5 however. I do have the new 64 bit processing turned on in 9.5. The problem is, there is a huge difference in performance between Cubase 9.2 and 9.5 using VEP. My main DAW is a 16 core workstation with 128 gig ram. CPU cycles are usually not an issue.  I would love to see VSL develope thier own DAW for scoring!


  • I have not activated the new 64-bit engine because it generates more CPU usage (as you have experienced). The quality woun't be much better with 64-bit mixing and if I am not mistaken only vst3 plugins can process 64-bit audio. Due to needed converting between 64 to 32 and back to 64-bit there will be an even higher CPU usage, too.
    And 64-bit mixing doesn't sound so much different from 32-bit ;)


    Ben@VSL | IT & Product Specialist
  • I resolved the "No Inputs Found" issue. It turned out that somehow the preferences were set to zero for Audio Inputs. I don't see how that changed, but at least the issue is fixed and not catastrophic. Whew!