Compyfox wrote:juffi wrote:Actually bridging all that cpu eaters and latency monsters (f.e. Halionsonic2, Kontakt, Ozone5 (!) .....) and running in Performance mode also solves that 30% Windows cpu/99 % Asio load Problem. Because the auxhost.exe processes are outside from cubase and will be distributed reasonable on the cores and asio load will fall down.
No problems with stability so far, i even tested a big Project to see if i can lower the latency .
So I take it, that C7 just has a funked up CPU core distribution?
Which could also clear why the x64 version works better(!) smoother than the x86 version. But if jBridge can still tickle a tad more out of it... then we have the culprit to most C7 problems.
I really, really have to retry that again. Unfortunately, jBridge only covers up until VST2.x, not VST3.
Seems like Cubase 7.5 (from 7 on maybe..) has a weird distribution. You can have 1 Core occupied and the other cores are doing nothing , but asio load is going towards red (huh?) . Some guys from recording.de reported this as well. Seems to happen if you have 1 midi track and a plugin loaded like kontakt with big samples. If you continue to work with more midi tracks, the distribution starts. Maybe some guys are making big eyes because they have an Intel core i7.
Afaik as i worked with Cubase Sx3 i could squeeze everything out of the processor and asio load. Now in C7 seems like only 1 kontakt (or another sample based plugin) is enough to destroy your asio load.
Another thing Steinberg should introduce is real gui Hardware acclereation. Hell even Google Browser does it, why not accelerate the mixer and Project window f.e.?