October 2024: Fractal Audio's VP4 Virtual Pedalboard has been added to the wiki.

Difference between revisions of "Presets"

From Fractal Audio Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
 
__TOC__
 
__TOC__
''Image to be added.''
 
=Number of presets=
 
* '''Axe-Fx III''': 512 (presets are much larger than in previous hardware).
 
* '''Axe-Fx II XL and XL+''': 768.
 
* '''Axe-Fx II''': 384.
 
* '''FX8''': 128.
 
* '''AX8''': 512.
 
  
=Loading a preset=
+
[[Image:Presets.png|300px|link=]]
  
Note to Axe-Fx II Mark I/II owners: due to space limitations in the Mark I/II BOOTROM, firmware Quantum 5.00 and later is not backwards compatible with presets created prior to firmware version 15.08. This limitation only exists for the Mark I/II. XL and XL+ still maintain backward compatibility.
+
=Number of preset slots=
  
You can load factory presets and presets from other users into your device. Presets have a .syx file extension. Presets are available on the user forum, Axe-Change and from other sources. If you use Fractal-Bot, a Fractal Audio editor or a MIDI librarian such as Snoize SysEx Librarian (Mac) or MIDI-OX (Windows): make a connection between your computer and the device, load the .syx file and send it to the device.
+
'''Axe-Fx III'''
 +
* Mark I: 512
 +
* Mark II, Mark II Turbo: 1024
 +
'''FM3, FM9''': 512<BR>
 +
'''VP4''': 104<BR>
 +
'''Axe-Fx II'''
 +
* Mark I and II: 384
 +
* XL and XL+: 768
 +
'''AX8''': 512<BR>
 +
'''FX8''': 128
  
To load an external preset file in the editor, click Import, or drag and drop a file onto the editor.
+
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
  
