PianoTeq Global Rackspace

Hello everyone,

I’m looking for some advice. I use 2 keyboards: the bottom one is an 88-key weighted model from Native Instrument, which I primarily will use for Pianoteq. Occasionally, I will also use it for LA EP and acoustic guitar sounds. Additionally, I layer strings or pads at times, all set up in the global Rackspace.

I noticed that my CPU usage was around 17-19%. After deleting all the VST’s except Pianoteq, the CPU usage dropped to 1%. Should I go back to creating the large global Rackspace with all those VST’s, or is there a better way to save CPU resources? I would appreciate any advice. Thank you

I would use different local rackspaces.

If it is in the Global rackpsace, it is always active. So it may continue to use CPU even if it not used. In contrast, if you put a CPU heavy instrument in a local rackspace that is not used, it should not use CPU.

With regard to ram, the same amount is used regardless of whether you put a plugin (with a particular “sound” selected) in a local rackspace or the Global Rackspace.

In light of this (this may be contrary to the initial concept of the Global Rackpsace), from a computer resource perspective, I think it makes sense to consider putting often used ram heavy instruments in the Global Rackspace, while putting low ram (CPU heavy) instruments in local rackspaces.

Great thank you for the quick responses

I don’t think that’s entirely true.
Although placed in the global rackspace, the plugin can be controlled in individual rackspaces and muted, so it doesn’t use CPU.

My understanding is “muting” does not make it inactive. But, you could bypass it.

(I have never bothered doing that. I suppose you would want the default to bypass and then have a widget in the Local rackspace to un-bypass it when used? Not sure).

(Also, I think DHJ has said the well-coded plugins should really not use (much, if any) CPU if they are not being used.)

I said they shouldn’t, but they’re not always well coded!

1 Like

[Sorry, meant DHJ]

The good ones do, but to play it safe I bypass everything using plug-in persist 2 scriplet. Highly recommend!

1 Like

Exactly what I do

Make sure that you are using the bypass function associated to each plugin that you use. I have different configurations for live shows / festivals compared to normal church services. In the church services, I am running 16 plugin instances (8 top keyboard assigned and 8 bottom keyboard assigned) I’ve never ran into any issues or cpu usage problems and that is running anywhere from 128-192 latency on a macbook with 16 gb of Ram on a M1.

Try that and post your results. Bypassing is my go to.

Honestly I don’t even know what you mean by instances. Can you explain that to me. Is it just say if I have a organ VST in every rackspace.? Thank you

With software, an “instance” is one instantiation of an app/plugin (that means it is loaded in memory and running/available to run). The verb “to instantiate” means “to run” or “to execute”. Clear as mud? :grin:

In your options tab, you have the option to open up another “instance” or window of GP. It is VERY handy when assigning rackspaces to different controllers. It allows for usage of multiple interfaces and audio performance.