42
5 PRESETS
Each block you place in a preset contributes to the total CPU load for that preset. You can check the current load
at any time by viewing the mini CPU meter at the top of the grid.
The maximum allowable load is about 80%, and if you manage to get much above that, audio performance may be
compromised.
When inserting a new block would cause an overload, this is prevented and the message “INSUFFICIENT CPU” is
displayed. It is assumed that a new block will be used to its limit when making this determination.
If you are prevented from inserting a block because of CPU limits, you can remove an unused or less important
block. Adjusting certain parameters can also help. Beware of trying to set parameters back to higher values after
inserting the desired block. At extremely high CPU usage levels, the Axe-Fx III may become unstable and/or Axe-
Edit may stop responding.
Here are a few of the common block parameters whose settings have a measurable effect on CPU usage:
Amp: Output Comp: Set to "0" for the least CPU usage.
Cab: Mute: The more IRs you use per block, the higher the CPU usage.
Cab Preamp and Room settings also affect CPU.
Reverb: Quality and Echo Density. Lower = less CPU. The “Spring” type uses the least CPU.
Compressor: Set Type to one of the "PEDAL" options to use less CPU.
Phaser: Stages. Lower = less CPU.
Filter: Order and Q. Lower = less CPU.
Multitap Delay: Type. Different types have different CPU requirements.
Modifiers also affect CPU usage.
Synth : More voices = more CPU.
The Fractal Audio Wiki keeps a list of CPU saving ideas. Find it at:
https://wiki.fractalaudio.com/axefx2/index.php?title=Presets and_blocks
.
CPU & USB
With its dedicated processor for USB, CPU usage is not increased when USB is connected.
PRESET CPU LIMITS
