Let's only use my woodwinds instance for some tests. Thanks a lot for your reply ! I've seen you're very active on this Vienna Forum, thanks again for that! In that, 4 total would be enough, I'm grandmothering in older templates.
I do tend to commit to audio using one thing, which has long (>20s) tails and is a bit unwieldy, and I've learned to have the Master containing the room/verb in its own output, but 4 per instance, say 3 instances is max for me. In v7, useful (actual) names of parameters are seen by Cubase in a single menu, per instance. There is a feature in VEP which for me amounted to being able to obviate mixing in Cubase like 99%, and then it's about audio I've committed to: the automation map. You may believe at this writing this many outs is necessary, but it is only really necessary if you need 30 stems to mix from. (Also, your threads per instance count is something you can experiment with.) "30 stereo outs returned to Cubase" is fixed by stopping that. If it is the former, I would seriously advise a different workflow. If you mean 30 stereo, or some combo of stereo and mono coming out of Kontakt to VE Pro, this is not likely to be at all difficult with the muscle you're indicating and I suspect you mean the former. * If you mean 30 stereo outs coming back to Cubase, this is probably your problem and it does use CPU kind of to the exclusion of it being otherwise used well. Is it also wrong knowing that I need (want) more than 10 instances.? On the preferences inside VEPro, the default thread count per instance is set to 2. Is more than 10 instances with more or less 30 Kontakt inputs just a foolish idea? I was wondering if I can change anything on VEPro.
Question: How can I fix this? I tried everything I could so Kontakt use more RAM and less CPU, but it is still the same. When Cubase and VEPro are "linked", VEPro shows on every instances that it is using more or less 90% of the CPU.
#Audio overload windows 10 mac#
It actually sounds the same than if the connection between the server and the Mac was 100 Mbits/s instead of 1 Gbit/s. However, when I connect more and more instances (like more than 10), VEPro is using so much CPU and all the sounds are suddenly terrible. (I'm using VST with Kontakt and also the dedicated plug-in from Spitfire Audio). Here's the thing, when I connect only 2 or 3 instances with Cubase, everything's working perfectly. Knowing that the server owns 256GB of RAM, I worked on a pretty big template both on Cubase 11 on my Mac and VEPro 7 on the server machine.
#Audio overload windows 10 pro#
I'm using VEPro 7 on Windows Pro on my Dell R610 Server. First of all, I'm so sorry if there is multiples threads already talking about VEP and CPU use.
0 kommentar(er)
