Gig Performer | Clever ways to optimize your plugin usage
Eight tips are presented in the article. In this thread we can share other tips or tips useful particularly for a specific plugin.
Ideas are all from existing blog posts and community posts.
Plugin specific tips:
For users of Jam Origin’s MIDI Guitar 2
You might want to consider to use the standalone version of
. MIDI Guitar 2
This way MIDI Guitar 2 runs in a completely separate space and your CPU is able to offload its processing out of your normal audio process thread which helps with the overall performance. Additionally, this will allow you to globally adjust the desired options in MIDI Guitar 2. Some references:
this, this, and this post.
Also make sure to check
this post by Tony Geballe where he explains how to extend the low end of your guitar range for MIDI Guitar 2 using Gig Performer.
Another tip for users that want to use MIDI Guitar 2 in the Global rackspace →
MIDI Guitar in another instance →
additionally to the section:
Plugin implementation and bypass
which links to this post from David-san:
this has probably been asked before but I did some searches and couldn’t find any threads about it.
A useful feature on some modelers is to enable effects automatically when moving an expression pedal.
Practically it would save me the need to have to switch a Wah pedal on before I can alter the frequency with the Expression pedal. Ideally, as soon as I start moving the Expression pedal. the Wah goes on, when I stop using it (maybe after a few 100ms delay) it goes on Bypass.
Any script or…
Edit: i just made the post i´ve written here, a own topic in the tipps section.
you find it here:
Better have this a own Tips topic, rather than just a post in one of the “blogs” threads:
in post #3 is a Gig file of sayed dual crossfade, for your evaluation purposes.
in post #4 is a test gig file with a quad switch, incl. all bypassing widgets of unused FX blocks.
these are for evaluation porposes to show you the idea, and how you can take out alots of advantages by working with individual curvatures vs. dealing with widgets.
here is a Tip from me
( see then below: my screenshots…
Of course, everyone is very welcome to present their tips
i thought you were asking for it,
but now i can´t find that sentence anylonger
Unload everything that you don’t need for the particular sound. More info →
Like Matt Vanacoro said -
Make it lean and mean!
Example: check your Poly settings on the Arturia synth plugins.
Some tips that
@Ali_B shared on the Facebook group:
A couple of things I have done on very long signal chains. Firstly, using Amplitube 4 instead of Amplitube 5. For pedals there is no improvement to the sound in AT5. Way lower cpu.
Secondly setting the i/o of each block to mono. It doesn’t halve cpu use but it is a significant percentage if you’re on the edge.
TBH on sensible chains where each rackspace is targeted to specific sound (4-5 FX blocks) these are both unnecessary for me even on a 10 year old MacBook Pro using a 128 buffer size.
Running Diva at ‘great’ rather than ‘divine’ resolution and ‘multicore’ helps too, but I’m only using 3-4 note polyphony and my preferred patches don’t seem to tax the cpu.
Various logging options may also affect response times of plugins. Additionally, review options to see what is saved as a part of the plugin’s state, as otherwise your gig file may explode in size.
Gig Performer | Gig Performer seems to be writing megabytes of data
Another tip: if you are using a plugin’s Persist mechanism (for example Omnisphere’s
Live Mode), you may want to switch to Gig Performer’s MIDI Patch Persist feature. More info is in . this blog
It’s also a question of whether you are going to use (say) Omnisphere Live mode and stay in one rackspace. If so, Gig Performer’s Patch Persist feature is simply not relevant.
However, if you want to be able to jump to other rackspaces and have Omnisphere stay on until you release notes in another rackspace, then Gig Performer’s Patch Persist needs to be on.
Tip for Amplitube:
LINK + VIDEO.
From what I understand this is not a real direct-from-disk streaming, in the sense that the sample are streamed from disk only once when first loaded and not each time they are accessed, right?
I’m not a Kontakt expert, but this tip is related to changing the buffer size, i.e. what amount of data you want to keep in RAM. Basically, more data you keep in RAM and not stream from the disk, it is more likely to have a streamlined experience. On fast SSDs you can (allegedly) keep the buffer as low as 6 KB.
From what I understand, they load at least a 6Kb beginning of all samples and load the rest on the fly from the disk. But, my understanding is that once it is downloaded it stays in memory. It seems to be differed downloading rather than real streaming where nothing stays in memory once played. If it indeed works like this it is not only almost useless, but also dangerous. If I run short in RAM I prefer to know it at loading time rather then having to discover it the hard way while playing.
I understood like that, as well. One smaller (or larger, if you set it like that) is loaded into RAM and stays there, and the rest is streamed from the drive. Used instrument memory = number of samples * preload buffer size.
Perhaps these video may make things clearer:
Here is an in-depth video showing how to use Sample Robot and Kontakt.
A useful post:
Next thing to look at: optimizing the plugins. Reducing polyphony, dropping unnecessary built-in effects and adjusting sample rate and buffer size will all have effect on the CPU hit of each individual plugin. Since you’re playing in a live band setting, you can propably reduce the polyphony of V Piano quite drastically and still sound great. Try out different settings and listen critically. You might get away with much less detailed piano and rhodes sounds, they may even sound BETTER in the context than the hyper-realistic concert grand with all the symphatetic resonance magic filling the frequencies.
Same applies to synths: see how dense chords you’re actually playing with the JUP8 and OBX and choose the maximum polyphony accordingly.
Plugin recommendation for a catch-all keyboard setup - #6 by mikkopat