The hardware is always ready to receive presets. If you upload a preset, the preset is not yet stored but kept in a buffer. If you want to keep it, save it in a preset slot.
+
<blockquote>
Preset files are also kept in bank files with the .syx file extension. You can use the editor to pick individual presets from a bank file.
+
[https://forum.fractalaudio.com/threads/what-was-the-trick-for-faster-boot-up.175256/post-2127759]
 +
The progress bar during boot indicates presets being copied from FLASH to RAM. If a preset is empty it is skipped so the more empty presets you have the shorter the boot time.
 +
</blockquote>
 +
</blockquote>
  
<blockquote>"There are two possible destinations for a preset: the edit buffer or a defined preset number. The destination is encoded in the data. If it's not going to the edit buffer then the preset was harvested from a hard drive somehow. When you load a preset with Axe-Edit it sets the destination bytes. However if you use a librarian then the preset may go to the edit buffer or to a defined preset location depending upon the destination bytes. You can identify the preset destination from the data. If the seventh byte is 7F then it will go into the edit buffer, otherwise it will go into preset memory. For example: F0 00 01 74 03 77 7F 00 goes to the edit buffer whereas F0 00 01 74 03 77 01 02 will go to bank B preset 2 (patch 130)." [http://forum.fractalaudio.com/axe-fx-ii-discussion/58581-help-loading-presets-using-sysex-librarian.html#post-732659 source] </blockquote>
+
=About presets=
  
=Loading presets through MIDI Program Changes=
+
The differences between presets, scenes and channels:
  
Presets are divided in banks. To select a preset through MIDI, a MIDI Bank Select message and a Program Change must be transmitted. The Owner's Manual lists which MIDI Program Changes correspond with presets on the hardware. See [[MIDI]].
+
; Presets :A Preset is like your traditional pedalboard. Because we can have many different presets stored in the modeler, it is as if we have numerous pedalboards within reach at any moment.  
 +
; Scenes :[[Scenes]] are like your traditional pedalboard at a particular moment, with effects on or off and set to a specific channel.
 +
; Channels :[[Channels]] are like the pedals on that pedalboard with its controls set in a specific way. There are four channels in most blocks, so there are four different sets of settings.
  
=Loading a preset on another type of hardware=
+
The hardware display and the switch LED on compatible foot controllers show the currently loaded preset.
  
Axe-Edit lets you transfer presets from an Axe-Fx II Mark I/II to a XL and XL+. But not the other way around. You can share individual effects blocks between Axe-Fx II models, AX8 and FX8 through the editor's Block Library.
+
Read more about presets in the [[Owners_Manuals| official manuals]].
  
[[FracTool]] lets you share presets between the various Axe-Fx II models and between Axe-Fx, AX8 and FX8, converting on the fly.
+
=Zoomed display mode=
  
Another way to store preset settings is to export them into a CSV file which lists all parameter values. The editors offer this functionality.  
+
The FM3 and FM9 support a zoomed display mode, where the preset title and all eight scenes are displayed in a large font for easy viewing. Turn the <q>B</q> knob on the Home screen to switch between display modes. In zoomed mode, use the cursor keys to switch between scenes and use the Value Wheel then press the <kbd>Enter</kbd> button on the front panel to switch presets.
  
<blockquote>(Yek) "When I transferred all my presets from the original Axe-Fx II to the XL, I kept a log of changed parameter values. These are the ones you may
+
Zoomed:<BR>
want to check before and after transfer:
+
[[image:S2.jpg|300px]]
* COMP — TYPE and SUSTAIN and MIX and AUTO
 
* PEQ — FREQ TYPE (bands 1 and 5), GAIN (all bands), LEVEL
 
* GEQ — 16k slider, LEVEL
 
* TREMOLO — LFO PHASE and START PHASE and WIDTH and TYPE
 
* MIXER — BALANCE
 
* CHORUS — LFO PHASE"</blockquote>
 
  
[http://forum.fractalaudio.com/posts/1298352 Walkthrough by Yek.]
+
=Factory presets=
 +
 
 +
Read <q>[[Factory presets]]</q> for more information.
 +
 
 +
=Songs and setlists=
 +
 
 +
Read <q>[[FC-6_and_FC-12_foot_controllers#Songs_and_setlists|Songs and setlists]]</q> for more information.
 +
 
 +
=Guidelines=
 +
 
 +
* Try to stick to the same grid layout/routing if possible, to simplify viewing and editing and to increase preset switching speed.
 +
* Re-use effect blocks with preferred settings and levels, through [[Global blocks]] or the [[Library|Editor's Library]].
 +
* Assign [[External controller|External controllers]] in a consistent way. Decide if you want them to reset or not when switching presets using the PC Reset parameter.
 +
* Effects in front of Amp and Drive blocks should not be set to stereo. Certain effect blocks, such as Amp, Drive and mono Cab, sum the signal to monoaural. Check your system settings and blocks for correct mono and stereo operation to prevent phase cancellation. Read <q>[[Mono and stereo]]</q> for more information.
 +
* Make sure that the blocks maintain [[I/O_connectivity_and_levels#Audio_jargon|unity gain]] in engaged and bypassed states.
 +
* Set Mix, Level, and Bypass parameters correctly when placing effects in parallel rows.
 +
* Make sure that the overall preset level matches that of other presets and does not clip when engaging a volume boost, Wah, etc. Use the <code>Tools | Preset Leveling</code> tool in the editor.
 +
* Let delay and reverb trails spill over between scenes.
 +
* Check the preset’s noise gate settings. Turn it off when not needed to save CPU.
 +
* Adjust the desired [[Input impedance]] in the [[Input block]] if needed and supported by the processor.
 +
* Use a consistent way to boost the level for leads.
 +
* Make sure that effect blocks are set to the correct channel in each scene.
 +
* If Tempo is set to <q>Preset</q>, set the preset's tempo settings.
 +
* When using one Amp block on an Axe-Fx: use AMP 1, not AMP 2.
 +
* Make sure that [[CPU usage]] stays below the limit (80%). Note that CPU usage can vary, depending on the channel of effect blocks. Also note that the value is the ''average'' and that spikes in CPU usage can be higher.
 +
* Place effects where they should be placed, e.g. Pitch before or after Amp/Cab.
 +
* Some people like to mute scenes that are not being used by disabling all blocks in those scenes. Others prefer to copy a generic scene for the preset to the unused slots and clear the name. The first ensures that ONLY the defined scenes will output sound, the second allows for accidentally scrolling into an <q>undefined</q> scene so sound is still output.
 +
* Use a consistent naming scheme for preset titles.
 +
* Use a consistent naming scheme for scene titles, if the processor supports it.  
 +
* Choose titles that fit on the hardware displays of the processor and foot controller. The displays are capable of showing up to ten characters.
 +
* FC-6 and FC-12 controllers, FM3, FM9: program per-preset switches.
 +
* AX8 and FX8: assign switches to effects in the preset.
 +
* [[FRFR]]: enter the desired low-pass and high-pass settings in the Cab block if desired.
 +
* Configure the Per-Preset Perform page.
 +
* Check the block Meters in the second tab in the Layout view on the front-panel.
 +
* Make sure the preset still works if a pedal or switch isn’t connected.
 +
 
 +
Note: The number of blocks in a preset does NOT have any impact on latency. Depending on the hardware, the ''type'' of blocks can affect latency. Read this: [[Latency]].
 +
 
 +
=Loading presets=
 +
 
 +
==Load a preset==
 +
 
 +
Load presets in one of the following ways:
 +
 
 +
* Use the tools on the hardware: the Value wheel, or cursor keys, or <code>Home > Presets</code> menu on the front panel. Use the soft knob to sort.
 +
* Use the [[Editors|editor]]: click on the Presets button or use <code>Tools > Manage Presets</code>.
 +
* Use a Fractal Audio controller.
 +
* Use a third-party MIDI controller.
 +
* Use a switch that's connected directly to the unit.
 +
* Use [[FracPad and FracTool|FracPad]].
 +
 
 +
The <q>Ignore Redundant PC</q> parameter in the Setup  menu determines what happens if the unit receives a MIDI Program Change for a preset that already is loaded. If Ignore Redundant PC is ON, and the desired scene is different from the current scene, the preset is not re-loaded but the default scene is selected.
 +
 
 +
The Axe-Fx III, FM9 and FM3 let you map MIDI commands to preset switching.
 +
 
 +
==Load a recently loaded preset again==
 +
 
 +
The [[Editors|editor]] keeps a list of recently loaded presets under <code>Preset > Recent Presents</code>.
 +
 
 +
Alternatively, hold <kbd>Command</kbd> on macOS and click on the <code>Presets</code> button.
 +
 
 +
==Load from disk==
 +
 
 +
Preset files on disk have a <samp>.syx</samp> file extension. Bank files, which contain multiple presets, have the same file extension.
 +
 
 +
These are different ways to load a preset file from disk into the hardware:
  
Another conversion issue concerns effects that support X/Y:
+
* Import the file into the connected editor through <code>Preset > Import</code>.
<blockquote>"Any blocks that have X/Y on the XL but not on the Mark II will not import the bypass state as that is stored differently. You need to manually adjust the bypass state after import." [http://forum.fractalaudio.com/axe-fx-ii-bugs/100398-potential-bug-xl-importing-mk-ii-presets.html#post1203688 source] </blockquote>
+
* Drag and drop the file onto the connected editor.
 +
* Use the editor's <code>Tools > Manage Presets</code> tool.
 +
* Use [[Fractal-Bot]].
 +
* Use a MIDI librarian such as Snoize SysEx Librarian or MIDI-OX.
 +
* Use [[FracPad and FracTool|FracTool]].
  
[http://axefxtutorials.com/2016/02/importing-block-files-into-fas-gear-and-saving-presets-as-block-files-to-share-among-devices-axe-fx-ii-ax8-fx8/ AxeFxTutorials article about sharing blocks.]
+
You can use the editor with your device or [[Fractal-Bot]] to transfer entire banks to the hardware. The editor also lets you open a Bank file and import a single preset from that file.
  
[http://forum.fractalaudio.com/threads/using-backing-tracks-to-trigger-preset-scene-changes-w-bandhelper.125461 Forum discussion about using the hex command to recall presets and scenes.]
+
The hardware is always ready to receive presets.
  
=Loading a blank preset on startup=
+
After loading a preset from the disk into the hardware, the preset resides in a temporary buffer. It is not saved in the hardware's memory <u>until you explicitly Save it</u>.
  
'''Axe-Fx III''': hold HOME on startup. The Axe-Fx III will boot with an empty initialized preset in location 000.
+
==Import from other devices==
  
'''Axe-Fx II''': press and hold RECALL on startup.
+
Presets are device-specific, which means that there are limitations to sharing presets across different modelers.  
  
'''AX8/FX8''': press ENTER when the splash screen is displayed.
+
Presets for the Axe-Fx III, FM9 and FM3 are mostly compatible (VP4: not); The most important factor is available CPU power. Other limitations are mentioned in [[Axe-Fx III, FM9 and FM3]]. The PresetTranslator in the [[Editors]] maintains a log file, accessible in the Help menu.
  
Software editors: select Preset > Clear Preset to create an empty preset.
+
Presets moved between the original hardware and their updates, such as the various <q>Turbo</q> and <q>Mark II</q> series are completely compatible if the block types are supported. The respective Edit applications are able to translate between the other units, however they do not <u>convert</u> the presets to fit. Said differently, an Axe-FX III preset that will exceed the FM3's CPU will not be automatically adjusted to run correctly on the smaller processor. That is our job to do before attempting to import the preset. Failing to do so can lock up the smaller siblings requiring a reboot and possibly using recovery steps to remove the preset.
  
=Default scene=
+
There are various workarounds for sharing presets between other processors:
 +
* The editor's [[Library]] lets you share effect block files between devices.
 +
* The editors let you export a preset as text, which will contain all parameter values.
  
[[Scenes#Default_scene|Read this]].
+
==Startup preset==
  
=Factory presets=
+
You can specify in the [[Setup menu]] which preset should be loaded when the device is powered on. This applies to the FM9 and FM3 only, at the time of writing.
 +
 
 +
==Default scene==
 +
 
 +
The processors let you specify which scene should be recalled upon loading a preset. Read [[Scenes]] for more information.
  
Read this: [[Factory presets]].
+
==Edited LED==
  
=Preset shows up empty=
+
Current generation processors and editors (optionally) prompt before changing presets if the current preset has been edited. This makes sure you do not lose edits. Note that the prompt doesn't appear when changing presets via MIDI.
  
If a preset shows up empty, it was probably created with firmware that is more recent than loaded on your hardware. Update the firmware!
+
This feature can be turned on/off in the [[Setup menu]].
  
=Preset size=
+
That menu also let you determine whether switching scenes should be marked as an Edit or not. When both parameters are enabled, you can't switch between presets using the FC controller, because the hardware will ask for confirmation first.
  
In rare cases a preset can get too large (too many bytes). This is not the same as overloading the CPU. There's no warning or checking mechanism for this. If this happens, certain values won't get stored, or revert to zero upon recall. These are rare cases, which seem to occur mostly when the user uses a VERY large number of modifiers/controllers.
+
==Gapless changes==
  
<blockquote>"A preset in the III is four times the size of a preset in the II. One preset easily does the work of four or more." [http://forum.fractalaudio.com/threads/why-512-presets.135057/page-2#post-1597873 source]</blockquote>
+
In current firmware, switching presets can happen gapless.
  
=Preset switching speed=
+
Read this: [[Setup_menu#Gapless_Changes|Gapless Changes]].
  
<blockquote>"With any device that features flexible routing you have to mute, switch then unmute. This takes time. The reason is that if you don't do this then you'll end up with sound from one of the blocks that may have moved to a different position possible causing a loud pop or other artifact. For example, if you have a simple amp->cab->delay preset then you switch to a preset that has delay->amp->cab the sound from the delay will get amplified during the switch so you have to mute everything, wait for the signals to decay, rearrange the blocks, then unmute. Products with a fixed routing can switch faster since they don't have to worry about rearranging blocks. The Axe-Fx amp modeling is also far more intricate and complex than other products and this requires muting the amp modeling for a short time to allow the bias points to settle." [http://forum.fractalaudio.com/threads/lag-on-the-ax8-when-switching-presets.108343 source] </blockquote>
+
==Spillover between presets==
  
<blockquote>"Our modeling is very detailed and whenever the amp model changes the "virtual circuit" needs to be reconfigured. We can switch quickly but often this causes clicks and pops due to the reconfiguration. So the amp block needs to run silently for a bit so things will settle. Then we unmute the block. This mute period is what you are hearing. Most other products just use a fixed algorithm and change the input/output EQ and gain. With this type of algorithm you can switch quickly without clicks and pops but, of course, you don't get the realism and detail." [http://forum.fractalaudio.com/threads/does-the-ax8-have-an-audio-gap.118736/page-2#post-1413280 source] </blockquote>
+
Read [[Spillover]] for more information.
  
<blockquote>(Axe-Fx II) "Dropout is only 20-30 ms. If you are experiencing more than that then your MIDI controller is not programmed properly." [http://forum.fractalaudio.com/axe-fx-ii-discussion/58589-preset-switching-latency-2.html#post732479 source] </blockquote>
+
==Send MIDI when loading presets==
  
=Preset-Cab bundle=
+
The [[Scene MIDI block]] lets you send MIDI Program Changes and Control Changes when loading a preset.
  
A Preset-Cab bundle is a single file containing the preset and one or more user cabs. You can save a bundle in Axe-Edit or AX8-Edit and load it into Axe-Edit or AX8-Edit using the Import button.
+
==FC: automatically display scenes after switching presets==
  
Do not not share IRs which are protected by an EULA, license, copyright etc.
+
You can configure an FC controller, the FM3 and FM9 to automatically display scenes after switching presets. In the PRESETS layout, add a layout link from the foot switch for that scene to the SCENES layout. When you select the preset, the modeler will automatically switch to display the scenes. Repeat as necessary for other preset switches.
  
=Moving a preset=
+
==Crossfading==
  
You can move a preset by using Store > Swap on the hardware (not on Axe-Fx III). Or use the software editor's Preset Manager.
+
There are several ways to crossfade sounds.
  
=Delete all presets=
+
'''Scene scontrollers''' — Use Scene controllers with a damping value of several hundreds of milliseconds.
  
The Utility menus on the hardware let you delete all presets at once. Be careful!
+
'''Sequencer''' — Use the Sequencer internal controller. (source: Bakerman)
 +
# Set it to something like 16 steps, Rate just over 1 Hz, Values increasing in steps of 10% and have it sit at 100% for the last 6 steps.
 +
# Place a volume block in each signal chain and assign Seq to turn chain B up and chain A down.
 +
# Use several hundreds of milliseconds of damping.
 +
# Assign one switch to Sequencer Run control and a second switch to bypass both volume blocks. You'll want them engaged before/during the crossfade.
 +
# Use Mute Bypass mode for the Vol block in chain A, Thru Bypass mode for the one in chain B.
 +
Now you can be playing sound A, hit switch 1 and get the 8-9 second crossfade, then hit switch 2 within the next 4-5 seconds before the sequencer restarts. If you wait too long you'll hear it fade back quickly to A (then B gradually again) but whenever you hit it you'll hear sound B regardless of what the sequencer's doing. After that you can always stop the sequencer and switch back to sound A; it will just be instant instead of a crossfade.  
  
=Printing a preset or user cabs list=
+
'''Pedal''' — Use a pedal to crossfade between i.e. two AMP blocks:
 +
# Assign the Level parameter of one AMP block to an external controller.
 +
# Do the same with the other AMP block, using the opposite curve (or reversed Min/Max values) and using the same external controller.
 +
# Assign the external controller to a pedal.
  
In the software editor, select Tools > Export as Text > Preset List.
+
==Create a fully initialised empty preset==
  
=Exporting the values of all parameters of a preset=
+
[https://forum.fractalaudio.com/threads/axe-fx-iii-firmware-25-00-public-beta-cygnus-x-3.202659/page-35#post-2538921 Fractal Audio:]
  
In the software editor, select Export Preset as CSV.
+
# Power down the unit and wait five seconds.
 +
# Power on holding HOME until the boot-up progress bar first appears.
 +
# The unit will boot with an empty initialized preset in location “000”. You can STORE this to any other location.
  
When executing this command, the editor writes a file to disk that contains a list of the parameter values of every block in the current preset. It’s a CSV file which means: Comma Separated Values. That’s a basic common database format that can be read or imported by any text editor, spreadsheet and database application.
+
=Managing presets=
  
=(Re)naming a preset=
+
==Preset titles==
  
'''Axe-Fx III:''' covered in Section 5 of the Owner's Manual.
+
'''Axe-Fx III, FM9 and FM3:'''
 +
* Covered in Section 5 of the [[Owners_Manuals|Owner's Manual]].
  
 
'''Axe-Fx II:'''
 
'''Axe-Fx II:'''
Line 133: Line 224:
 
When renaming a preset in the software editor, make sure to press ENTER in the name field, before saving the preset.
 
When renaming a preset in the software editor, make sure to press ENTER in the name field, before saving the preset.
  
=Setting levels and avoiding clipping=
+
==Manage Presets tool==
 +
 
 +
The tool [[Editors|Manage Presets]] in the editor lets you manage presets: copy, paste, delete, clear, import/export, etc.
 +
 
 +
==Preset numbering==
 +
 
 +
Preset numbering starts at 000. The Display Offset parameter in the [[Setup menu]] lets you change this to 001. This only affects offsets the display, meaning that it does not change which preset is actually loaded by a given footswitch or MIDI message.
 +
 
 +
==Export to disk==
 +
 
 +
To export a preset (or bank) to disk for archiving or sharing:
 +
 
 +
* Select Export in the editor.
 +
* use the editor's Manage Presets tool.
 +
* use Fractal-Bot.
 +
 
 +
The preset or bank will have the .syx filename extension.
 +
 
 +
Do not share IRs which are protected by a EULA, license, copyright, etc.
 +
 
 +
If the preset has [[Global blocks]] (Axe-Fx only), it's recommended to unlink these before exporting a preset. If not, the preset is only usable if you include your system data file.
 +
 
 +
==FC: save through a foot switch==
 +
 
 +
An edited preset can be saved during a performance through a foot switch on your FC. Assign the function Amp Level + Save with a value of 0 dB to a switch.
 +
 
 +
==Preset-Cab bundle==
 +
 
 +
A Preset-Cab bundle is a single file containing a preset and user IRs used by that preset. You can save and load Preset-Cab bundles with the editor. Bundles make it easier to share sounds and are easy to export and import.
 +
 
 +
'''''Warning: Do not share IRs which are protected by a EULA, license, copyright, and such.'''''
 +
 
 +
To export a bundle, use the <code>Preset > Export Preset-Cab Bundle</code> menu in the editor, which will display a dialog allowing us to include user IRs which can be saved by checking them.
 +
 
 +
To import a bundle, use the <code>Presets > Import Preset</code> menu in the editor, or drag-and-drop a bundle file onto the editor's main Preset display. This will display a dialog. This dialog unpacks a Preset-Cab Bundle and saves it ready-for-use to your device. A bundle contains one preset plus all of the IRs it depends on. To proceed, you must select a location to save each of the items within the Bundle. The preset will be updated automatically to refer to the location(s) you selected for the IRs.
 +
 
 +
Also see [[Cab_block#Preset-Cab_bundle|Cab block]] for more information.
 +
 
 +
==Swap presets==
 +
 
 +
The Axe-Fx III, FM9 and FM3 currently don't provide the possibility to swap presets on the hardware itself. Use the editor's <code>Tools > Manage Presets</code> tool.
 +
 
 +
==Share presets==
 +
 
 +
Besides the factory presets, there are presets and preset collections available from various sources.
 +
 
 +
The main sources for free presets are:
 +
* [http://axechange.fractalaudio.com Axe-Change]
 +
* [http://forum.fractalaudio.com Fractal Audio Forum]
 +
 
 +
There also are many commercial or donation-based offerings available, such as:
 +
 
 +
* [http://austinbuddy.com/ AustinBuddy]
 +
* [http://www.edosounds.com Edo]
 +
* [http://fremenpresets.com/ Fremen]
 +
* [http://www.marcofanton.it/ Marco Fanton]
 +
* [http://www.custompresets.com/ Moke]
 +
* [http://www.simeonharris.co.uk/Blocks/blocks.html Simeon]
 +
 
 +
==Delete presets==
 +
 
 +
The hardware does not provide a Clear or Delete/Erase tool for single presets. You can clear a preset slot by overwriting it with another empty preset.
 +
 
 +
Use the editor to clear a single or multiple presets.
 +
 
 +
The [[Setup menu]] on the Fx III, FM9 and FM3 allows deleting ALL presets. Be careful!
 +
 
 +
<blockquote>'''FRACTAL AUDIO QUOTES'''<HR>
 +
 
 +
<blockquote>
 +
 
 +
[https://forum.fractalaudio.com/threads/axe-fx-iii-firmware-23-02-release.199440/post-2485761]
 +
This erases the presets from non-volatile memory. The presets are in still in RAM until you reboot. This allows a small bit of safety in case you decide "oh, crap, I didn't want to erase THIS preset".
 +
</blockquote>
 +
</blockquote>
 +
 
 +
==Create a list of all presets==
 +
 
 +
In the software editor, select <code>Tools > Export as Text</code>. You can also choose to save a list of all presets including all scenes.
 +
 
 +
==Export preset settings to CSV==
 +
 
 +
This command is available as a menu command in AX8-Edit. In FX8-Edit, hold down <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>Shift</kbd> and click <code>Import</code> on Windows. On macOS use <kbd>Command</kbd>+<kbd>Alt</kbd>+<kbd>Shift</kbd>.
 +
 
 +
In the software editor, select <code>Export Preset as CSV</code> if available.
 +
 
 +
When executing this command, the editor writes a Comma-Separated-Values (CSV) file to disk that contains a list of the parameter values of each block in the current preset. CSV files are a basic common database format that can be read or imported by any text editor, spreadsheet and database application.
 +
 
 +
You can also use this feature to see if a preset has changed, by dumping a preset before and after editing.
 +
 
 +
==Preset size==
 +
 
 +
In rare cases a preset can get too large, having too many bytes. This is not the same as overloading the CPU. There's no warning or checking mechanism for this. If this happens, certain values won't get stored, or revert to zero upon recall. These are rare cases, which seem to occur mostly when the user uses a VERY large number of modifiers/controllers, or too many [[Global blocks]].
 +
 
 +
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
 +
<blockquote>
 +
[http://forum.fractalaudio.com/threads/why-512-presets.135057/page-2#post-1597873]
 +
A preset in the III is four times the size of a preset in the II.
 +
</blockquote>
 +
</blockquote>
 +
 
 +
==CPU usage==
 +
 
 +
Read [[CPU usage]] for more information.
 +
 
 +
=Preset levels=
 +
 
 +
==Level controls==
 +
 
 +
* The [[Input block]] has a Level control. It allows sending a lower or higher level into the effects grid which i.e. can be used to compensate for guitars with varying output levels.
 +
* Each preset has a Level control in the [[Output block]], and in the FX Loop block on the Axe-Fx II and AX8 only. Level in the Output block and FXL block is saved per scene.
 +
* All effect blocks have Level controls.
  
Controls:
+
There are systemwide level controls too.
* The Input block has a input level control. It allows sending a lower or higher level into the effects grid which i.e. can be used to compensate for guitars with varying output.
 
* Each preset has an output level control in the Output block (OUT1) and in the FX Loop block (OUT2, not on Axe-Fx III and FX8). Level in the Output block operates per scene (not on Axe-Fx III).
 
* All effect blocks have output level controls.
 
  
There are Systemwide level controls as well:
+
* The [[Global EQ]] provides gain controls for each output.
* The Global menu has gain controls for each output.
+
* OUT knobs on the top/front panel.
* OUT level knobs on the front panel of the Axe-Fx and AX8.
+
* Some processors let you switch the nominal output of the device between +4 and -10 dB in the [[Setup menu]].
  
When the red “Out1 Clip” LED blinks, the signal in the digital domain is too hot (loud). Severe clipping will cause digital audio distortion (crackle) which you want to avoid. This kind of clipping is not related to amp distortion. This digital distortion doesn't occur immediately when the Clip LED light, there's still some headroom left.
+
If the red “Out Clip” LED blinks, the signal in the digital domain is too hot (loud). Severe clipping will cause digital audio distortion (crackle) which you want to avoid. This kind of clipping is not related to amp distortion.
 +
 
 +
Read [[I/O_connectivity_and_levels#Main_output_level|Main output level]] for more information.
  
 
Important:
 
Important:
* The OUT level knobs on the front panel have no effect on clipping, because they control the analog circuitry and are placed after the digital-to-analog converter.
+
* The OUT level knobs on the top/front panel have no effect on output clipping, because they control the analog circuitry and are placed after the digital-to-analog converter.
* Clipping always occurs at the digital output stage.  
+
* Clipping always occurs at the digital-to-analog output stage.
 
* You can't clip an individual block.
 
* You can't clip an individual block.
 
* Digital clipping does NOT harm the unit.
 
* Digital clipping does NOT harm the unit.
* There is NO relationship between I/O > Input and output clipping. The input level parameters only controls the signal-to-noise ratio at the input stage and do NOT affect gain in the signal chain.  
+
* There is NO relationship between Input Level / Input Pad and output clipping. The Input Level parameters in the Setup menu only control the signal-to-noise ratio at the input stage and do NOT affect gain in the signal chain.
 +
 
 +
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
 +
<blockquote>
 +
[https://forum.fractalaudio.com/threads/meters-basically-useless-without-peak-db-readout.161912/post-1939615]
 +
It is floating point. A block can't clip (unless it's designed to).
 +
</blockquote>
 +
</blockquote>
 +
 
 +
You can reduce the digital signal level in any block by turning down its Level. The Amp block's Level or the Output block's Level controls are recommended.
 +
 
 +
If your unit's output is clipping heavily during a gig, you don't need to adjust the preset. Just enter the Global EQ and turn down Gain to solve this temporarily. Use the OUT knob on the top/front panel to compensate for loss of volume.
 +
 
 +
The latest generation of processors feature meters in the Layout menu which display the level of each effect block. This is extremely helpful for finding the cause of an interrupted signal.
  
You can reduce the digital signal level in any block by turning down its Level. Recommended are the Amp block's Level and Output block's Level controls. The Axe-Fx III lets you monitor block levels.
+
==Setting and matching levels==
  
If your unit's output is clipping heavily during a gig, you don't need to adjust the preset. Just enter the Global EQ and turn down Gain to solve this temporarily. Use the OUT knob on the front panel to compensate for loss of volume.
+
You probably want to match the output levels of all your presets. If you want to do this by ear, don't do it at low volume level and don't use headphones. The reason is, you may think that your high-gain preset needs to be turned down compared to your clean preset, but when playing live, that high-gain preset is compressed and has no peaks, while the clean is tone is very dynamic. Really, the only proven way to match levels by ear is to do this at gig level, and preferable with the band playing or using a backing track.
  
A front panel LED meter bridge provides instant visual status for the inputs and outputs. There also are meters in the GUI. The red LEDs on the front panel come on at -1 dBFS which is different than on previous hardware.
+
The recommended control to adjust the preset level is Output Level in the Amp block. The current editors provide a Preset Leveling tool for this task using <kbd>Control</kbd>+<kbd>L</kbd> on Windows or <kbd>Command</kbd>+<kbd>L</kbd> on macOS.
  
<blockquote>"Brief excursions into clipping may not light the clip LED long enough to be noticeable but can be audible. There is a hard limiter prior to D/A conversion that prevents wrap-around but if your preset is too hot you can hit that limiter which will sound nasty. As a rule of thumb, a preset shouldn't clip regardless of the pickups used. If you plug in a hotter guitar and the output clips, then your amp block output level is too high."</blockquote>
+
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
 +
<blockquote>
 +
[http://forum.fractalaudio.com/threads/so-many-volumes-options.55340/#post-698522]
 +
The amp block is always the place to set your volume. The Level control is repeated at several places in the amp block menus for convenience so you don't have to keep switching pages. The Level control has no affect on the tone.
  
=Leveling presets (VU meters)=
+
That quote above is only valid for non-MV amps (i.e. Fenders). The Master Volume (MV) DOES affect the tone. It sets the level into the power amp simulation. The Level control has no affect on the tone. For non-MV amps the recommended setting for MV is around 9.0. For MV amps, i.e a 5150, adjust the MV until the desired amount of power amp distortion is obtained. Most MV amps rely on preamp distortion and don't produce much power amp distortion. If you turn the MV up too high on them the tone will get muddy and flubby.
  
You probably want to match the (output) levels of all your presets. If you want to do this by ear, don't do it at low volume level and don't use headphones. The reason: you may think that your high-gain preset needs to be turned down compared to your clean preset. But when playing live, that high-gain preset is compressed (has no peaks) while the clean is tone is very dynamic. Really, the only proved way to match levels by ear is to do this at gig level, and preferable with the band playing or using a backing track.
+
Non-MV amps rely primarily on power amp distortion so you need the level into the power amp to be hot enough to push the power amp into distortion.
 +
</blockquote>
 +
</blockquote>
  
Another approach: measure and match preset levels using the VU meters. These show the relative loudness of the preset. To vied the VU meters:
+
Another approach is to measure and match the preset levels using the VU meters. These show the relative loudness of the preset.
* Axe-Fx III: zoom out from the layout grid.
 
* Axe-Fx II: Utility menu.
 
* AX8: page to the right.
 
These readouts can be used to help set preset levels to the same apparent volume. For convenience the level of the Amp blocks can be set from this page.
 
  
<blockquote>"ITU-R is a standard for loudness measurement. Broadcasters use it to monitor the apparent loudness of program material and comply with regulations, i.e. making sure commercials aren't louder than the programming. The measurement includes a simple head model and hearing perception model to give a fairly accurate indication of relative volume." [http://forum.fractalaudio.com/axe-fx-ii-wish-list/92953-level-matching-algorithm.html#post1117223 source] Be aware that the VU meter is offset by 20 dB, so when the meter reads 0 it’s actually -20 dB. This means that the "0" mark does not indicate clipping. This allows for sufficient headroom. When playing you'll see the meters bounce around. The meters give you a general idea of the loudness of the current preset, to get you in the ballpark. Try strumming the strings in a consistent way. Adjust the Amp level(s), aiming for an average level around 0 dB."</blockquote>
+
To view the VU meters:
  
A third method:
+
'''Axe-Fx III, FM9, FM3''' — Zoom out from the layout grid, or view the Output blocks.
# Select a preset with a really clean amp. Why? As Jay Mitchell explains: "Clean presets have the greatest crest factor (ratio of peak to average energy) and will therefore cause digital clipping at lower average levels (which determine your perception of volume) than gainier presets. For that reason, it is important to reference the levels of all other presets to that of the cleanest one set so that it never causes the (device) to clip with the Level control set to maximum. Once you have set this level you then need to set other presets to match it. Otherwise, your cleaner presets will either clip or be much softer than the others."
+
 
# Disable all effect blocks (especially compressors) except Amp and Cabinet.
+
'''Axe-Fx II''' — Use the Utility menu.
 +
 
 +
'''AX8''' — Page right.
 +
 
 +
These readouts can be used to help set preset levels to the same apparent volume. For convenience, the level of the Amp blocks can be set from this page.
 +
 
 +
Section 7 of the [[Owners_Manuals|Axe-Fx III Owner's Manual]] also discusses setting preset levels.
 +
 
 +
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
 +
 
 +
<blockquote>
 +
[https://forum.fractalaudio.com/threads/anyone-got-any-tips-for-settings-levels.150761/post-1793092]
 +
Don't be afraid to turn up the Amp level. The VU meters are calibrated such that there is 12 dB of headroom at the red line when the Output Level knob is at maximum.
 +
</blockquote>
 +
 
 +
<blockquote>
 +
[https://forum.fractalaudio.com/threads/using-the-vu-meter-to-balance-volume-among-presets.103173/#post-1235319]
 +
ITU-R is a standard for loudness measurement. Broadcasters use it to monitor the apparent loudness of program material and comply with regulations, i.e., making sure commercials aren't louder than the programming. The measurement includes a simple head model and hearing perception model to give a fairly accurate indication of relative volume.
 +
</blockquote>
 +
 
 +
<blockquote>
 +
Be aware that the VU meter is offset by 20 dB, so when the meter reads 0 it’s actually -20 dB. This means that the "0" mark does not indicate clipping. This allows for sufficient headroom. When playing you'll see the meters bounce around. The meters give you a general idea of the loudness of the current preset, to get you in the ballpark. Try strumming the strings in a consistent way. Adjust the Amp level(s), aiming for an average level around 0 dB.
 +
</blockquote>
 +
</blockquote>
 +
 
 +
And another method:
 +
# Select a preset with a really clean amp. Why? As Jay Mitchell explains: <q>Clean presets have the greatest crest factor (ratio of peak to average energy) and will therefore cause digital clipping at lower average levels (which determine your perception of volume) than gainier presets. For that reason, it is important to reference the levels of all other presets to that of the cleanest one set so that it never causes the (device) to clip with the Level control set to maximum. Once you have set this level you then need to set other presets to match it. Otherwise, your cleaner presets will either clip or be much softer than the others.</q>
 +
# Disable all effect blocks, especially compressors, except Amp and Cabinet.
 
# If you use a boost in the preset, enable it.
 
# If you use a boost in the preset, enable it.
 
# Select your loudest pickup and hit the strings hard.
 
# Select your loudest pickup and hit the strings hard.
Line 183: Line 433:
 
# If this method causes volume loss, compensate by turning up the overall volume level on the front panel or on your amplifier.
 
# If this method causes volume loss, compensate by turning up the overall volume level on the front panel or on your amplifier.
  
Section 7 of the Axe-Fx III Owner's Manual discusses setting preset levels.
+
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
 +
 
 +
<blockquote>
 +
[http://www.thegearpage.net/board/index.php?threads/gt1000-vs-helix-lt.1949412/page-2#post-26597522]
 +
All Fractal Audio products use floating-point processing. In fact the Axe-Fx III uses 64-bit floating-point in many places. It's impossible to clip internally. The AX-8 and Axe-Fx II use 40-bit in many places and are also impossible to clip internally. If you are clipping the output, which is the final fixed-point signal to the converters (all audio converters use fixed-point), then your internal signals are far too high. If you use the VU meters and set your output to 0 dB you are guaranteed 12 dB of headroom at the converters with the output level knob all the way up. I've never witnessed a palm mute that was more than a few dB hotter than nominal.
 +
 
 +
Go into the Layout menu and press the Zoom hotkey. This will display VU meters for the two main outputs. Adjust the level of the Amp block (using the Block Level knob with the Amp block selected) so that the signal hovers around the 0 dB marker. If you do this it's impossible to clip the outputs.
 +
 
 +
The factory presets are all adjusted for roughly 0 dB on the VU meters. Even with the output level knob all the way up I never get anywhere even close to clipping.
 +
 
 +
We could've taken a conservative approach and built in a lot of headroom so that clipping the converters was impossible but then you lose dynamic range. The approach taken optimizes the dynamic range of the converters (so you aren't wasting bits) thereby ensuring maximum fidelity and lowest noise. It does require that the user adjust their presets correctly to avoid overflowing the converters but the VU meters make this task trivially easy.
 +
</blockquote>
 +
 
 +
<blockquote>
 +
[https://forum.fractalaudio.com/threads/heavy-cleans.181074/post-2217439]
 +
The leveling tool will often result in clean tones not sounding as loud as distorted tones due to the greater dynamic range.
 +
</blockquote>
 +
</blockquote>
  
=Use VOL INC and VOL DEC to adjust and store the preset level while playing=
+
==Vol Inc and Vol Dec==
  
Volume Inc(rement) and Volume Dec(rement) present a convenient way to adjust preset levels on the fly (without manual editing). These commands let you adjust the preset level in small steps while playing. Adjustments are saved automatically.
+
Volume Inc(rement) and Volume Dec(rement) present a convenient way to adjust preset levels on the fly (without manual editing). These commands let you adjust the preset level in steps of 1 dB while playing. Adjustments are saved automatically.
  
To make this work, assign these commands to switches on your foot controller, using their MIDI CCs. The MFC-101 has dedicated commands for this purpose.
+
To make this work, assign these commands to switches on your foot controller, using their MIDI CCs. The MFC-101 MIDI foot controller (discontinued) and [[FC-6 and FC-12 foot controllers]] have dedicated commands for this purpose.
  
Notes:
+
Notes:nued
 
* Make sure that a single press sends just one command, not a double one.
 
* Make sure that a single press sends just one command, not a double one.
* VOL INC and VOL DEC only affect the signal through Output 1, not Output 2, unless Echo Output 1 is set to Output 2 in I/O AND the preset doesn't contain a FX Loop block (AX8 or Axe-Fx II) or a corresponding Output block (Axe-Fx III).
+
* Axe-Fx II and AX8: Vol Inc and Vol Dec only affect the signal through Output 1, not Output 2, unless Echo Output 1 is set to Output 2 in the Setup menu AND the preset doesn't contain an FX Loop block (AX8 or Axe-Fx II).
* They work per scene (not on Axe-Fx III).
+
* Axe-Fx III, FM9, and FM3: there are separate Vol Inc/Vol dec commands for Outputs 1 and 2.
 +
* They work per scene.
  
Note that other unsaved changes to the preset will get saved too, when VOL INC or VOL DEC is triggered.
+
Note that other unsaved changes to the preset will get saved too when Vol Inc or Vol Dec is triggered.
  
=Boosting the output level temporarily=
+
The [[FC-6 and FC-12 foot controllers]], FM3 and FM9 provide an alternative for Vol Inc and Vol Dec: adjust Amp Level in steps. This also includes a quick way to save a preset in its current state through a footswitch (without increasing or decreasing the level).
  
Methods to boost the signal level, i.e. for leads:
+
==Boost the output level==
* Add a Filter block at the end of the signal chain, set to "Null" with Level at e.g. 3 dB, and its Bypass assigned to a switch.
 
* Use a PEQ or GEQ block with its Level turned up and assign the block's Bypass to a switch.
 
* Use a pedal or switch to turn up the Input Drive, or Input Trim, or Master Volume, of the Amp block.
 
* Boost the level at the input of the grid, using the Level parameter in the GTE/IN menu.
 
* Create a global "Boost" switch without having to modify each preset (source: M@) as follows. Set the CC of an IA switch on the floor controller to OUT1 VOLUME. Set the OFF value to (for example) "111" (unboosted level) and set the ON value to "127" (boosted level). If you're using Output 2 as well, don't forget to add a second CC for OUT2 VOLUME, or assign OUT2 to the same CC as OUT1.
 
* Use a scene for increased output level.
 
* Use an expression pedal.
 
* Configure a block for X/Y switching or channels.
 
* [http://www.youtube.com/watch?v=Db8Jlltmdus Tutorial by AxeFxTutorials.]
 
* [http://www.youtube.com/watch?v=G7udaPFSTqo Tutorial by AustinBuddy.]
 
* [http://forum.fractalaudio.com/threads/tip-adjustable-lead-volume.123607 Connect an external volume knob through an external controller.]
 
  
=Preset guidelines=
+
Methods to boost the signal level, i.e., for leads:
  
Here's a checklist to verify your presets' consistency:
+
* FM3, FM9, FX3, All GEN1 + GEN2 devices:
* Stick to the same grid layout/routing if possible, to simplify viewing and editing, and to increase preset switching speed.
+
**Add a Filter block at the end of the signal chain, set to <q>Null</q> with Level at e.g. 3 dB, and its Bypass assigned to a switch.
* Re-use effect blocks with preferred settings and levels, through Global Blocks (Axe-Fx II), or saved/recalled effects from the editor's Block Library.
+
** Use a PEQ or GEQ block with its Level turned up and assign the block's Bypass to a switch.
* Assign external controllers in a consistent way.
+
** Use a pedal or switch to turn up Gain the Amp block, or Input Trim, or Master Volume, of the Amp block.
* Even if delay/reverb won't be used in a preset, consider inserting a bypassed Delay/Reverb block to enable spillover.
+
** Boost the level at the input of the grid using the Level parameter in the GTE/IN menu.
* Verify that effects before Amp and Drive blocks are not set to stereo.
+
* FM3, FM9, FX3: Use a scene for increased output level.
* Be aware that certain effect blocks sum the signal to mono (Amp, Drive, mono Cab).
+
* MFC-101: Create a global <q>Boost</q> switch without having to modify each preset (source: M@) as follows.
* Check your settings (I/O, and blocks) for correct mono and stereo operation to prevent phase cancellation.
+
** Set the CC of an IA switch on the floor controller to OUT1 VOLUME.
* Make sure that the blocks maintain unity gain where needed, in engaged and bypassed states.
+
** Set the OFF value to <q>111</q> for example, for the unboosted level, and set the ON value to <q>127</q> for the boosted level.
* Set Mix, Level and Bypass parameters correctly when placing effects in parallel rows.
+
** If you're using Output 2 as well, don't forget to add a second CC for OUT2 VOLUME, or assign OUT2 to the same CC as OUT1.  
* Make sure that the overall preset level matches that of other presets and does not clip when engaging a volume boost, Wah, etc.
+
* All devices: Use an expression pedal.
* Check the preset noise gate settings. Turn it off when not needed to save CPU.
+
* All GEN1 + GEN2 devices: Assign a modifier to Level in the Cab block.
* Select the desired impedance in the input instrument block (not on AX8).
+
* X/Y: AX8, FX8. Scenes: FM3, FM9, III: Configure a block for X/Y switching or channels.
* Use a consistent way to boost the level for leads.
 
* Make sure that effect blocks are set to the correct X/Y state or channel in each scene.
 
* Be aware that the current scene when saving an Axe-Fx III preset, is the default scene when loading that preset.  
 
* If Tempo is set to “preset”, set the preset's tempo settings.
 
* When using one Amp block on the Axe-Fx: use AMP 1, never AMP 2.
 
* Make sure that CPU usage stays below 90% on the Axe-Fx II and lower than that on the FX8 and AX8. Note that CPU usage can vary, depending on the X/Y state or channel of effect blocks.
 
* Mute scenes which are not being used.
 
* Use Feedback Send/Return (Axe-Fx II and III only) to extend a routing on multiple rows.
 
* Use a consistent naming scheme for presets.
 
* Use a consistent naming scheme for scenes (Axe-Fx III only).
 
* Choose a preset title that fits on the hardware display.  
 
* AX8 and FX8: assign switches to effects in the preset.  
 
  
[[image:Iii grid.jpg|400px]]
+
For more information see:
 +
* AustinBuddy's <q>[http://www.youtube.com/watch?v=G7udaPFSTqo How to Level and Gain stage your AX8 and AXE-FX Presets]</q> tutorial.
 +
* The forum's <q>[http://forum.fractalaudio.com/threads/tip-adjustable-lead-volume.123607 Tip: Adjustable Lead Volume]</q> discussion.
  
=Effects list=
+
=Routing=
  
Read this: [[Effects list]].
 
  
The Axe-Fx II and III Owners Manuals also contain a block inventory with short descriptions.
+
==Series and parallel routing==
 +
 
 +
You can put effect blocks in series (in a single row) or parallel.
  
=Effects levels=
+
'''Axe-Fx III''' – Extensive routing possibilities, using the 6x14 grid.
  
==Block meters on the Axe-Fx III==
+
'''FM9''' – Extensive routing possibilities, using the 6x14 grid.
  
The Axe-Fx III features meters which display the level of each effect block.
+
'''FM3''' – Extensive routing possibilities, using the 4x12 grid.
  
[[image:Iii grid meters.jpg|link=|400px]]
+
'''VP4''' – An effect can be placed in parallel with the previous effect..
  
==Global adjustments of effects levels==
+
'''Axe-Fx II and AX8''' – Extensive routing possibilities, using the 4x12 grid.
  
The Effects (FX) Mix parameter in the Global menu lets you control the overall wetness of effect blocks with a Global Mix parameter. There's a separate global mix parameter for reverb: Rev Mix (reverb is also affected by the Effects Mix parameter). The global parameters simply multiply the preset mix value.
+
'''FX8''' – Single row and the possibility to place an effect in parallel with another effect. You can adjust the placement of effect blocks in the preset configuration (Config page). Examples are provided in the [[Owners_Manuals|FX8 manual]]. The first PRE and first POST effect are always in series.
  
<blockquote>"Global Reverb and Effects Mix are relative. If set to 0% the mix is set by the preset. If set to, say, -10% the mix would be 10% less than the preset mix.” [http://forum.fractalaudio.com/axe-fx-ii-discussion/94812-global-reverb-all-presets.html#post1135617 source] </blockquote>
+
Parallel routing is a common method in traditional analog rigs to avoid loss of tone. There's no need to use parallel routing to prevent loss of tone quality when using Fractal Audio gear. But parallel routing makes it possible to have e.g. independent delay and reverb paths, or lets you place effects after a specific effect, not affecting the main signal. Also, on the Axe-Fx II, III and AX8, it allows you to put more effects in a preset, overcoming the limit of the maximum number of columns.
  
Note that adjusting this control may not have the desired effect when the Reverb block is placed in a parallel row with its Mix parameter set to 100%.
+
You don’t want to place <q>100% wet</q> effects in a parallel path, such as Tremolo or Compressor, because dry signal will still be going through the main path and affect the effect.
  
=Routing=
+
If an effect is placed in parallel, bypassing that effect may pass <q>direct</q> signal, which, when merged with the main signal, increases the overall signal level. To prevent this, select a suitable Bypass Mode (not: THRU). MUTE OUT and MUTE FX OUT will kill effect tails, while MUTE IN and MUTE FX IN preserve tails.
  
==Entering and leaving the grid==
+
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
 +
<blockquote>
 +
[https://forum.fractalaudio.com/threads/axe-fx-iii-firmware-25-00-release.203482/page-11#post-2546236]
 +
If using Kill Dry you typically wouldn't use THRU. Use any of the other modes. If you want the tails use Mute Fx In or Mute In.
 +
</blockquote>
 +
</blockquote>
  
* [[Input block]].
+
'''Firmware 25.00 and later for the Axe-Fx III (and corresponding FM3 and FM9 firmware)'''
* [[Output block]].
 
  
==Series and parallel routing==
+
Current firmware makes it easy to configure effects for operation in parallel paths. The Kill Dry parameter mutes the dry signal, and lets you keep using the Mix parameter to dial in the desired effects level. This also provides support for the Reverb and Effects Mix parameter in the Global menu. You still need to set the correct Bypass Mode to prevent an undesirable level boost when bypassing the effect, see above.
  
You can put effect blocks in series (in a single row) or parallel.
+
Release notes: [https://forum.fractalaudio.com/threads/axe-fx-iii-firmware-25-00-release.203482/#post-2545408]
  
* '''Axe-Fx III''': extensive routing possibilities, using the 6x14 grid.
+
<blockquote>
* '''Axe-Fx II and AX8''': extensive routing possibilities, using the 4x12 grid.
+
<HR>
* '''FX8''': a single row and the possibility to place an effect in parallel with another effect. You can adjust the placement of effect blocks in the preset configuration (Config page). Examples are provided in the FX8 manual. The first PRE and first POST effect are always series.
+
<blockquote>
 +
Added “Kill Dry” control to Delay, Multitap Delay, Pitch, Plex and Reverb blocks. When set to ON the dry signal is muted. This simplifies routing these blocks in parallel. When using these blocks in parallel the user can turn Kill Dry on and set the wet level using the Mix control, leaving the Level control at 0dB. This also has the advantage that the wet level is controlled by the global Reverb/Effects Mix, if desired.
  
Parallel routing is a common method in traditional analog rigs to avoid loss of tone. However, there's no need to use parallel routing to prevent loss of tone quality when using Fractal Audio gear. Parallel routing makes it possibe to have, i.e., independent delay and reverb paths. Or you can use it to put effects after a specific effect only, not affecting the main signal. Also, on the Axe-Fx II, III and AX8 it allows you to put more effects in a preset, overcoming the limit of columns.
+
</blockquote>
 +
</blockquote>
  
You don’t want to place "100% wet” effects in a parallel path, such as Tremolo or Compressor, because dry signal will still be going through the main path and affect the effect.
+
Kill Dry has also been added to the Megatap Delay block.
  
More information: [http://forum.fractalaudio.com/axe-fx-ii-discussion/49482-wicked-wiki-12-parallel-paths.html discussion], [http://forum.fractalaudio.com/axe-fx-ii-discussion/70249-delay-block-lowering-overall-output-level.html discussion], [http://forum.fractalaudio.com/axe-fx-ii-discussion/71026-why-do-parallel-effects-if-its-all-digital-anyway.html discussion.]
+
'''Before firmware 25.00 for the Axe-Fx III:'''
  
When running an effect in series, using its Mix parameter (if available) may affect the level of the dry level too. This is not the case with effects in a parallel row, when Mix is set to 100% (fully "wet") and using Level or Input Gain to dial in the desired effects level. So: when using effects in parallel, always set Mix at 100%, and use Level to dial in the desired amount of effect. With effects featuring an Input Gain parameter, keep Level at 0 dB and use Input Gain to dial in the desired amount of effect. Also, setting Mix at 100% avoids creating "double" direct signal paths, which result in undesirable increase of volume.
+
When running an effect in series, using its Mix parameter (if available) may affect the level of the dry level too. This is not the case with effects in a parallel row when Mix is set to 100% (fully <q>wet</q>) and using Level or Input Gain to dial in the desired effects level. So, when using effects in parallel, set Mix at 100% and use Level to dial in the desired amount of effect. With effects featuring an Input Gain parameter, you can keep Level at 0 and use Input Gain (which controls the level going into the block) to dial in the desired amount of effect. Also, setting Mix at 100% avoids creating <q>double</q> direct signal paths, which would result in undesirable increase of volume.
  
If an effect is placed in parallel, bypassing that effect may pass "direct" signal, which, when merged with the main signal, may increase the overall signal level. To prevent this, select a suitable Bypass Mode: Mute Out or Mute In. Do not use Mix 0% / Thru Mute FX In / Mute FX Out.
+
See <q>[https://forum.fractalaudio.com/threads/wicked-wiki-12-parallel-paths.49482 WICKED WIKI 12: Parallel Paths]</q> and <q>[http://forum.fractalaudio.com/posts/1535651 What is the "exact?" db of gain increase on muted parallel effects?]</q> in the forum for more information.
  
The FX8 automates all this, using "smart" controls. Mix, Level and Bypass are automatically adjusted when moving an effect from series to parallel, and vice versa.
+
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
  
<blockquote>Bakerman: "Decibels use a logarithmic scale. You need to double the voltage (paths of identical signal) to see a ~6 dB increase. 1 to 2 is doubling. 2 to 4 is doubling. 2 to 3 (voltage gain of 1.5) is only a ~3.5 dB increase." [http://forum.fractalaudio.com/threads/signal-levels-is-this-what-is-expected.107325/#post-1284204 source]</blockquote>
+
<blockquote>
 +
[http://forum.fractalaudio.com/threads/signal-levels-is-this-what-is-expected.107325/#post-1284542]
 +
Don't think in terms of dB. Assume you are putting 1V in (for convenience). If you add two rows you get 2V out. That's a 6 dB increase. If you add three rows you get 3V out. That's a 9.5 dB increase. If you add four rows you get 4V. That's 12 dB.
 +
</blockquote>
  
<blockquote>"Don't think in terms of dB. Assume you are putting 1V in (for convenience). If you add two rows you get 2V out. That's a 6 dB increase. If you add three rows you get 3V out. That's a 9.5 dB increase. If you add four rows you get 4V. That's 12 dB." [http://forum.fractalaudio.com/threads/signal-levels-is-this-what-is-expected.107325/#post-1284542 source]</blockquote>
+
'''OTHER QUOTES'''
 +
<HR>
 +
Forum member Bakerman:
 +
<blockquote>
 +
[http://forum.fractalaudio.com/threads/signal-levels-is-this-what-is-expected.107325/#post-1284204]:
 +
Decibels use a logarithmic scale. You need to double the voltage (paths of identical signal) to see a ~6 dB increase. 1 to 2 is doubling. 2 to 4 is doubling. 2 to 3 (voltage gain of 1.5) is only a ~3.5 dB increase.
 +
</blockquote>
  
[http://forum.fractalaudio.com/posts/1535651 More information.]
+
Forum member GM Arts:
 +
<blockquote>
 +
Here's a bit of trivia to cover the comments we often see along the lines of: when I combine two blocks in parallel into a single block, it gets louder... The two signals sum, so it's necessary to reduce the output levels of the two blocks so they combine without volume boost. For an equal mix, each block must be set to -6dB. What's not so apparent is what levels to use for unequal mixes, so here they are. This applies to combining two blocks that each have the same level into a single block without volume change.
  
M@:
+
<table style="text-align:right;">
<blockquote>"When turning up Mix in a block, the dry signal decreases. The table below shows wet/dry dB levels at various settings for blocks like Reverb, Pitch, etc. which do NOT use a constant power algorithm (like DRIVE). The Delay also uses a different method. In a rig where unity gain matters, these numbers are used to know how much to adjust Level for a given Mix setting."</blockquote>
+
<tr><td>-6</td><td>-6dB</td></tr>
 +
<tr><td>-5.5</td><td>-6.6dB</td></tr>
 +
<tr><td>-5</td><td>-7.2dB</td></tr>
 +
<tr><td>-4.5</td><td>-7.9dB</td></tr>
 +
<tr><td>-4</td><td>-8.7dB</td></tr>
 +
<tr><td>-3.5</td><td>-9.6dB</td></tr>
 +
<tr><td>-3</td><td>-10.7dB</td></tr>
 +
<tr><td>-2.5</td><td>-12dB</td></tr>
 +
<tr><td>-2</td><td>-13.7dB</td></tr>
 +
<tr><td>-1.5</td><td>-16dB</td></tr>
 +
<tr><td>-1</td><td>-19.3dB</td></tr>
 +
<tr><td>-0.5</td><td>-25dB</td></tr>
 +
</table>
 +
</blockquote>
  
<code>
+
[https://forum.fractalaudio.com/threads/why-does-a-side-reverb-block-at-the-end-of-a-chain-right-before-the-output-so-different-great.160239/page-2#post-1918680 Forum member DLC86]:
MIX SETTING / WET LEVEL / DRY LEVEL / WET/DRY DIFF<BR>
+
<blockquote>
0 / -∞ / 0.00 / -∞<BR>
+
When the mix knob is set at 50%:
5 / -26.02 / -0.45 / 25.58<BR>
 
10 / -20.00 / -0.92 / 19.08<BR>
 
15 / -16.48 / -1.41 / 15.07<BR>
 
20 / -13.98 / -1.94 / 12.04<BR>
 
25 / -12.04 / -2.50 / 9.54<BR>
 
30 / -10.46 / -3.10 / 7.36<BR>
 
35 / -9.12 / -3.74 / 5.38<BR>
 
40 / -7.96 / -4.44 / 3.52<BR>
 
45 / -6.94 / -5.19 / 1.74<BR>
 
50 / -6.02 / -6.02 / 0.00<BR>
 
55 / -5.19 / -6.94 / 1.74<BR>
 
60 / -4.44 / -7.96 / 3.52<BR>
 
65 / -3.74 / -9.12 / 5.38<BR>
 
70 / -3.10 / -10.46 / 7.36<BR>
 
75 / -2.50 / -12.04 / 9.54<BR>
 
80 / -1.94 / -13.98 / 12.04<BR>
 
85 / -1.41 / -16.48 / 15.07<BR>
 
90 / -0.92 / -20.00 / 9.08<BR>
 
95 / -0.45 / -26.02 / 25.58<BR>
 
100 / 0.00 / -∞ / ∞</code>
 
  
The formula for an exact calculator is:
+
Chorus: -3 dB<BR>
* DRY LEVEL=(LOG((100-MIX)/100))*20
+
Compressor: -6 dB<BR>
* WET LEVEL =(LOG(MIX/100))*20.
+
Delay: 0 dB<BR>
 +
Drive: -6 dB<BR>
 +
Flanger: -3 dB<BR>
 +
Formant: -6 dB<BR>
 +
Megatap Delay: -6 dB<BR>
 +
Multiband Comp: -6 dB<BR>
 +
Multitap Delay: -3 dB<BR>
 +
Phaser: -3 dB<BR>
 +
Pitch: -6 dB<BR>
 +
Plex Delay: -6 dB<BR>
 +
Reverb: -3 dB<BR>
 +
Ring Modulator: -6 dB<BR>
 +
Rotary: -3 dB<BR>
 +
Synth: -6 dB<BR>
 +
Ten-Tap Delay: -3 dB<BR>
 +
Vocoder: 0 dB
  
<blockquote>GM Arts: "Here's a bit of trivia to cover the comments we often see along the lines of: when I combine two blocks in parallel into a single block, it gets louder... The two signals sum, so it's necessary to reduce the output levels of the two blocks so they combine without volume boost. For an equal mix, each block must be set to -6dB. What's not so apparent is what levels to use for unequal mixes, so here they are. This applies to combining two blocks that each have the same level into a single block without volume change." [http://forum.fractalaudio.com/axe-edit-general-discussion/42921-block-summing.html source]
+
</blockquote>
 +
</blockquote>
  
<code>-6dB&nbsp;&nbsp;&nbsp;&nbsp;-6dB<BR>
+
==PRE and POST routing==
-5.5dB&nbsp;&nbsp;-6.6dB<BR>
 
-5dB&nbsp;&nbsp;&nbsp;&nbsp;-7.2dB<BR>
 
-4.5dB&nbsp;&nbsp;-7.9dB<BR>
 
-4dB&nbsp;&nbsp;&nbsp;&nbsp;-8.7dB<BR>
 
-3.5dB&nbsp;&nbsp;-9.6dB<BR>
 
-3dB&nbsp;&nbsp;&nbsp;&nbsp;-10.7dB<BR>
 
-2.5dB&nbsp;&nbsp;-12dB<BR>
 
-2dB&nbsp;&nbsp;&nbsp;&nbsp;-13.7dB<BR>
 
-1.5dB&nbsp;&nbsp;-16dB<BR>
 
-1dB&nbsp;&nbsp;&nbsp;&nbsp;-19.3dB<BR>
 
-0.5dB&nbsp;&nbsp;-25dB</code></blockquote>
 
  
[http://forum.fractalaudio.com/axe-fx-ii-discussion/76501-taming-monster-series-parallel-routing.html Scott Peterson shows how to build a parallel path.]
+
<q>PRE</q> and <q>POST</q> refer to the position of effects before or after the Amp block and/or Cab block.
  
[http://www.youtube.com/watch?v=CZ-XKJ3BVpA Leon Todd's tutorial.]
+
See <q>[[Cab block]]</q> for more information.
  
==PRE and POST routing==
+
<blockquote>
 +
'''[[Owners_Manuals|FX8 Owner's manual]]:'''
 +
<HR>
  
Owner's manuals:
+
<blockquote>
 +
Sonically speaking, the main reason to care about PRE vs. POST is that a given effect will sound different when placed BEFORE or AFTER your amp’s preamp—the place where distortion occurs. How does this difference sound? If you’ve ever switched the sequence of traditional DRIVE and WAH pedals, you’ve heard an excellent example. In the case of wah before overdrive, the resonant filter of the wah “excites” the overdrive in a cool way while still retaining a natural overall tone. When the wah follows distortion, you might hear a more dramatic filtered sweep—with heavy distortion it can get almost synth-like—which might be considered less “classic.” It’s not surprising then that Wah would traditionally be a run as a “PRE” effect between guitar and amp. The amp’s distortion follows the wah effect. Many other effects fall in this same category. A different example is found in overdrive with reverb and delay. In the natural world, reverb and echo occur because of open spaces around your guitar amp – like a club or concert hall. These effects would therefore NOT be heard before a distorted amp, but after it. Recording studios often add these kinds of effects at the console—after the mic has picked up the distorted sound from the guitar amp. If you wanted to simulate this natural sounding reverb or delay these effects would likely be run “POST.” This is not to say that delay or reverb before distortion is a “no-no.” Many “legendary” tones came from echo units in front of an amp—but this effect is very different from “POST” delay—not only tonally, but also in terms of dynamics. The good news is that the FX8 allows you to experiment easily and find what combinations of pre- and post-effects work best for you. Creativity begins where tradition ends.
 +
</blockquote>
 +
</blockquote>
  
<blockquote>"Sonically speaking, the main reason to care about PRE vs. POST is that a given effect will sound different when placed BEFORE or AFTER your amp’s preamp—the place where distortion occurs. How does this difference sound? If you’ve ever switched the sequence of traditional DRIVE and WAH pedals, you’ve heard an excellent example. In the case of wah before overdrive, the resonant filter of the wah “excites” the overdrive in a cool way while still retaining a natural overall tone. When the wah follows distortion, you might hear a more dramatic filtered sweep—with heavy distortion it can get almost synth-like—which might be considered less “classic.” It’s not surprising then that Wah would traditionally be a run as a “PRE” effect between guitar and amp. The amp’s distortion follows the wah effect. Many other effects fall in this same category. A different example is found in overdrive with reverb and delay. In the natural world, reverb and echo occur because of open spaces around your guitar amp – like a club or concert hall. These effects would therefore NOT be heard before a distorted amp, but after it. Recording studios often add these kinds of effects at the console—after the mic has picked up the distorted sound from the guitar amp. If you wanted to simulate this natural sounding reverb or delay these effects would likely be run “POST.” This is not to say that delay or reverb before distortion is a “no-no.” Many “legendary” tones came from echo units in front of an amp—but this effect is very different from “POST” delay—not only tonally, but also in terms of dynamics. The good news is that the FX8 allows you to experiment easily and find what combinations of pre- and post-effects work best for you. Creativity begins where tradition ends."</blockquote>
+
The FX8 is designed for PRE and POST hardware routing. There are 3 supported ways:
  
==PRE and POST routing in the FX8==
+
'''PRE''' — Effects between guitar and Amp.
  
Read the manual. It has diagrams. There are 3 supported ways:
+
'''POST''' — Effects after the Amp. I.e. in a real amp's effects loop, or added in a studio.
  
* '''PRE''': effects between guitar and Amp.
+
'''Four Cable Method (4CM)''' — Combination of PRE and POST.
* '''POST''': effects after the Amp. I.e. in a real amp's effects loop, or added in a studio.
 
* '''Four Cable Method (4CM)''': combination of PRE and POST.
 
  
 
PRE and POST chains depend on the way the FX8 is connected and is configured on the preset's CFG page.
 
PRE and POST chains depend on the way the FX8 is connected and is configured on the preset's CFG page.
The PRE/POST effects configuration per preset is indicated at the top of the screen.
+
The PRE/POST effects configuration per preset is indicated at the top of the screen:
 +
 
 +
'''8/0''' — All blocks are PRE.
 +
 
 +
'''0/8''' — All blocks are POST.
 +
 
 +
Any other value indicates a mix of PRE and POST.
 +
 
 +
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
 +
 
 +
<blockquote>
 +
[http://forum.fractalaudio.com/posts/1224745]
 +
The paradigm for the FX-8 is that if you put the typical effects in the "Post" section then the level out of the Post section is the same as the level in. Therefore your effects loop is running at unity gain and the volume won't change if you bypass all the effects.
 +
</blockquote>
 +
</blockquote>
 +
 
 +
The [[Owners Manuals|FX8 manual]] contains diagrams.
 +
 
 +
==Bypass mode==
 +
 
 +
; MUTE IN :When the block is bypassed, its inputs are muted, silencing the both wet and dry but allowing effect <q>tails</q> to ring out or <q>spill over</q>. Use this (or MUTE FX IN) for time-based effects in parallel.
 +
 
 +
; MUTE OUT :When the block is bypassed, all audio is totally silenced at the outputs. Effect tails are silenced immediately, but the input is still <q>listening</q> so tails may be heard when you engage the effect.
 +
 
 +
; MUTE FX IN :When the block is bypassed, the inputs of its internal processor are muted, but the dry is unaffected. This allows effect <q>tails</q> to ring. LEVEL and BALANCE and MIX controls continue to operate when the block is bypassed. Use this for time-based effects in series when you want spillover.
 +
 
 +
; MUTE FX OUT :When the block is bypassed, the outputs of its internal processor are pulled, but dry signal is totally unaffected. With this setting, signals can enter a reverb or delay before it is engaged. LEVEL and BALANCE and MIX controls continue to operate when the block is bypassed.
 +
 
 +
; MUTE :When the block is bypassed, both wet and dry are totally silenced.
 +
 
 +
; THRU :When bypassed, the block is completely disengaged. None of its parameters have any effect on the sound; it behaves exactly as if it were never there in the first place.
  
* '''8/0''': all blocks are PRE.
+
The settings are explained through diagrams in the [[Owners_Manuals|Owner's Manual]]:
* '''0/8''': all blocks are POST.
 
* Everything indicates a mix of PRE and POST.
 
  
<blockquote>"The paradigm for the FX-8 is that if you put the typical effects in the "Post" section then the level out of the Post section is the same as the level in. Therefore your effects loop is running at unity gain and the volume won't change if you bypass all the effects." [http://forum.fractalaudio.com/fx8-discussion/102189-first-rehearsal-fx8-few-issues.html#post1224745 source]</blockquote>
+
[[image:Bypass modes.png|500px]]
  
==Effects before or after the Cab block==
+
To set a block's Bypass state in all scenes of a preset, use the editor.
  
Read this: [[Cab block and IRs]].
+
<blockquote>
 +
'''PREVIOUS GENERATIONS'''
 +
<HR>
  
==More routing tools==
+
<blockquote>
 +
[http://forum.fractalaudio.com/threads/strange-the-more-bypassed-effects-the-less-gain-and-real-amp-feeling.88053/#post-1064563]
 +
A bypassed block does nothing more than copy the input to the output. Any perceived changes in sound are just that, perceived.
 +
</blockquote>
  
* [[Multiplexer block]].
+
<blockquote>
* [[Feedback Send/Return block]].
+
[https://forum.fractalaudio.com/threads/silence-between-scene-switching-channel-switching.139604/#post-1655468]
* [[Mixer block]].
+
FX bypasses are done as fades but much shorter that 500 ms. More like 20 ms.
* [[FX Loop block]].
+
</blockquote>
 +
</blockquote>
  
==Mono and stereo signal==
+
The Bypass Mode parameter on the Axe-Fx II, AX8 and FX8 can be attached to a controller. The controller will then control the block's state: engaged or bypassed. You can also use the Setup menu to switch the effect through the corresponding INIT VALUE parameter. The Axe-Fx III, FM9 and FM3 provide a dedicated Bypass parameter for this purpose.
  
Read this: [[Mono and stereo]].
+
The engaged/bypass state of an effect block can be different per scene when not connected to a controller. Read [[Scenes]] for more information.
  
=Edit parameters=
+
When switching between two Amp blocks in parallel rows, make sure to set their Bypass Mode to Mute, to prevent bleed-through of dry signal from the bypassed Amp block.
  
==Resetting an effect block==
+
Bypassing a block does NOT lower CPU usage. CPU usage only decreases when removing the block from the grid.
  
* '''Axe-Fx III''': press the Reset soft button. This resets the current channel only.
+
In firmware 21.x and later for the Axe-Fx III, and corresponding FM3 and FM9 firmware, the bypass design has been changed for blocks whose mix is <q>hard-coded</q> at 100%, for example, Wah, Filter, EQ, Tremolo. These blocks now bypass and engage with a gentle fade, smoothening the transition.
* '''Axe-Fx II''': click BYPASS twice (not EFF.BYPASS) or press-and-hold it.
 
* '''FX8''': click ENTER twice.
 
* '''AX8''': click SHIFT, then press EDIT twice.
 
Or use the software editor to initialize the block.
 
  
[[Amp_block#Resetting_AMP_block_parameters: resetting the parameters |More information about defaulting the parameters in an Amp block.]]
+
==Mono or stereo==
 +
 
 +
Read <q>[[Mono and stereo]]</q> for more information.
 +
 
 +
==Routing tools==
 +
 
 +
See these sections for more information:
 +
 
 +
* [[Multiplexer block]]
 +
* [[Send and Return blocks]]
 +
* [[Mixer block]]
 +
* [[Volume/Panner block]]
 +
 
 +
=Editing parameters=
 +
 
 +
==Reset a block==
 +
 
 +
'''Axe-Fx III''' and '''FM9''' and '''FM3''' — Press the Reset soft button. This resets the current channel only.
 +
 
 +
'''Axe-Fx II''' — Click BYPASS twice (not EFF.BYPASS) or press-and-hold it.
 +
 
 +
'''FX8''' — Click ENTER twice.
 +
 
 +
'''AX8''' — Click SHIFT, then press EDIT twice.
 +
 
 +
Or use the editor to initialize the entire block, or just the channel.
 +
 
 +
Visit the [[Amp block]] page for more information about defaulting the parameters in an Amp block.
  
 
==Recall Effect==
 
==Recall Effect==
  
"Recall Effect" lets you copy the parameters of an effect block from another preset into the current preset. The Axe-Fx II, FX8 and AX8. have this feature, the Axe-Fx III does not.
+
The Recall Effect function lets you copy the parameters of an effect block from another preset into the current preset. The Axe-Fx II, FX8 and AX8 have this feature, the Axe-Fx III, FM3 and FM9 do not.
 +
 
 +
'''Axe-Fx II''' — On the Recall screen, press PAGE RIGHT to get to the Recall Effect page.
  
* '''Axe-Fx II''': on the Recall screen, press PAGE RIGHT to get to the Recall Effect page.
+
'''AX8 and FX8''' — Set one of your function switches to SINGLE PRESET/BANK, press the switch, press PAGE.
* '''AX8/FX8''': set one of your function switches to SINGLE PRESET/BANK, press the switch, press PAGE.
 
  
 
Follow the instructions in the manual to load a preset. Once the "RECALL" page is visible, press the <PAGE> button. This will take you to the "EFFECT" screen. From here you can load any effect block to your current preset from any other preset on the unit
 
Follow the instructions in the manual to load a preset. Once the "RECALL" page is visible, press the <PAGE> button. This will take you to the "EFFECT" screen. From here you can load any effect block to your current preset from any other preset on the unit
Line 411: Line 743:
 
* Always includes the X and Y settings (if applicable).
 
* Always includes the X and Y settings (if applicable).
 
* Includes modifier settings.
 
* Includes modifier settings.
* Does not include Global Block linking.
+
* Does not include Global block linking.
 +
 
 +
If the recalled block settings don't match the ones in the block from which they were copied (source preset), there's an issue with the preset version. See Troubleshooting below.
 +
 
 +
To recall internal controller values only, such as Envelope or LFO, scroll to Control when using Recall Effect.
 +
 
 +
==Global blocks==
 +
 
 +
Global blocks let you change a parameter value in all presets with the same instance of that Global block.
 +
 
 +
Read [[Global blocks]] for more information.
  
If the recalled block settings don't match the ones in the block from which they were copied (source preset), there's an issue with the preset version. To solve this, save the source preset (this will update it to the latest specs), then perform the recall operation again.
+
==Channels or X/Y switching==
  
To recall internal controller values only, such as Envelope or LFO, scroll to Control when using Recall Effect (not on Axe-Fx III).
+
Read [[Channels]].
  
Using [[Global blocks]] on the Axe-Fx II is another way to use parameter values in multiple presets. Global Blocks do not include modifier settings.
+
==Set Bypass state across all presets==
  
==Changing a parameter in multiple presets==
+
The bypass state of a block is saved per preset, not across all presets.
  
* [[Global blocks]] in the Axe-Fx II let you change a parameter value across multiple presets.
+
If you want systemwide control of the bypass state of an effect block, here's a solution:
* [[FracTool]]'s Batch Setter feature lets you change a parameter value across multiple presets.
 
  
==Bypass Mode==
+
* Attach the Bypass parameter of the effect block to an [[External controller]].
 +
* In the I/O menu, switch the external controller's initial value between 0% or 100% to change the effect's Bypass state. Or assign a switch on your foot controller to the MIDI CC of the external Controller to switch the block.
 +
* This works with Global and non-Global Blocks, and across all presets with the same effect block.
  
Owner's manual:
+
==Library==
* '''MUTE IN''': when the block is bypassed, its inputs are muted, silencing the both wet and dry but allowing effect “tails” to ring out or “spill over”. Use this for time-based effects in parallel.
 
* '''MUTE OUT''': when the block is bypassed, all audio is totally silenced at the outputs. Effect tails are silenced immediately, but the input is still “listening” so tails may be heard when you engage the effect.
 
* '''MUTE FX IN''': when the block is bypassed, the inputs of its internal processor are muted, but the dry is unaffected. This allows effect “tails” to ring. LEVEL and BALANCE controls continue to operate when the block is bypassed. Use this for time-based effects in series when you want spillover.
 
* '''MUTE FX OUT''': when the block is bypassed, the outputs of its internal processor are pulled, but dry signal is totally unaffected. With this setting, signals can enter a reverb or delay before it is engaged.
 
* '''MUTE''': when the block is bypassed, both wet and dry are totally silenced.
 
* '''THRU''': when bypassed, the block is completely disengaged. None of its parameters have any effect on the sound; it behaves exactly as if it were never there in the first place.
 
  
<blockquote>(Axe-Fx II) "A bypassed block does nothing more than copy the input to the output. Any perceived changes in sound are just that, perceived." [http://forum.fractalaudio.com/axe-fx-ii-discussion/88053-strange-more-bypassed-effects-less-gain-real-amp-feeling.html#post1064563 source]</blockquote>
+
Read [[Editors]] for more information.
  
The Bypass Mode parameter on the Axe-Fx II, AX8 and FX8 can be attached to a controller. The controller will then control the block's state: engaged or bypassed. You can also use the I/O menu to switch the effect through the corresponding INIT VALUE parameter. The Axe-Fx III provides a dedicated Bypass parameter for this purpose.
+
==Scenes==
  
The engaged/bypass state of an effect block can be different per scene (when not connected to a controller). See [[Scenes]].
+
Read [[Scenes]] for more information.
  
When putting blocks in parallel rows, it's important to set Mix, Level and Bypass correctly. The FX8 features "smart" Level, Mix and Bypass controls. These are automatically adjusted when moving an effect from series to parallel or vice versa.
+
==Performance Pages==
  
When switching between two Amp blocks in parallel rows, make sure to set their Bypass Mode to Mute, to prevent bleed-through of dry signal from the bypassed Amp block.
+
The Performance Pages on the Axe-Fx III, FM9 and FM3 allow fast access to system parameters and effect block parameters. There's a Global Perform page and a Per-Preset Perform page. You must use the editor to add controls to these screens.  
  
Bypassing a block does NOT lower CPU usage. CPU usage only decreases when removing the block from the grid.
+
* Each of the Performance sections can be configured with up to 10 user-selected controls from any of the blocks found in the preset (including Controllers and system settings). Configuration of the Perform tabs are done via the editor. Allowable controls include rotary knobs, slider controls (which are displayed as rotary knobs), push-buttons, drop-downs, and toggle controls (e.g., on/off controls).
  
==Channels and X/Y switching==
+
* The editor's Perform view is accessed via the <q>Perform</q> button or the Tools > Performance menu.
  
* [[Channels]] (Axe-Fx III).
+
* Performance controls are assigned via drag-and-drop from a block's parameter view to the Perform view. To assign a block's parameter to the Perform view, click on the control's label and drag the control to the desired Perform configuration. (To assign a Perform control from the CONTROLLERS Sequencer, right-click on the Sequencer control and choose the location from the pop-up menu.)
* [[X/Y switching]] (Axe-Fx II, AX8 and FX8).
 
  
==Controllers and modifiers==
+
* Assigned controls within the Perform view can be drag-and-dropped to new locations. The Perform view supports the SWAP and MOVE operations similar to the Grid.
  
Read this: [[Modifiers and internal+external controllers]].
+
* Each Performance control has two labels. To change the text of any Performance Control label, double-click it. To reset the label to its default text use the <q>Reset Label</q> button.
  
[http://forum.fractalaudio.com/threads/appendix-of-controllable-parameters.118090 List of controllable effect parameters in the AX8.]
+
* To remove a Performance control, select the control and press the DELETE key.
  
==Spillover==
+
* The <q>Per-Preset Performance Controls</q> are stored per-preset. Adding or removing a control from this area will change the EDIT state of the preset.
  
Read this: [[Spillover]].
+
* The <q>Global Performance Controls</q> are stored in the system settings. Adding or removing a control from this area automatically saves the control, without needing to save the preset.
  
=CPU load=
+
* The <q>Per-Preset Performance Controls</q> can be saved to and loaded from the [[Library]] using the arrow control in the <q>Per-Preset Performance Controls</q> title.
  
==About CPU usage==
+
* When the Perform view is visible, the main effect editor's controls are disabled to allow for drag-and-drop assignment to the Perform view.
  
A preset uses CPU (CPU is used here as a synonym to DSP). The amount depends on the number of blocks, effect settings, controllers, overhead and more. You can check the current CPU usage percentage on the hardware and in the software editor.
+
Firmware for the FM3 includes a short Performance Control Pages manual and tutorial.
  
Due to the power of the different processors in the hardware, the Axe-Fx II has more CPU available in presets than the AX8 and FX8. The Axe-Fx III has much more CPU available than the Axe-Fx II.
+
Tip: You can copy the Global Performance Controls to the Per-Preset controls in an empty Preset, then save the preset, and restore them at a later moment by switching back to that preset and copying them back to the Global Performance Controls pane. You can also save the Per-Preset Performance Controls to the [[Library]] and reload them later using the reveal triangle.
  
Important: bypassing a block on the grid does NOT lower CPU usage.
+
Also read [[Editors#Performance_pages|Editors]] for more information.
  
[http://forum.fractalaudio.com/axe-fx-ii-discussion/70023-why-there-limit-blocks-why-not-3-pitch-blocks-3-amp-whatever.html#post859452 Explanation why there is a CPU limit.]
+
==Tempo==
  
Even an empty preset requires CPU power, depending on things such as the input noise gate settings and overhead.
+
You can specify in the Tempo menu whether you want to the tempo to apply to all presets or per preset.
  
<blockquote>“CPU usage number represents the amount of CPU dedicated to audio processing in real-time. We chose to display the actual limitation, rather than scale the number.” [http://forum.fractalaudio.com/threads/ax8-cpu-power-limitations.114306/page-2#post-1456927 source] </blockquote>
+
Read [[Tempo]] for more information.
  
CPU usage is also covered in the Owners Manuals.
+
==Mix parameter==
  
==What happens when the CPU limit is approached==
+
The Mix parameter determines the amount of <q>wet</q> signal in a block. At <q>100</q> the signal is totally wet. This is usually used with effects such as Tremolo and Compressor. At <q>0</q>, the signal stays completely dry (no effect), with the exception of the Drive block.
  
At about 90% on the AX8, FX8, Axe-Fx II and III, you'll approach the CPU limit of your processor. You may notice the GUI becoming slow at that point. That's because the audio signal always gets priority, above the GUI refresh rate.
+
Mix at 50% results in both wet and dry being at -6 db in comparison to their maximum output levels (except the [[Delay block]] because of the <q>Delay Mix Law</q>). Compensate by adjusting Level.
  
When the presets requires too much CPU, audio starts too crackle and a warning message may appear. The GUI may prevent you from adding blocks at this point.
+
<blockquote>'''FRACTAL AUDIO QUOTES'''<HR>
 +
<blockquote>
 +
When turning up Mix in a block, the dry signal decreases. The table below shows wet/dry dB levels at various settings for blocks like Reverb, Pitch, etc. which do NOT use a constant power algorithm (like DRIVE). The Delay also uses a different method. In a rig where unity gain matters, these numbers are used to know how much to adjust Level for a given Mix setting.
 +
</blockquote>
 +
</blockquote>
  
<blockquote>“The audio processing is the highest priority thread. When there is time left the GUI thread is run. If CPU usage is high there simply isn't enough time to run the GUI at the normal refresh rate so the thread reduces the refresh rate.” </blockquote>
 
  
<blockquote>“The CPU simply monitors the time between frame interrupts and if it predicts it doesn't have enough cycles left to process the next effect in the grid it aborts and flashes a warning." [http://forum.fractalaudio.com/axe-fx-ii-discussion/56751-cpu-%25-overload.html#post712983 source] </blockquote>
+
<table border="1" style="border-collapse:collapse">
 +
<tr><th>MIX<br>SETTING</th><th>WET<br>LEVEL</th><th>DRY<br>LEVEL</th><th>WET/DRY<br>DIFF</th></tr>
 +
<tr style="text-align:right"> <td> 0  </td> <td> -∞    </td> <td> 0.00  </td> <td> -∞    </td> </tr>
 +
<tr style="text-align:right"> <td> 5  </td> <td> -26.02 </td> <td> -0.45  </td> <td> 25.58 </td> </tr>
 +
<tr style="text-align:right"> <td> 10  </td> <td> -20.00 </td> <td> -0.92  </td> <td> 19.08 </td> </tr>
 +
<tr style="text-align:right"> <td> 15  </td> <td> -16.48 </td> <td> -1.41  </td> <td> 15.07 </td> </tr>
 +
<tr style="text-align:right"> <td> 20  </td> <td> -13.98 </td> <td> -1.94  </td> <td> 12.04 </td> </tr>
 +
<tr style="text-align:right"> <td> 25 </td> <td> -12.04 </td> <td> -2.50  </td> <td> 9.54  </td> </tr>
 +
<tr style="text-align:right"> <td> 30  </td> <td> -10.46 </td> <td> -3.10  </td> <td> 7.36  </td> </tr>
 +
<tr style="text-align:right"> <td> 35  </td> <td> -9.12  </td> <td> -3.74  </td> <td> 5.38  </td> </tr>
 +
<tr style="text-align:right"> <td> 40  </td> <td> -7.96  </td> <td> -4.44  </td> <td> 3.52  </td> </tr>
 +
<tr style="text-align:right"> <td> 45  </td> <td> -6.94  </td> <td> -5.19  </td> <td> 1.74  </td> </tr>
 +
<tr style="text-align:right"> <td> 50  </td> <td> -6.02  </td> <td> -6.02  </td> <td> 0.00  </td> </tr>
 +
<tr style="text-align:right"> <td> 55  </td> <td> -5.19  </td> <td> -6.94  </td> <td> 1.74  </td> </tr>
 +
<tr style="text-align:right"> <td> 60  </td> <td> -4.44  </td> <td> -7.96  </td> <td> 3.52  </td> </tr>
 +
<tr style="text-align:right"> <td> 65  </td> <td> -3.74  </td> <td> -9.12  </td> <td> 5.38  </td> </tr>
 +
<tr style="text-align:right"> <td> 70  </td> <td> -3.10  </td> <td> -10.46 </td> <td> 7.36  </td> </tr>
 +
<tr style="text-align:right"> <td> 75  </td> <td> -2.50  </td> <td> -12.04 </td> <td> 9.54  </td> </tr>
 +
<tr style="text-align:right"> <td> 80  </td> <td> -1.94  </td> <td> -13.98 </td> <td> 12.04 </td> </tr>
 +
<tr style="text-align:right"> <td> 85  </td> <td> -1.41  </td> <td> -16.48 </td> <td> 15.07 </td> </tr>
 +
<tr style="text-align:right"> <td> 90  </td> <td> -0.92  </td> <td> -20.00 </td> <td> 9.08  </td> </tr>
 +
<tr style="text-align:right"> <td> 95  </td> <td> -0.45  </td> <td> -26.02 </td> <td> 25.58 </td> </tr>
 +
<tr style="text-align:right"> <td> 100 </td> <td> 0.00  </td> <td> -∞    </td> <td> ∞    </td> </tr>
 +
</table>
  
<blockquote>"Audio processing is the highest priority. Once you exceed 90% that remaining CPU is divided up between the display, expression pedals, MIDI, etc., etc. Something has to give." [http://forum.fractalaudio.com/axe-fx-ii-discussion/75320-pedals-lagging-when-cpu-around-92%25.html#post920394 source] </blockquote>
 
  
<blockquote>"The audio will always switch quickly. The display may take a while to switch since the audio processing takes priority. If CPU usage is high the display will take a little while to update." [http://forum.fractalaudio.com/axe-fx-ii-discussion/97242-does-anyone-else-have-lag-when-preset-switching-18b.html#post1167213 source] </blockquote>
+
The formula for an exact calculator is:
  
<blockquote>"The LCD is low priority. If CPU usage is high then the screen refresh rate drops because priority is given to the audio threads." [http://forum.fractalaudio.com/threads/having-screen-issues.116120/#post-1388090 source] </blockquote>
+
* <code>DRY LEVEL = (LOG((100-MIX)/100))*20</code>
 +
* <code>WET LEVEL = (LOG(MIX/100))*20</code>
  
[http://axefxtutorials.com/2014/09/why-does-it-say-excess-cpu-usage-why-is-there-a-crackling-noise-too More information by AxeFxTutorials.]
 
  
==CPU usage on FX8 and AX8==
+
Forum member DLC86 [https://forum.fractalaudio.com/threads/why-does-a-side-reverb-block-at-the-end-of-a-chain-right-before-the-output-so-different-great.160239/post-1918680 created this table], which lists the required dry level reduction with Mix at 50%:
  
The AX8 and FX8 allow you to put blocks into the grid that will push utilization above 88% (when not playing). When taking overhead into account, the real CPU ceiling is 90% (sustained).
+
<table style="text-align:right;" >
 +
<tr><td>Chorus:</td><td> -3 dB</td></tr>
 +
<tr><td>Compressor:</td><td> -6 dB</td></tr>
 +
<tr><td>Delay:</td><td> 0 dB</td></tr>
 +
<tr><td>Drive:</td><td> -6 dB</td></tr>
 +
<tr><td>Flanger:</td><td> -3 dB</td></tr>
 +
<tr><td>Formant:</td><td> -6 dB</td></tr>
 +
<tr><td>Megatap Delay:</td><td> -6 dB</td></tr>
 +
<tr><td>Multiband Comp:</td><td> -6 dB</td></tr>
 +
<tr><td>Multitap Delay:</td><td> -3 dB</td></tr>
 +
<tr><td>Phaser:</td><td> -3 dB</td></tr>
 +
<tr><td>Pitch:</td><td> -6 dB</td></tr>
 +
<tr><td>Plex Delay:</td><td> -6 dB</td></tr>
 +
<tr><td>Reverb:</td><td> -3 dB</td></tr>
 +
<tr><td>Ring Modulator:</td><td> -6 dB</td></tr>
 +
<tr><td>Rotary:</td><td> -3 dB</td></tr>
 +
<tr><td>Synth:</td><td> -6 dB</td></tr>
 +
<tr><td>Ten-Tap Delay:</td><td> -3 dB</td></tr>
 +
<tr><td>Vocoder:</td><td> 0 dB</td></tr>
 +
</table>
  
When CPU usage gets above 90%, the FX8 and AX8 will automatically disable blocks. The firmware will look for effects which are the biggest offenders, starting with the last edited one. If disabling the last edited one does not reduce the load enough, big offenders are next. Usually the Reverb block (especially when set to High Quality) is the first to go. Switching Reverb to Normal Quality may help to regain CPU power.
 
  
When an effect is automatically disabled, audio passes through as if it were a shunt. If it’s a block that is placed in a parallel row, this can cause a signal level issue.  
+
Note that on the VP4 the "Mix law" is adjusted.
  
Note about the Pitch block: the Pitch block in the AX8 and FX8 is very sensitive to CPU load, far before the CPU limit is reached. So try to keep CPU usage low (below 60 - 70%) when using pitch effects.
+
<blockquote>'''FRACTAL AUDIO QUOTES'''<HR>
 +
<blockquote>
 +
[https://forum.fractalaudio.com/threads/are-the-mix-levels-lower-than-the-equivalent-mix-levels-in-the-fm-and-iii.208988/#post-2611013]
 +
The mix law in many blocks is different to suit the "all effects before the amp" crowd better.
 +
</blockquote>
  
Tip: when building presets, always add the most CPU-hungry effects first.
+
<blockquote>
 +
[https://forum.fractalaudio.com/threads/are-the-mix-levels-lower-than-the-equivalent-mix-levels-in-the-fm-and-iii.208988/#post-2611186]
 +
The sweetened mix law places a wider range of knob motion in the portion of the curve where the delay is quieter. This replicates the way pedals that are designed for use in front of an amp work because the amp's compression reduces the difference between the quiet echoes and the louder dry signal.
 +
</blockquote>
 +
</blockquote>
  
<blockquote>"If I am reading these posts correctly, it sounds as though folks seem to think that an effects CPU usage is a static thing. That is, if I use a compressor in my preset it uses X% of the CPU. This is not actually how it works. CPU usage fluctuates as you use the device. That is, depending on what an effect is doing, or how it is configured, the CPU usage will vary dynamically. The AX8 monitors and manages the CPU usage. This is done for two reasons: (1) If CPU load gets too high, then the audio is effected (2) If CPU load gets too high, the front panel (footswitches primarily) is adversely effected. The performance of preset, scenes, effect bypass, etc. starts to become effected. A lot of development time has been put into reducing these effects, but it is impossible to eliminate them entirely. Rather than just allow the AX8 to behave in an undesirable fashion, the unit manages the CPU load by disabling effects. The biggest offenders are disabled first in an effort to reduce the number of disabled effects. This typically means the REVERB block is the first effect disabled. The trick is to build your presets in a manner in which this does not happen when you are playing live. In other words, test your presets out and give yourself some head room for last minute changes whenever possible." [http://forum.fractalaudio.com/threads/running-out-of-power-bug.116145/page-2#post-1388196 source] </blockquote>
+
==Global Effects Mix==
  
<blockquote>"Lots of different parameters, controllers, etc. can cause variation in your CPU utilization. Also, playing your guitar will bump your CPU as well. So, if you are looking at the utilization while your input is quiet, then you should plan on a 2% - 3% increase when you start playing. The cutoff for CPU is 90%. This cutoff prevents audio glitches, and provides enough CPU for low priority activities." [http://forum.fractalaudio.com/threads/ax8-cpu-limitation-amount.124809/#post-1484682 source]</blockquote>
+
The Effects Mix parameter in the [[Setup menu]] lets you control the overall wetness of effect blocks that have a Global Mix parameter. The parameter simply multiplies the Mix value in the presets.
  
==CPU usage increases with USB (Axe-Fx III: n/a)==
+
<blockquote>'''FRACTAL AUDIO QUOTES'''<HR>
  
Connecting via USB will increase CPU utilization. This is by design. If a preset uses much CPU, you may run into CPU overload problems when connecting the hardware to a computer through USB. [http://forum.fractalaudio.com/axe-fx-ii-discussion/41013-usb-connection-raises-preset-cpu-utilization-5%25.html#post551466 source] and [http://forum.fractalaudio.com/axe-fx-ii-bugs/40246-global-cab-sim-cpu.html#post573202 source]
+
<blockquote>
 +
[http://forum.fractalaudio.com/threads/global-reverb-on-all-presets.94812/#post-1135617]  
 +
Global Reverb and Effects Mix are relative. If set to 0% the mix is set by the preset. If set to, say, -10% the mix would be 10% less than the preset mix.
 +
</blockquote>
 +
</blockquote>
  
This does not apply to the Axe-Fx III because USB is handled by a dedicated USB processor.
+
==Global Reverb Mix==
  
<blockquote>"There's a bunch of stuff running behind the scenes. The control block is always running, the pitch detector for the pitch blocks is always running, the display is being updated, etc." [http://forum.fractalaudio.com/axe-fx-ii-discussion/82812-empty-preset-8%25-cpu-2.html#post1005020 source]</blockquote>
+
There's a separate global mix parameter in the [[Setup menu]] for reverb: Reverb Mix. Note that reverbs also are effected by the Effects Mix parameter (see above). The parameter simply multiplies the Mix value in the presets.
  
==CPU usage per block and effect type==
+
<blockquote>'''FRACTAL AUDIO QUOTES'''<HR>
  
* [http://www.roxxxtar.com/ax8-cpu-usage-chart CPU usage chart (AX8), by RoxXxtar.]
+
<blockquote>
 +
[http://forum.fractalaudio.com/threads/global-reverb-on-all-presets.94812/#post-1135617]
 +
Global Reverb and Effects Mix are relative. If set to 0% the mix is set by the preset. If set to, say, -10% the mix would be 10% less than the preset mix.
 +
</blockquote>
 +
</blockquote>
  
==How to decrease CPU usage==
+
==Internal controllers, External Controllers, Control Switches==
  
* The number of effect blocks in the preset has great impact on CPU usage. Be aware that a bypassed block uses the same CPU capacity as when engaged.
+
Read [[Controllers and modifiers]] for more information.
* Adding a second Amp block in an Axe-Fx preset increases CPU usage slightly (one DSP on the Axe-Fx is dedicated to Amp blocks).
 
* Attaching a controller to Input Drive in the Amp block may eat a lot of CPU. "If you attach a modifier to the Input Drive it is constantly recalculating the network which increases CPU usage."
 
* Switching off the noise gate in Input/Gate decreases CPU usage (less than 1%).
 
* Minimizing shunt blocks decreases CPU usage. If you use parallel paths, try to merge the paths instead of routing them all the way to the end separately.
 
* If you move an expression pedal, CPU usage will increase slightly because of MIDI traffic management.
 
* OUT COMP and SPEAKER COMP in the Amp block will increase CPU usage.
 
* Switch a Cab block to mono and/or another resolution to save CPU usage.
 
* When using more than one external impulse response in a mono Axe-Fx or AX8 setup, mix them into a single IR to avoid having to use a stereo Cab or two mono Cabs.
 
* Connecting USB increases CPU usage (Axe-Fx III: n/a).
 
* Some effect types within an effect block use more CPU than others. Example: Studio compressor versus Pedal compressor types, Hall reverb versus Spring Reverb.
 
* Use X/Y or channels instead of two instances of an effect block to save CPU.
 
* Reduce the number of controllers.
 
* High Quality Reverb uses more CPU than Normal Quality.
 
* Spring Reverb uses the least amount of CPU of the Reverb types.
 
* Decrease CPU usage by decreasing Echo Density in the Reverb block.
 
* The Fast RMS detector type in the Studio Comp uses less CPU than the other types.
 
* Filter: use a lower Order and Q.
 
* Multi Delay: use a different type.
 
* Chorus: use less voices.
 
* Phaser: use less stages.
 
* Pitch: the Pitch block in the FX8 and AX8 has an Economy mode that decreases CPU usage. The Axe-Fx doesn’t.
 
* FX8: disable the Looper.
 
* Drive blocks: CPU usage is amplitude dependent, which means that adding a Drive block to a preset not only increases CPU usage, but CPU usage will also increase when playing the guitar (and more with two Drive blocks).
 
* Synth: turn off voices.
 
* Cab preamp simulation uses more CPU in High Quality mode than in Economy mode.
 
* [http://forum.fractalaudio.com/axe-fx-ii-discussion/60723-tips-taming-cpu.html#post756543 More tips from forum member Voes and others.]
 
* [http://forum.fractalaudio.com/axe-fx-ii-discussion/49146-wicked-wiki-3-decreasing-cpu-usage.html Wicked Wiki.]
 
  
=Waveforms=
+
==Waveforms==
  
 
[[image:waveform.png|link=]]
 
[[image:waveform.png|link=]]
  
Look up the explanation of waveforms and graphs in the Owner's Manual and [http://en.wikipedia.org/wiki/Waveforms Wikipedia].
+
For explanations of waveforms and graphs, read the [[Owners_Manuals|Owner's Manual]] and and look up [http://en.wikipedia.org/wiki/Waveforms Waveforms in Wikipedia].
  
=Crossfading sounds=
+
=Troubleshooting=
  
There are several ways to accomplish this.
+
==No sound==
  
Use the Multiplexer in the Axe-Fx III.
+
If the device or preset doesn't produce any sound, check the following:
  
Use the Sequencer internal controller. (source: Bakerman):
+
* Check your cables! [https://forum.fractalaudio.com/threads/if-you-read-nothing-else-read-this.162537/]
*# Set it to something like 16 steps, Rate just over 1 Hz, Values increasing in steps of 10% and have it sit at 100% for the last 6 steps.
+
* Is the latest firmware installed on the unit?
*# Place a volume block in each signal chain and assign Seq to turn chain B up and chain A down.
+
* Is the correct Input block connected to the correct Output block on the grid?
*# Use several hundreds of milliseconds of damping.
+
* Verify that Bypass Mode in bypassed blocks is not set to “Mute”.
*# Assign one switch to Sequencer Run control and a second switch to bypass both volume blocks. You'll want them engaged before/during the crossfade.
+
* Are the blocks set to channels that pass signal?
*# Use Mute Bypass mode for the Vol block in chain A, Thru Bypass mode for the one in chain B.
+
* Does the Cab block use a cab slot that's not empty?
Now you can be playing sound A, hit switch 1 and get the 8-9 second crossfade, then hit switch 2 within the next 4-5 seconds before the sequencer restarts. If you wait too long you'll hear it fade back quickly to A (then B gradually again) but whenever you hit it you'll hear sound B regardless of what the sequencer's doing. After that you can always stop the sequencer and switch back to sound A; it will just be instant instead of a crossfade.  
+
* There isn't an expression pedal muting the signal?
 +
* Are the OUT level knobs on the hardware turned up?
 +
* Is Return Level in the Feedback Return block turned up?
 +
* Is the Scene Output Level in the Output block correctly set?
 +
* Isn't Gain in the Global EQ turned down?
 +
* Is the monitor or other amplification turned on?
 +
 
 +
==Bypass corrupt preset at startup==
 +
 
 +
A corrupt preset can cause problems at startup.
 +
 
 +
; Axe-Fx III : If a problematic system parameter prevents the device from booting, hold EDIT on startup to bypass non-default system settings and reset them. Press-and-hold both EDIT and HOME at startup to bypass and reset the system settings AND load a fully initialised empty preset.
 +
 
 +
; FM9, FM3 : If a problematic system parameter prevents the device from booting, hold EDIT on startup to bypass non-default system settings and reset them. Press-and-hold both EDIT and HOME at startup to bypass and reset the system settings AND load a fully initialised empty preset.
 +
 
 +
; Axe-Fx II XL/XL+ : Hold down Page Left and Page Right while cycling power until the Emergency Utility menu appears. Update the firmware using Fractal-Bot.
 +
 
 +
; FX8 : Hold down SETUP and power the unit on. Hold the button for about 1 second beyond the power up, then release. The unit will now allow you to install firmware using Fractal-Bot. If a problematic system parameter prevents the device from booting, press ENTER when the splash screen is displayed.
 +
 
 +
; AX8 : Hold down SHIFT and power the unit on. Hold the button for about 1 second beyond the power up, then release. The unit will now allow you to install firmware using Fractal-Bot. If a problematic system parameter prevents the device from booting, press ENTER when the splash screen is displayed.
 +
 
 +
If the unit sounds bad after an update, try this: [[Reset system parameters]]
 +
 
 +
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
 +
 
 +
<blockquote>
 +
[http://forum.fractalaudio.com/threads/firmware-3-0-beta-output-volume-drop.147052/#post-1737574]
 +
There's multiple levels of error checking. First the USB endpoint is a bulk endpoint so it has guaranteed transmission. Then each packet has a checksum. Then the entire image has a checksum. Finally the image written to the FLASH is compared to the downloaded image byte-by-byte. It's virtually impossible to have corrupted firmware image.
 +
</blockquote>
 +
 
 +
<blockquote>
 +
[https://forum.fractalaudio.com/threads/fm3-firmware-version-5-00.181256/post-2221317]
 +
It's virtually impossible to brick a Fractal product. All our products feature an "emergency bootloader" that allows booting the unit in the event of a failed firmware update.
 +
</blockquote>
 +
</blockquote>
 +
 
 +
==Issue with Effect Recall or copy-and-paste==
 +
 
 +
This applies to previous-generation hardware only:<BR>
 +
If using Recall Effect or copy-and-paste in the editor doesn't deliver the expected results (different sound), there may be a mismatch between the preset versions. To solve this, save the source preset to update it to the latest specs, then perform the recall or copy/paste operation again. When executed, all presets stored in flash with an older version of the firmware will be upgraded to the currently installed firmware version and automatically re-saved to flash. This process can take up to 20 minutes but will speed up preset changes in some cases.
 +
 
 +
==Preset appears empty==
 +
 
 +
If a preset unexpectedly shows up empty, it was probably saved with firmware that is more recent than the version that is loaded on your device. Update your unit's [[Firmware]].
 +
 
 +
<blockquote>'''FRACTAL AUDIO QUOTES'''<HR>
  
Use [[Scenes|Scene controllers]]. Use a damping value of several hundreds of milliseconds.
+
<blockquote>
 +
[https://forum.fractalaudio.com/threads/reverted-back-to-fw-15-created-presets-missing-from-axe-and-backups.171096/post-2061172]
 +
Whenever there is a major revision presets created with that revision are NOT backwards compatible.
  
Use a pedal to crossfade between two AMP blocks:
+
</blockquote>
*# Assign the Level parameter of one AMP block to an external controller.
+
</blockquote>
*# Do the same with the other AMP block, using the opposite curve (or reversed Min/Max values) and using the same external controller.
 
*# Assign the external controller to a pedal.
 
  
[http://forum.fractalaudio.com/axe-fx-ii-discussion/84967-distortion-clean-scene-spillover.html More tips about crossfading.]
+
==Device won't save a preset==
  
=Comparing sounds=
+
If saving a preset to a specific preset slot on the device is unsuccessful, there may be an issue with its FLASH memory.
  
* Use [[X/Y switching]] or [[Channels]].
+
<blockquote>'''FRACTAL AUDIO QUOTES'''<HR>
* Use [[FracPad]].
 
* Use snapshots in the software editors.
 
  
=Troubleshooting=
+
<blockquote>
 +
[https://forum.fractalaudio.com/threads/corrupt-unusable-presets-on-axefxiii.194511/#post-2422385]
 +
If it's always the same preset locations then the FLASH is going bad.
 +
</blockquote>
 +
</blockquote>
  
==No sound==
+
=Videos=
  
[[No sound|Help, I have no sound]].
+
[[video:Rosh-BasicPreset]]
 +
[[video:RoshBypassModes]]
 +
[[video:Rosh-SeriesParallel]]
 +
[[video:Leon-ScenesPresetsChannels]]
 +
[[video:Leon-SceneandChannels]]
 +
[[video:Cooper-CombiningPresets]]
 +
[[video:Leon-AX8-Routing]]
 +
[[video:Matt-Routing]]
 +
[[video:Rosh-Parallel2]]
 +
[[video:Tom-FM3]]
 +
[[video:Rosh-Gapless]]
 +
[[video:Rosh-TrueGapless]]
 +
[[video:G66-GlobalMix]]
  
 
[[category:Axe-Fx2]]
 
[[category:Axe-Fx2]]
 
[[category:Axe-Fx3]]
 
[[category:Axe-Fx3]]
 
[[category:AX8]]
 
[[category:AX8]]
 +
[[category:FM3]]
 +
[[category:FM9]]
 +
[[category:VP4]]
 
[[category:FX8]]
 
[[category:FX8]]
 
[[category:Sounds]]
 
[[category:Sounds]]
 +
[[category:Remote]]
 +
[[category:All]]

Latest revision as of 14:59, 8 November 2024

Contents

Presets.png

Number of preset slots

Axe-Fx III

  • Mark I: 512
  • Mark II, Mark II Turbo: 1024

FM3, FM9: 512
VP4: 104
Axe-Fx II

  • Mark I and II: 384
  • XL and XL+: 768

AX8: 512
FX8: 128

FRACTAL AUDIO QUOTES


[1] The progress bar during boot indicates presets being copied from FLASH to RAM. If a preset is empty it is skipped so the more empty presets you have the shorter the boot time.

About presets

The differences between presets, scenes and channels:

Presets
A Preset is like your traditional pedalboard. Because we can have many different presets stored in the modeler, it is as if we have numerous pedalboards within reach at any moment.
Scenes 
Scenes are like your traditional pedalboard at a particular moment, with effects on or off and set to a specific channel.
Channels 
Channels are like the pedals on that pedalboard with its controls set in a specific way. There are four channels in most blocks, so there are four different sets of settings.

The hardware display and the switch LED on compatible foot controllers show the currently loaded preset.

Read more about presets in the official manuals.

Zoomed display mode

The FM3 and FM9 support a zoomed display mode, where the preset title and all eight scenes are displayed in a large font for easy viewing. Turn the B knob on the Home screen to switch between display modes. In zoomed mode, use the cursor keys to switch between scenes and use the Value Wheel then press the Enter button on the front panel to switch presets.

Zoomed:
S2.jpg

Factory presets

Read Factory presets for more information.

Songs and setlists

Read Songs and setlists for more information.

Guidelines

  • Try to stick to the same grid layout/routing if possible, to simplify viewing and editing and to increase preset switching speed.
  • Re-use effect blocks with preferred settings and levels, through Global blocks or the Editor's Library.
  • Assign External controllers in a consistent way. Decide if you want them to reset or not when switching presets using the PC Reset parameter.
  • Effects in front of Amp and Drive blocks should not be set to stereo. Certain effect blocks, such as Amp, Drive and mono Cab, sum the signal to monoaural. Check your system settings and blocks for correct mono and stereo operation to prevent phase cancellation. Read Mono and stereo for more information.
  • Make sure that the blocks maintain unity gain in engaged and bypassed states.
  • Set Mix, Level, and Bypass parameters correctly when placing effects in parallel rows.
  • Make sure that the overall preset level matches that of other presets and does not clip when engaging a volume boost, Wah, etc. Use the Tools | Preset Leveling tool in the editor.
  • Let delay and reverb trails spill over between scenes.
  • Check the preset’s noise gate settings. Turn it off when not needed to save CPU.
  • Adjust the desired Input impedance in the Input block if needed and supported by the processor.
  • Use a consistent way to boost the level for leads.
  • Make sure that effect blocks are set to the correct channel in each scene.
  • If Tempo is set to Preset, set the preset's tempo settings.
  • When using one Amp block on an Axe-Fx: use AMP 1, not AMP 2.
  • Make sure that CPU usage stays below the limit (80%). Note that CPU usage can vary, depending on the channel of effect blocks. Also note that the value is the average and that spikes in CPU usage can be higher.
  • Place effects where they should be placed, e.g. Pitch before or after Amp/Cab.
  • Some people like to mute scenes that are not being used by disabling all blocks in those scenes. Others prefer to copy a generic scene for the preset to the unused slots and clear the name. The first ensures that ONLY the defined scenes will output sound, the second allows for accidentally scrolling into an undefined scene so sound is still output.
  • Use a consistent naming scheme for preset titles.
  • Use a consistent naming scheme for scene titles, if the processor supports it.
  • Choose titles that fit on the hardware displays of the processor and foot controller. The displays are capable of showing up to ten characters.
  • FC-6 and FC-12 controllers, FM3, FM9: program per-preset switches.
  • AX8 and FX8: assign switches to effects in the preset.
  • FRFR: enter the desired low-pass and high-pass settings in the Cab block if desired.
  • Configure the Per-Preset Perform page.
  • Check the block Meters in the second tab in the Layout view on the front-panel.
  • Make sure the preset still works if a pedal or switch isn’t connected.

Note: The number of blocks in a preset does NOT have any impact on latency. Depending on the hardware, the type of blocks can affect latency. Read this: Latency.

Loading presets

Load a preset

Load presets in one of the following ways:

  • Use the tools on the hardware: the Value wheel, or cursor keys, or Home > Presets menu on the front panel. Use the soft knob to sort.
  • Use the editor: click on the Presets button or use Tools > Manage Presets.
  • Use a Fractal Audio controller.
  • Use a third-party MIDI controller.
  • Use a switch that's connected directly to the unit.
  • Use FracPad.

The Ignore Redundant PC parameter in the Setup menu determines what happens if the unit receives a MIDI Program Change for a preset that already is loaded. If Ignore Redundant PC is ON, and the desired scene is different from the current scene, the preset is not re-loaded but the default scene is selected.

The Axe-Fx III, FM9 and FM3 let you map MIDI commands to preset switching.

Load a recently loaded preset again

The editor keeps a list of recently loaded presets under Preset > Recent Presents.

Alternatively, hold Command on macOS and click on the Presets button.

Load from disk

Preset files on disk have a .syx file extension. Bank files, which contain multiple presets, have the same file extension.

These are different ways to load a preset file from disk into the hardware:

  • Import the file into the connected editor through Preset > Import.
  • Drag and drop the file onto the connected editor.
  • Use the editor's Tools > Manage Presets tool.
  • Use Fractal-Bot.
  • Use a MIDI librarian such as Snoize SysEx Librarian or MIDI-OX.
  • Use FracTool.

You can use the editor with your device or Fractal-Bot to transfer entire banks to the hardware. The editor also lets you open a Bank file and import a single preset from that file.

The hardware is always ready to receive presets.

After loading a preset from the disk into the hardware, the preset resides in a temporary buffer. It is not saved in the hardware's memory until you explicitly Save it.

Import from other devices

Presets are device-specific, which means that there are limitations to sharing presets across different modelers.

Presets for the Axe-Fx III, FM9 and FM3 are mostly compatible (VP4: not); The most important factor is available CPU power. Other limitations are mentioned in Axe-Fx III, FM9 and FM3. The PresetTranslator in the Editors maintains a log file, accessible in the Help menu.

Presets moved between the original hardware and their updates, such as the various Turbo and Mark II series are completely compatible if the block types are supported. The respective Edit applications are able to translate between the other units, however they do not convert the presets to fit. Said differently, an Axe-FX III preset that will exceed the FM3's CPU will not be automatically adjusted to run correctly on the smaller processor. That is our job to do before attempting to import the preset. Failing to do so can lock up the smaller siblings requiring a reboot and possibly using recovery steps to remove the preset.

There are various workarounds for sharing presets between other processors:

  • The editor's Library lets you share effect block files between devices.
  • The editors let you export a preset as text, which will contain all parameter values.

Startup preset

You can specify in the Setup menu which preset should be loaded when the device is powered on. This applies to the FM9 and FM3 only, at the time of writing.

Default scene

The processors let you specify which scene should be recalled upon loading a preset. Read Scenes for more information.

Edited LED

Current generation processors and editors (optionally) prompt before changing presets if the current preset has been edited. This makes sure you do not lose edits. Note that the prompt doesn't appear when changing presets via MIDI.

This feature can be turned on/off in the Setup menu.

That menu also let you determine whether switching scenes should be marked as an Edit or not. When both parameters are enabled, you can't switch between presets using the FC controller, because the hardware will ask for confirmation first.

Gapless changes

In current firmware, switching presets can happen gapless.

Read this: Gapless Changes.

Spillover between presets

Read Spillover for more information.

Send MIDI when loading presets

The Scene MIDI block lets you send MIDI Program Changes and Control Changes when loading a preset.

FC: automatically display scenes after switching presets

You can configure an FC controller, the FM3 and FM9 to automatically display scenes after switching presets. In the PRESETS layout, add a layout link from the foot switch for that scene to the SCENES layout. When you select the preset, the modeler will automatically switch to display the scenes. Repeat as necessary for other preset switches.

Crossfading

There are several ways to crossfade sounds.

Scene scontrollers — Use Scene controllers with a damping value of several hundreds of milliseconds.

Sequencer — Use the Sequencer internal controller. (source: Bakerman)

  1. Set it to something like 16 steps, Rate just over 1 Hz, Values increasing in steps of 10% and have it sit at 100% for the last 6 steps.
  2. Place a volume block in each signal chain and assign Seq to turn chain B up and chain A down.
  3. Use several hundreds of milliseconds of damping.
  4. Assign one switch to Sequencer Run control and a second switch to bypass both volume blocks. You'll want them engaged before/during the crossfade.
  5. Use Mute Bypass mode for the Vol block in chain A, Thru Bypass mode for the one in chain B.

Now you can be playing sound A, hit switch 1 and get the 8-9 second crossfade, then hit switch 2 within the next 4-5 seconds before the sequencer restarts. If you wait too long you'll hear it fade back quickly to A (then B gradually again) but whenever you hit it you'll hear sound B regardless of what the sequencer's doing. After that you can always stop the sequencer and switch back to sound A; it will just be instant instead of a crossfade.

Pedal — Use a pedal to crossfade between i.e. two AMP blocks:

  1. Assign the Level parameter of one AMP block to an external controller.
  2. Do the same with the other AMP block, using the opposite curve (or reversed Min/Max values) and using the same external controller.
  3. Assign the external controller to a pedal.

Create a fully initialised empty preset

Fractal Audio:

  1. Power down the unit and wait five seconds.
  2. Power on holding HOME until the boot-up progress bar first appears.
  3. The unit will boot with an empty initialized preset in location “000”. You can STORE this to any other location.

Managing presets

Preset titles

Axe-Fx III, FM9 and FM3:

Axe-Fx II:

  • X: Insert a character at the current cursor position.
  • Y: Delete the character at the current cursor position.
  • A: Select an upper-case character.
  • B: Select a lower-case character.
  • C: Select a number.
  • D: Move the cursor.
  • < >: Move the cursor.
  • Value: Select any character from the character set.

FX8 and AX8:

  • Value/NAV: Move the cursor.
  • A: Select an upper-case character.
  • B: Select a lower-case character.
  • C: Select numbers and symbols.

When renaming a preset in the software editor, make sure to press ENTER in the name field, before saving the preset.

Manage Presets tool

The tool Manage Presets in the editor lets you manage presets: copy, paste, delete, clear, import/export, etc.

Preset numbering

Preset numbering starts at 000. The Display Offset parameter in the Setup menu lets you change this to 001. This only affects offsets the display, meaning that it does not change which preset is actually loaded by a given footswitch or MIDI message.

Export to disk

To export a preset (or bank) to disk for archiving or sharing:

  • Select Export in the editor.
  • use the editor's Manage Presets tool.
  • use Fractal-Bot.

The preset or bank will have the .syx filename extension.

Do not share IRs which are protected by a EULA, license, copyright, etc.

If the preset has Global blocks (Axe-Fx only), it's recommended to unlink these before exporting a preset. If not, the preset is only usable if you include your system data file.

FC: save through a foot switch

An edited preset can be saved during a performance through a foot switch on your FC. Assign the function Amp Level + Save with a value of 0 dB to a switch.

Preset-Cab bundle

A Preset-Cab bundle is a single file containing a preset and user IRs used by that preset. You can save and load Preset-Cab bundles with the editor. Bundles make it easier to share sounds and are easy to export and import.

Warning: Do not share IRs which are protected by a EULA, license, copyright, and such.

To export a bundle, use the Preset > Export Preset-Cab Bundle menu in the editor, which will display a dialog allowing us to include user IRs which can be saved by checking them.

To import a bundle, use the Presets > Import Preset menu in the editor, or drag-and-drop a bundle file onto the editor's main Preset display. This will display a dialog. This dialog unpacks a Preset-Cab Bundle and saves it ready-for-use to your device. A bundle contains one preset plus all of the IRs it depends on. To proceed, you must select a location to save each of the items within the Bundle. The preset will be updated automatically to refer to the location(s) you selected for the IRs.

Also see Cab block for more information.

Swap presets

The Axe-Fx III, FM9 and FM3 currently don't provide the possibility to swap presets on the hardware itself. Use the editor's Tools > Manage Presets tool.

Share presets

Besides the factory presets, there are presets and preset collections available from various sources.

The main sources for free presets are:

There also are many commercial or donation-based offerings available, such as:

Delete presets

The hardware does not provide a Clear or Delete/Erase tool for single presets. You can clear a preset slot by overwriting it with another empty preset.

Use the editor to clear a single or multiple presets.

The Setup menu on the Fx III, FM9 and FM3 allows deleting ALL presets. Be careful!

FRACTAL AUDIO QUOTES


[2] This erases the presets from non-volatile memory. The presets are in still in RAM until you reboot. This allows a small bit of safety in case you decide "oh, crap, I didn't want to erase THIS preset".

Create a list of all presets

In the software editor, select Tools > Export as Text. You can also choose to save a list of all presets including all scenes.

Export preset settings to CSV

This command is available as a menu command in AX8-Edit. In FX8-Edit, hold down Ctrl+Alt+Shift and click Import on Windows. On macOS use Command+Alt+Shift.

In the software editor, select Export Preset as CSV if available.

When executing this command, the editor writes a Comma-Separated-Values (CSV) file to disk that contains a list of the parameter values of each block in the current preset. CSV files are a basic common database format that can be read or imported by any text editor, spreadsheet and database application.

You can also use this feature to see if a preset has changed, by dumping a preset before and after editing.

Preset size

In rare cases a preset can get too large, having too many bytes. This is not the same as overloading the CPU. There's no warning or checking mechanism for this. If this happens, certain values won't get stored, or revert to zero upon recall. These are rare cases, which seem to occur mostly when the user uses a VERY large number of modifiers/controllers, or too many Global blocks.

FRACTAL AUDIO QUOTES


[3] A preset in the III is four times the size of a preset in the II.

CPU usage

Read CPU usage for more information.

Preset levels

Level controls

  • The Input block has a Level control. It allows sending a lower or higher level into the effects grid which i.e. can be used to compensate for guitars with varying output levels.
  • Each preset has a Level control in the Output block, and in the FX Loop block on the Axe-Fx II and AX8 only. Level in the Output block and FXL block is saved per scene.
  • All effect blocks have Level controls.

There are systemwide level controls too.

  • The Global EQ provides gain controls for each output.
  • OUT knobs on the top/front panel.
  • Some processors let you switch the nominal output of the device between +4 and -10 dB in the Setup menu.

If the red “Out Clip” LED blinks, the signal in the digital domain is too hot (loud). Severe clipping will cause digital audio distortion (crackle) which you want to avoid. This kind of clipping is not related to amp distortion.

Read Main output level for more information.

Important:

  • The OUT level knobs on the top/front panel have no effect on output clipping, because they control the analog circuitry and are placed after the digital-to-analog converter.
  • Clipping always occurs at the digital-to-analog output stage.
  • You can't clip an individual block.
  • Digital clipping does NOT harm the unit.
  • There is NO relationship between Input Level / Input Pad and output clipping. The Input Level parameters in the Setup menu only control the signal-to-noise ratio at the input stage and do NOT affect gain in the signal chain.

FRACTAL AUDIO QUOTES


[4] It is floating point. A block can't clip (unless it's designed to).

You can reduce the digital signal level in any block by turning down its Level. The Amp block's Level or the Output block's Level controls are recommended.

If your unit's output is clipping heavily during a gig, you don't need to adjust the preset. Just enter the Global EQ and turn down Gain to solve this temporarily. Use the OUT knob on the top/front panel to compensate for loss of volume.

The latest generation of processors feature meters in the Layout menu which display the level of each effect block. This is extremely helpful for finding the cause of an interrupted signal.

Setting and matching levels

You probably want to match the output levels of all your presets. If you want to do this by ear, don't do it at low volume level and don't use headphones. The reason is, you may think that your high-gain preset needs to be turned down compared to your clean preset, but when playing live, that high-gain preset is compressed and has no peaks, while the clean is tone is very dynamic. Really, the only proven way to match levels by ear is to do this at gig level, and preferable with the band playing or using a backing track.

The recommended control to adjust the preset level is Output Level in the Amp block. The current editors provide a Preset Leveling tool for this task using Control+L on Windows or Command+L on macOS.

FRACTAL AUDIO QUOTES


[5] The amp block is always the place to set your volume. The Level control is repeated at several places in the amp block menus for convenience so you don't have to keep switching pages. The Level control has no affect on the tone.

That quote above is only valid for non-MV amps (i.e. Fenders). The Master Volume (MV) DOES affect the tone. It sets the level into the power amp simulation. The Level control has no affect on the tone. For non-MV amps the recommended setting for MV is around 9.0. For MV amps, i.e a 5150, adjust the MV until the desired amount of power amp distortion is obtained. Most MV amps rely on preamp distortion and don't produce much power amp distortion. If you turn the MV up too high on them the tone will get muddy and flubby.

Non-MV amps rely primarily on power amp distortion so you need the level into the power amp to be hot enough to push the power amp into distortion.

Another approach is to measure and match the preset levels using the VU meters. These show the relative loudness of the preset.

To view the VU meters:

Axe-Fx III, FM9, FM3 — Zoom out from the layout grid, or view the Output blocks.

Axe-Fx II — Use the Utility menu.

AX8 — Page right.

These readouts can be used to help set preset levels to the same apparent volume. For convenience, the level of the Amp blocks can be set from this page.

Section 7 of the Axe-Fx III Owner's Manual also discusses setting preset levels.

FRACTAL AUDIO QUOTES


[6] Don't be afraid to turn up the Amp level. The VU meters are calibrated such that there is 12 dB of headroom at the red line when the Output Level knob is at maximum.

[7] ITU-R is a standard for loudness measurement. Broadcasters use it to monitor the apparent loudness of program material and comply with regulations, i.e., making sure commercials aren't louder than the programming. The measurement includes a simple head model and hearing perception model to give a fairly accurate indication of relative volume.

Be aware that the VU meter is offset by 20 dB, so when the meter reads 0 it’s actually -20 dB. This means that the "0" mark does not indicate clipping. This allows for sufficient headroom. When playing you'll see the meters bounce around. The meters give you a general idea of the loudness of the current preset, to get you in the ballpark. Try strumming the strings in a consistent way. Adjust the Amp level(s), aiming for an average level around 0 dB.

And another method:

  1. Select a preset with a really clean amp. Why? As Jay Mitchell explains: Clean presets have the greatest crest factor (ratio of peak to average energy) and will therefore cause digital clipping at lower average levels (which determine your perception of volume) than gainier presets. For that reason, it is important to reference the levels of all other presets to that of the cleanest one set so that it never causes the (device) to clip with the Level control set to maximum. Once you have set this level you then need to set other presets to match it. Otherwise, your cleaner presets will either clip or be much softer than the others.
  2. Disable all effect blocks, especially compressors, except Amp and Cabinet.
  3. If you use a boost in the preset, enable it.
  4. Select your loudest pickup and hit the strings hard.
  5. Turn down Amp Level until the clip LED doesn't light anymore.
  6. Turn the level down another 8 dB. This creates sufficient headroom for unforeseen circumstances.
  7. This is now your reference level for all presets.
  8. If this method causes volume loss, compensate by turning up the overall volume level on the front panel or on your amplifier.

FRACTAL AUDIO QUOTES


[8] All Fractal Audio products use floating-point processing. In fact the Axe-Fx III uses 64-bit floating-point in many places. It's impossible to clip internally. The AX-8 and Axe-Fx II use 40-bit in many places and are also impossible to clip internally. If you are clipping the output, which is the final fixed-point signal to the converters (all audio converters use fixed-point), then your internal signals are far too high. If you use the VU meters and set your output to 0 dB you are guaranteed 12 dB of headroom at the converters with the output level knob all the way up. I've never witnessed a palm mute that was more than a few dB hotter than nominal.

Go into the Layout menu and press the Zoom hotkey. This will display VU meters for the two main outputs. Adjust the level of the Amp block (using the Block Level knob with the Amp block selected) so that the signal hovers around the 0 dB marker. If you do this it's impossible to clip the outputs.

The factory presets are all adjusted for roughly 0 dB on the VU meters. Even with the output level knob all the way up I never get anywhere even close to clipping.

We could've taken a conservative approach and built in a lot of headroom so that clipping the converters was impossible but then you lose dynamic range. The approach taken optimizes the dynamic range of the converters (so you aren't wasting bits) thereby ensuring maximum fidelity and lowest noise. It does require that the user adjust their presets correctly to avoid overflowing the converters but the VU meters make this task trivially easy.

[9] The leveling tool will often result in clean tones not sounding as loud as distorted tones due to the greater dynamic range.

Vol Inc and Vol Dec

Volume Inc(rement) and Volume Dec(rement) present a convenient way to adjust preset levels on the fly (without manual editing). These commands let you adjust the preset level in steps of 1 dB while playing. Adjustments are saved automatically.

To make this work, assign these commands to switches on your foot controller, using their MIDI CCs. The MFC-101 MIDI foot controller (discontinued) and FC-6 and FC-12 foot controllers have dedicated commands for this purpose.

Notes:nued

  • Make sure that a single press sends just one command, not a double one.
  • Axe-Fx II and AX8: Vol Inc and Vol Dec only affect the signal through Output 1, not Output 2, unless Echo Output 1 is set to Output 2 in the Setup menu AND the preset doesn't contain an FX Loop block (AX8 or Axe-Fx II).
  • Axe-Fx III, FM9, and FM3: there are separate Vol Inc/Vol dec commands for Outputs 1 and 2.
  • They work per scene.

Note that other unsaved changes to the preset will get saved too when Vol Inc or Vol Dec is triggered.

The FC-6 and FC-12 foot controllers, FM3 and FM9 provide an alternative for Vol Inc and Vol Dec: adjust Amp Level in steps. This also includes a quick way to save a preset in its current state through a footswitch (without increasing or decreasing the level).

Boost the output level

Methods to boost the signal level, i.e., for leads:

  • FM3, FM9, FX3, All GEN1 + GEN2 devices:
    • Add a Filter block at the end of the signal chain, set to Null with Level at e.g. 3 dB, and its Bypass assigned to a switch.
    • Use a PEQ or GEQ block with its Level turned up and assign the block's Bypass to a switch.
    • Use a pedal or switch to turn up Gain the Amp block, or Input Trim, or Master Volume, of the Amp block.
    • Boost the level at the input of the grid using the Level parameter in the GTE/IN menu.
  • FM3, FM9, FX3: Use a scene for increased output level.
  • MFC-101: Create a global Boost switch without having to modify each preset (source: M@) as follows.
    • Set the CC of an IA switch on the floor controller to OUT1 VOLUME.
    • Set the OFF value to 111 for example, for the unboosted level, and set the ON value to 127 for the boosted level.
    • If you're using Output 2 as well, don't forget to add a second CC for OUT2 VOLUME, or assign OUT2 to the same CC as OUT1.
  • All devices: Use an expression pedal.
  • All GEN1 + GEN2 devices: Assign a modifier to Level in the Cab block.
  • X/Y: AX8, FX8. Scenes: FM3, FM9, III: Configure a block for X/Y switching or channels.

For more information see:

Routing

Series and parallel routing

You can put effect blocks in series (in a single row) or parallel.

Axe-Fx III – Extensive routing possibilities, using the 6x14 grid.

FM9 – Extensive routing possibilities, using the 6x14 grid.

FM3 – Extensive routing possibilities, using the 4x12 grid.

VP4 – An effect can be placed in parallel with the previous effect..

Axe-Fx II and AX8 – Extensive routing possibilities, using the 4x12 grid.

FX8 – Single row and the possibility to place an effect in parallel with another effect. You can adjust the placement of effect blocks in the preset configuration (Config page). Examples are provided in the FX8 manual. The first PRE and first POST effect are always in series.

Parallel routing is a common method in traditional analog rigs to avoid loss of tone. There's no need to use parallel routing to prevent loss of tone quality when using Fractal Audio gear. But parallel routing makes it possible to have e.g. independent delay and reverb paths, or lets you place effects after a specific effect, not affecting the main signal. Also, on the Axe-Fx II, III and AX8, it allows you to put more effects in a preset, overcoming the limit of the maximum number of columns.

You don’t want to place 100% wet effects in a parallel path, such as Tremolo or Compressor, because dry signal will still be going through the main path and affect the effect.

If an effect is placed in parallel, bypassing that effect may pass direct signal, which, when merged with the main signal, increases the overall signal level. To prevent this, select a suitable Bypass Mode (not: THRU). MUTE OUT and MUTE FX OUT will kill effect tails, while MUTE IN and MUTE FX IN preserve tails.

FRACTAL AUDIO QUOTES


[10] If using Kill Dry you typically wouldn't use THRU. Use any of the other modes. If you want the tails use Mute Fx In or Mute In.

Firmware 25.00 and later for the Axe-Fx III (and corresponding FM3 and FM9 firmware)

Current firmware makes it easy to configure effects for operation in parallel paths. The Kill Dry parameter mutes the dry signal, and lets you keep using the Mix parameter to dial in the desired effects level. This also provides support for the Reverb and Effects Mix parameter in the Global menu. You still need to set the correct Bypass Mode to prevent an undesirable level boost when bypassing the effect, see above.

Release notes: [11]


Added “Kill Dry” control to Delay, Multitap Delay, Pitch, Plex and Reverb blocks. When set to ON the dry signal is muted. This simplifies routing these blocks in parallel. When using these blocks in parallel the user can turn Kill Dry on and set the wet level using the Mix control, leaving the Level control at 0dB. This also has the advantage that the wet level is controlled by the global Reverb/Effects Mix, if desired.

Kill Dry has also been added to the Megatap Delay block.

Before firmware 25.00 for the Axe-Fx III:

When running an effect in series, using its Mix parameter (if available) may affect the level of the dry level too. This is not the case with effects in a parallel row when Mix is set to 100% (fully wet) and using Level or Input Gain to dial in the desired effects level. So, when using effects in parallel, set Mix at 100% and use Level to dial in the desired amount of effect. With effects featuring an Input Gain parameter, you can keep Level at 0 and use Input Gain (which controls the level going into the block) to dial in the desired amount of effect. Also, setting Mix at 100% avoids creating double direct signal paths, which would result in undesirable increase of volume.

See WICKED WIKI 12: Parallel Paths and What is the "exact?" db of gain increase on muted parallel effects? in the forum for more information.

FRACTAL AUDIO QUOTES


[12] Don't think in terms of dB. Assume you are putting 1V in (for convenience). If you add two rows you get 2V out. That's a 6 dB increase. If you add three rows you get 3V out. That's a 9.5 dB increase. If you add four rows you get 4V. That's 12 dB.

OTHER QUOTES


Forum member Bakerman:

[13]: Decibels use a logarithmic scale. You need to double the voltage (paths of identical signal) to see a ~6 dB increase. 1 to 2 is doubling. 2 to 4 is doubling. 2 to 3 (voltage gain of 1.5) is only a ~3.5 dB increase.

Forum member GM Arts:

Here's a bit of trivia to cover the comments we often see along the lines of: when I combine two blocks in parallel into a single block, it gets louder... The two signals sum, so it's necessary to reduce the output levels of the two blocks so they combine without volume boost. For an equal mix, each block must be set to -6dB. What's not so apparent is what levels to use for unequal mixes, so here they are. This applies to combining two blocks that each have the same level into a single block without volume change.

-6-6dB
-5.5-6.6dB
-5-7.2dB
-4.5-7.9dB
-4-8.7dB
-3.5-9.6dB
-3-10.7dB
-2.5-12dB
-2-13.7dB
-1.5-16dB
-1-19.3dB
-0.5-25dB

Forum member DLC86:

When the mix knob is set at 50%:

Chorus: -3 dB
Compressor: -6 dB
Delay: 0 dB
Drive: -6 dB
Flanger: -3 dB
Formant: -6 dB
Megatap Delay: -6 dB
Multiband Comp: -6 dB
Multitap Delay: -3 dB
Phaser: -3 dB
Pitch: -6 dB
Plex Delay: -6 dB
Reverb: -3 dB
Ring Modulator: -6 dB
Rotary: -3 dB
Synth: -6 dB
Ten-Tap Delay: -3 dB
Vocoder: 0 dB

PRE and POST routing

PRE and POST refer to the position of effects before or after the Amp block and/or Cab block.

See Cab block for more information.

FX8 Owner's manual:


Sonically speaking, the main reason to care about PRE vs. POST is that a given effect will sound different when placed BEFORE or AFTER your amp’s preamp—the place where distortion occurs. How does this difference sound? If you’ve ever switched the sequence of traditional DRIVE and WAH pedals, you’ve heard an excellent example. In the case of wah before overdrive, the resonant filter of the wah “excites” the overdrive in a cool way while still retaining a natural overall tone. When the wah follows distortion, you might hear a more dramatic filtered sweep—with heavy distortion it can get almost synth-like—which might be considered less “classic.” It’s not surprising then that Wah would traditionally be a run as a “PRE” effect between guitar and amp. The amp’s distortion follows the wah effect. Many other effects fall in this same category. A different example is found in overdrive with reverb and delay. In the natural world, reverb and echo occur because of open spaces around your guitar amp – like a club or concert hall. These effects would therefore NOT be heard before a distorted amp, but after it. Recording studios often add these kinds of effects at the console—after the mic has picked up the distorted sound from the guitar amp. If you wanted to simulate this natural sounding reverb or delay these effects would likely be run “POST.” This is not to say that delay or reverb before distortion is a “no-no.” Many “legendary” tones came from echo units in front of an amp—but this effect is very different from “POST” delay—not only tonally, but also in terms of dynamics. The good news is that the FX8 allows you to experiment easily and find what combinations of pre- and post-effects work best for you. Creativity begins where tradition ends.

The FX8 is designed for PRE and POST hardware routing. There are 3 supported ways:

PRE — Effects between guitar and Amp.

POST — Effects after the Amp. I.e. in a real amp's effects loop, or added in a studio.

Four Cable Method (4CM) — Combination of PRE and POST.

PRE and POST chains depend on the way the FX8 is connected and is configured on the preset's CFG page. The PRE/POST effects configuration per preset is indicated at the top of the screen:

8/0 — All blocks are PRE.

0/8 — All blocks are POST.

Any other value indicates a mix of PRE and POST.

FRACTAL AUDIO QUOTES


[14] The paradigm for the FX-8 is that if you put the typical effects in the "Post" section then the level out of the Post section is the same as the level in. Therefore your effects loop is running at unity gain and the volume won't change if you bypass all the effects.

The FX8 manual contains diagrams.

Bypass mode

MUTE IN
When the block is bypassed, its inputs are muted, silencing the both wet and dry but allowing effect tails to ring out or spill over. Use this (or MUTE FX IN) for time-based effects in parallel.
MUTE OUT
When the block is bypassed, all audio is totally silenced at the outputs. Effect tails are silenced immediately, but the input is still listening so tails may be heard when you engage the effect.
MUTE FX IN
When the block is bypassed, the inputs of its internal processor are muted, but the dry is unaffected. This allows effect tails to ring. LEVEL and BALANCE and MIX controls continue to operate when the block is bypassed. Use this for time-based effects in series when you want spillover.
MUTE FX OUT
When the block is bypassed, the outputs of its internal processor are pulled, but dry signal is totally unaffected. With this setting, signals can enter a reverb or delay before it is engaged. LEVEL and BALANCE and MIX controls continue to operate when the block is bypassed.
MUTE
When the block is bypassed, both wet and dry are totally silenced.
THRU
When bypassed, the block is completely disengaged. None of its parameters have any effect on the sound; it behaves exactly as if it were never there in the first place.

The settings are explained through diagrams in the Owner's Manual:

Bypass modes.png

To set a block's Bypass state in all scenes of a preset, use the editor.

PREVIOUS GENERATIONS


[15] A bypassed block does nothing more than copy the input to the output. Any perceived changes in sound are just that, perceived.

[16] FX bypasses are done as fades but much shorter that 500 ms. More like 20 ms.

The Bypass Mode parameter on the Axe-Fx II, AX8 and FX8 can be attached to a controller. The controller will then control the block's state: engaged or bypassed. You can also use the Setup menu to switch the effect through the corresponding INIT VALUE parameter. The Axe-Fx III, FM9 and FM3 provide a dedicated Bypass parameter for this purpose.

The engaged/bypass state of an effect block can be different per scene when not connected to a controller. Read Scenes for more information.

When switching between two Amp blocks in parallel rows, make sure to set their Bypass Mode to Mute, to prevent bleed-through of dry signal from the bypassed Amp block.

Bypassing a block does NOT lower CPU usage. CPU usage only decreases when removing the block from the grid.

In firmware 21.x and later for the Axe-Fx III, and corresponding FM3 and FM9 firmware, the bypass design has been changed for blocks whose mix is hard-coded at 100%, for example, Wah, Filter, EQ, Tremolo. These blocks now bypass and engage with a gentle fade, smoothening the transition.

Mono or stereo

Read Mono and stereo for more information.

Routing tools

See these sections for more information:

Editing parameters

Reset a block

Axe-Fx III and FM9 and FM3 — Press the Reset soft button. This resets the current channel only.

Axe-Fx II — Click BYPASS twice (not EFF.BYPASS) or press-and-hold it.

FX8 — Click ENTER twice.

AX8 — Click SHIFT, then press EDIT twice.

Or use the editor to initialize the entire block, or just the channel.

Visit the Amp block page for more information about defaulting the parameters in an Amp block.

Recall Effect

The Recall Effect function lets you copy the parameters of an effect block from another preset into the current preset. The Axe-Fx II, FX8 and AX8 have this feature, the Axe-Fx III, FM3 and FM9 do not.

Axe-Fx II — On the Recall screen, press PAGE RIGHT to get to the Recall Effect page.

AX8 and FX8 — Set one of your function switches to SINGLE PRESET/BANK, press the switch, press PAGE.

Follow the instructions in the manual to load a preset. Once the "RECALL" page is visible, press the <PAGE> button. This will take you to the "EFFECT" screen. From here you can load any effect block to your current preset from any other preset on the unit

Recalling an effect:

  • Changes the engaged/bypass state of the selected effect.
  • Always includes the X and Y settings (if applicable).
  • Includes modifier settings.
  • Does not include Global block linking.

If the recalled block settings don't match the ones in the block from which they were copied (source preset), there's an issue with the preset version. See Troubleshooting below.

To recall internal controller values only, such as Envelope or LFO, scroll to Control when using Recall Effect.

Global blocks

Global blocks let you change a parameter value in all presets with the same instance of that Global block.

Read Global blocks for more information.

Channels or X/Y switching

Read Channels.

Set Bypass state across all presets

The bypass state of a block is saved per preset, not across all presets.

If you want systemwide control of the bypass state of an effect block, here's a solution:

  • Attach the Bypass parameter of the effect block to an External controller.
  • In the I/O menu, switch the external controller's initial value between 0% or 100% to change the effect's Bypass state. Or assign a switch on your foot controller to the MIDI CC of the external Controller to switch the block.
  • This works with Global and non-Global Blocks, and across all presets with the same effect block.

Library

Read Editors for more information.

Scenes

Read Scenes for more information.

Performance Pages

The Performance Pages on the Axe-Fx III, FM9 and FM3 allow fast access to system parameters and effect block parameters. There's a Global Perform page and a Per-Preset Perform page. You must use the editor to add controls to these screens.

  • Each of the Performance sections can be configured with up to 10 user-selected controls from any of the blocks found in the preset (including Controllers and system settings). Configuration of the Perform tabs are done via the editor. Allowable controls include rotary knobs, slider controls (which are displayed as rotary knobs), push-buttons, drop-downs, and toggle controls (e.g., on/off controls).
  • The editor's Perform view is accessed via the Perform button or the Tools > Performance menu.
  • Performance controls are assigned via drag-and-drop from a block's parameter view to the Perform view. To assign a block's parameter to the Perform view, click on the control's label and drag the control to the desired Perform configuration. (To assign a Perform control from the CONTROLLERS Sequencer, right-click on the Sequencer control and choose the location from the pop-up menu.)
  • Assigned controls within the Perform view can be drag-and-dropped to new locations. The Perform view supports the SWAP and MOVE operations similar to the Grid.
  • Each Performance control has two labels. To change the text of any Performance Control label, double-click it. To reset the label to its default text use the Reset Label button.
  • To remove a Performance control, select the control and press the DELETE key.
  • The Per-Preset Performance Controls are stored per-preset. Adding or removing a control from this area will change the EDIT state of the preset.
  • The Global Performance Controls are stored in the system settings. Adding or removing a control from this area automatically saves the control, without needing to save the preset.
  • The Per-Preset Performance Controls can be saved to and loaded from the Library using the arrow control in the Per-Preset Performance Controls title.
  • When the Perform view is visible, the main effect editor's controls are disabled to allow for drag-and-drop assignment to the Perform view.

Firmware for the FM3 includes a short Performance Control Pages manual and tutorial.

Tip: You can copy the Global Performance Controls to the Per-Preset controls in an empty Preset, then save the preset, and restore them at a later moment by switching back to that preset and copying them back to the Global Performance Controls pane. You can also save the Per-Preset Performance Controls to the Library and reload them later using the reveal triangle.

Also read Editors for more information.

Tempo

You can specify in the Tempo menu whether you want to the tempo to apply to all presets or per preset.

Read Tempo for more information.

Mix parameter

The Mix parameter determines the amount of wet signal in a block. At 100 the signal is totally wet. This is usually used with effects such as Tremolo and Compressor. At 0, the signal stays completely dry (no effect), with the exception of the Drive block.

Mix at 50% results in both wet and dry being at -6 db in comparison to their maximum output levels (except the Delay block because of the Delay Mix Law). Compensate by adjusting Level.

FRACTAL AUDIO QUOTES


When turning up Mix in a block, the dry signal decreases. The table below shows wet/dry dB levels at various settings for blocks like Reverb, Pitch, etc. which do NOT use a constant power algorithm (like DRIVE). The Delay also uses a different method. In a rig where unity gain matters, these numbers are used to know how much to adjust Level for a given Mix setting.


MIX
SETTING
WET
LEVEL
DRY
LEVEL
WET/DRY
DIFF
0 -∞ 0.00 -∞
5 -26.02 -0.45 25.58
10 -20.00 -0.92 19.08
15 -16.48 -1.41 15.07
20 -13.98 -1.94 12.04
25 -12.04 -2.50 9.54
30 -10.46 -3.10 7.36
35 -9.12 -3.74 5.38
40 -7.96 -4.44 3.52
45 -6.94 -5.19 1.74
50 -6.02 -6.02 0.00
55 -5.19 -6.94 1.74
60 -4.44 -7.96 3.52
65 -3.74 -9.12 5.38
70 -3.10 -10.46 7.36
75 -2.50 -12.04 9.54
80 -1.94 -13.98 12.04
85 -1.41 -16.48 15.07
90 -0.92 -20.00 9.08
95 -0.45 -26.02 25.58
100 0.00 -∞


The formula for an exact calculator is:

  • DRY LEVEL = (LOG((100-MIX)/100))*20
  • WET LEVEL = (LOG(MIX/100))*20


Forum member DLC86 created this table, which lists the required dry level reduction with Mix at 50%:

Chorus: -3 dB
Compressor: -6 dB
Delay: 0 dB
Drive: -6 dB
Flanger: -3 dB
Formant: -6 dB
Megatap Delay: -6 dB
Multiband Comp: -6 dB
Multitap Delay: -3 dB
Phaser: -3 dB
Pitch: -6 dB
Plex Delay: -6 dB
Reverb: -3 dB
Ring Modulator: -6 dB
Rotary: -3 dB
Synth: -6 dB
Ten-Tap Delay: -3 dB
Vocoder: 0 dB


Note that on the VP4 the "Mix law" is adjusted.

FRACTAL AUDIO QUOTES


[17] The mix law in many blocks is different to suit the "all effects before the amp" crowd better.

[18] The sweetened mix law places a wider range of knob motion in the portion of the curve where the delay is quieter. This replicates the way pedals that are designed for use in front of an amp work because the amp's compression reduces the difference between the quiet echoes and the louder dry signal.

Global Effects Mix

The Effects Mix parameter in the Setup menu lets you control the overall wetness of effect blocks that have a Global Mix parameter. The parameter simply multiplies the Mix value in the presets.

FRACTAL AUDIO QUOTES


[19] Global Reverb and Effects Mix are relative. If set to 0% the mix is set by the preset. If set to, say, -10% the mix would be 10% less than the preset mix.

Global Reverb Mix

There's a separate global mix parameter in the Setup menu for reverb: Reverb Mix. Note that reverbs also are effected by the Effects Mix parameter (see above). The parameter simply multiplies the Mix value in the presets.

FRACTAL AUDIO QUOTES


[20] Global Reverb and Effects Mix are relative. If set to 0% the mix is set by the preset. If set to, say, -10% the mix would be 10% less than the preset mix.

Internal controllers, External Controllers, Control Switches

Read Controllers and modifiers for more information.

Waveforms

Waveform.png

For explanations of waveforms and graphs, read the Owner's Manual and and look up Waveforms in Wikipedia.

Troubleshooting

No sound

If the device or preset doesn't produce any sound, check the following:

  • Check your cables! [21]
  • Is the latest firmware installed on the unit?
  • Is the correct Input block connected to the correct Output block on the grid?
  • Verify that Bypass Mode in bypassed blocks is not set to “Mute”.
  • Are the blocks set to channels that pass signal?
  • Does the Cab block use a cab slot that's not empty?
  • There isn't an expression pedal muting the signal?
  • Are the OUT level knobs on the hardware turned up?
  • Is Return Level in the Feedback Return block turned up?
  • Is the Scene Output Level in the Output block correctly set?
  • Isn't Gain in the Global EQ turned down?
  • Is the monitor or other amplification turned on?

Bypass corrupt preset at startup

A corrupt preset can cause problems at startup.

Axe-Fx III 
If a problematic system parameter prevents the device from booting, hold EDIT on startup to bypass non-default system settings and reset them. Press-and-hold both EDIT and HOME at startup to bypass and reset the system settings AND load a fully initialised empty preset.
FM9, FM3 
If a problematic system parameter prevents the device from booting, hold EDIT on startup to bypass non-default system settings and reset them. Press-and-hold both EDIT and HOME at startup to bypass and reset the system settings AND load a fully initialised empty preset.
Axe-Fx II XL/XL+ 
Hold down Page Left and Page Right while cycling power until the Emergency Utility menu appears. Update the firmware using Fractal-Bot.
FX8 
Hold down SETUP and power the unit on. Hold the button for about 1 second beyond the power up, then release. The unit will now allow you to install firmware using Fractal-Bot. If a problematic system parameter prevents the device from booting, press ENTER when the splash screen is displayed.
AX8 
Hold down SHIFT and power the unit on. Hold the button for about 1 second beyond the power up, then release. The unit will now allow you to install firmware using Fractal-Bot. If a problematic system parameter prevents the device from booting, press ENTER when the splash screen is displayed.

If the unit sounds bad after an update, try this: Reset system parameters

FRACTAL AUDIO QUOTES


[22] There's multiple levels of error checking. First the USB endpoint is a bulk endpoint so it has guaranteed transmission. Then each packet has a checksum. Then the entire image has a checksum. Finally the image written to the FLASH is compared to the downloaded image byte-by-byte. It's virtually impossible to have corrupted firmware image.

[23] It's virtually impossible to brick a Fractal product. All our products feature an "emergency bootloader" that allows booting the unit in the event of a failed firmware update.

Issue with Effect Recall or copy-and-paste

This applies to previous-generation hardware only:
If using Recall Effect or copy-and-paste in the editor doesn't deliver the expected results (different sound), there may be a mismatch between the preset versions. To solve this, save the source preset to update it to the latest specs, then perform the recall or copy/paste operation again. When executed, all presets stored in flash with an older version of the firmware will be upgraded to the currently installed firmware version and automatically re-saved to flash. This process can take up to 20 minutes but will speed up preset changes in some cases.

Preset appears empty

If a preset unexpectedly shows up empty, it was probably saved with firmware that is more recent than the version that is loaded on your device. Update your unit's Firmware.

FRACTAL AUDIO QUOTES


[24] Whenever there is a major revision presets created with that revision are NOT backwards compatible.

Device won't save a preset

If saving a preset to a specific preset slot on the device is unsuccessful, there may be an issue with its FLASH memory.

FRACTAL AUDIO QUOTES


[25] If it's always the same preset locations then the FLASH is going bad.

Videos