Menu
What's new
By:
Filters

Cubase, Kontakt and VEPro, Multi-Threading enabled or not for best CPU perfomance?

C

chizfreak

New Member
Hello, I've searched on this topic but all answers are old (2 years old usually) or inconclusive. These questions are related to very big, high-track-count Orchestral Template projects with a lot of virtual instruments. I would really appreciate your help on this.

As of now, using the latest version of Kontakt 7 and the latest version of Cubase 13, and VEPro 6.5 (I didn't want to upgrade to 7):
1. Is there better performance hosting the Kontakt virtual instruments inside VEPro Server and connecting it to Cubase via the VEPro plug-in, or is it better to host Kontakt inside Cubase itself?
2. Should Multi-Threading INSIDE Kontakt be enabled if hosting Kontakt inside Cubase? What about if hosting inside VEPro Server?
3. Should Multi-Threading INSIDE Cubase be enabled if hosting Kontakt inside Cubase? What about if hosting inside VEPro Server?
4. Same for ASIO-Guard: Should ASIO-Guard be enabled if hosting Kontakt inside Cubase (most people agree yes I think)? What about if hosting inside VEPro (I've seen some people say in that cause ASIO Guard should be off in Cubase)?
5. Does ASIO-Guard add latency when live-playing a MIDI Track connected to the VEPro Plug-in (which functions as VSTI and is in turn is connected to VEPro Server outside Cubase)?
Click to read more...
 
chizfreak said:
Hello, I've searched on this topic but all answers are old (2 years old usually) or inconclusive. These questions are related to very big, high-track-count Orchestral Template projects with a lot of virtual instruments. I would really appreciate your help on this.

As of now, using the latest version of Kontakt 7 and the latest version of Cubase 13, and VEPro 6.5 (I didn't want to upgrade to 7):
1. Is there better performance hosting the Kontakt virtual instruments inside VEPro Server and connecting it to Cubase via the VEPro plug-in, or is it better to host Kontakt inside Cubase itself?
2. Should Multi-Threading INSIDE Kontakt be enabled if hosting Kontakt inside Cubase? What about if hosting inside VEPro Server?
3. Should Multi-Threading INSIDE Cubase be enabled if hosting Kontakt inside Cubase? What about if hosting inside VEPro Server?
4. Same for ASIO-Guard: Should ASIO-Guard be enabled if hosting Kontakt inside Cubase (most people agree yes I think)? What about if hosting inside VEPro (I've seen some people say in that cause ASIO Guard should be off in Cubase)?
5. Does ASIO-Guard add latency when live-playing a MIDI Track connected to the VEPro Plug-in (which functions as VSTI and is in turn is connected to VEPro Server outside Cubase)?
Click to expand...
Hello. I'd upgrade to 7 if I were you, if only because of improved performance and stability.
I think the best person to answer anything VEPro-related is @Ben , but from personal experience;

1. Yes, very much so. Clearly you can do both, but using VEPro to host your instruments really helps a lot.
2. Yes, I think so to both. Isn't that the default? Just leave it then.
3. Yes.
4. Yes, but you should disable ASIO Guard for VEPro.
5. Yes, turn on Constrain Delay Compensation if you want to record something in if the latency is too much and/or tweak your audio interface buffer size. Bump up your buffer size to its max once you start mixing/mastering.

You can also tweak the buffer setting for each instance if needed;
Screenshot 2024-01-28 002614.png
 
quickbrownf0x said:
Hello. I'd upgrade to 7 if I were you, if only because of improved performance and stability.
I think the best person to answer anything VEPro-related is @Ben , but from personal experience;

1. Yes, very much so. Clearly you can do both, but using VEPro to host your instruments really helps a lot.
2. Yes, I think so to both. Isn't that the default? Just leave it then.
3. Yes.
4. Yes, but you should disable ASIO Guard for VEPro.
5. Yes, turn on Constrain Delay Compensation if you want to record something in if the latency is too much and/or tweak your audio interface buffer size. Bump up your buffer size to its max once you start mixing/mastering.

You can also tweak the buffer setting for each instance if needed;
Screenshot 2024-01-28 002614.png
Click to expand...
Thank you for your answers!

I didn't know VEPro 7 had better performance than 6.5, I will consider upgrading to 7 more seriously then.

Two questions:

1. Are you sure that ASIO-Guard adds latency when live-recording (I mean when you record enable a MIDI track so you can play with a MIDI keyboard in real time) when the MIDI track is routed to the VEPro plug-in (that connects to the outside VEPro server)?

I was told on the Cubase forums that Cubase automatically disables ASIO-Guard (a.k.a. ''puts the track in real-time processing'') when that track is record enabled, and specifically told that because of that Virtual Instruments hosted inside Cubase in Instrument Tracks do not have any added latency by ASIO-Guard when playing them with a MIDI Keyboard (although, admiteddly, they were refering to Instrument Tracks where the Instrument is host inside Cubase itself, but I don't think Cubase ''can tell the difference'' between an Instrument Track with an actual VSTi inside of it and the VEPro plug-in).

According to what I understood, the latency only applies in playback (when playing already recorded material, so to speak) and not to tracks that are currently being recorded to. But I'm not sure if VEPro plug-in is a special case or something, plus doesn't the VEPro plug-in itself add latency because it has its own buffer? (in that case it would always have more latency than hosting the VSTi in the DAW itself unless you turn the plug-in's buffer to none which usually ends up in crackles and pops).

2. Taking what I said above into account, why is it recommended to disable ASIO-Guard in Cubase if using the VEPro plug-in connected to a VEPro Server?
 
Last edited:
chizfreak said:
Thank you for your answers!

I didn't know VEPro 7 had better performance than 6.5, I will consider upgrading to 7 more seriously then.

Two questions:

1. Are you sure that ASIO-Guard adds latency when live-recording (I mean when you record enable a MIDI track so you can play with a MIDI keyboard in real time) when the MIDI track is routed to the VEPro plug-in (that connects to the outside VEPro server)?

I was told on the Cubase forums that Cubase automatically disables ASIO-Guard (a.k.a. ''puts the track in real-time processing'') when that track is record enabled, and specifically told that because of that Virtual Instruments hosted inside Cubase in Instrument Tracks do not have any added latency by ASIO-Guard when playing them with a MIDI Keyboard (although, admiteddly, they were refering to Instrument Tracks where the Instrument is host inside Cubase itself, but I don't think Cubase ''can tell the difference'' between an Instrument Track with an actual VSTi inside of it and the VEPro plug-in).

According to what I understood, the latency only applies in playback (when playing already recorded material, so to speak) and not to tracks that are currently being recorded to. But I'm not sure if VEPro plug-in is a special case or something, plus doesn't the VEPro plug-in itself add latency because it has its own buffer? (in that case it would always have more latency than hosting the VSTi in the DAW itself unless you turn the plug-in's buffer to none which usually ends up in crackles and pops).

2. Taking what I said above into account, why is it recommended to disable ASIO-Guard in Cubase if using the VEPro plug-in connected to a VEPro Server?
Click to expand...
1. Yes, pretty sure it does. They all do. The solution is simply to have a(n optimized) system and interface that are powerful enough to process everything so you can keep your buffer size as small as possible when recording, so you won't notice. VEPro and constraining delay compensation will help you with that. OR freeze tracks, etc.

2. VEPro is already much more optimized for streaming audio/data than Cubase + ASIO Guard are. You'll f*ck that up if you leave ASIO Guard on for the plugin.

So it's always what Ben says. :thumbsup:
 
Where does one turn off ASIO guard in Cubase plug-in manager. The manual states:

If you select Studio > VST Plug-in Manager and click Show VST Plug-in Information, you can deactivate the ASIO-Guard option for selected plug-ins.

I don't see the option to show VST Plug-in Information in the manager.

M.
 
Thank you all for your answers, I'm new to this forum and I have to say everyone here has been very nice and helpful :emoji_thumbsup:.

And thank you Ben for the heads-up, I didn't even know you could disable ASIO-Guard for specific plug-ins only, good to know!
 
You must log in or register to reply here.
Top Bottom