View source for Zery uninteresting wiki sandbox

===Tidbits===
* TOC
* * faq
* crosslinks
* redirects
* pic
* layout (template)

<blockquote>[...]</blockquote>

To change which page is the main page, in the search bar, type MediaWiki:Mainpage. Then edit it so its content is the name of the page you want to be the main page. MediaWiki:Mainpage should always contain the title, because it is a system message that is reserved for the title of the main page, so don't change it to MediaWiki:x.

<code>Menus</code> and <code>keyboard</code>

[[mediawiki:sidebar|Sidebar]]

[[mediawiki:sitenotice|Sitenotice]]

<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2;font-size:85%">
</div>

[[Special:Random|random page]]

[http://wiki.fractalaudio.com/axefx2/index.php?title=Category:All category ALL]

embed/transclute page:
{{:}}

Example:

{{:Soon}}

<font size=1>Font Size 1</font>
<font size=2>Font Size 2</font>
<font size=3>Font Size 3</font>
<font size=4>Font Size 4</font>
<font size=5>Font Size 5</font>

{| class="wikitable"
|-
! '''Parameter'''
! '''Axe-Fx III'''
! '''Axe-Fx II'''
! '''AX8, FX8'''
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
!
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|-
| 
! 
! 
! 
|}

----
A very uninteresting test edit by iaresee

====Really Righteous Reading and References====

Become accquainted with this page, then see the following pages for more information:

Start here and do NOT pass Go. Do it. You know you want to….
* WikiMedia's <q>[https://en.wikipedia.org/wiki/Help:Sandbox_tutorial#:~:text=Creating%20a%20sandbox&text=You%20can%20do%20this%20by,summary%2C%20and%20press%20Publish%20changes%20. Help:Sandbox tutorial]</q> pages.

At this point the world is your oyster, use your brand-spankin' new sandbox for any experimenting or editing…

* WikiMedia's <q>[https://wiki.fractalaudio.com/wiki/index.php?title=Help:Editing Help:Editing]</q>.
* The W3.org's <q>[https://www.w3.org/WAI/tips/writing/#make-link-text-meaningful Writing for Web Accessibility]</q> page.
:In particular this is important:<blockquote><q>Write link text so that it describes the content of the link target. Avoid using ambiguous link text, such as ‘<u>click here</u>’ or ‘<u>read more</u>’. Indicate relevant information about the link target, such as document type and size, for example, ‘<u>Proposal Documents (RTF, 20MB)</u>’.</q>:
:This is bad:<blockquote><q>For more information on device independence, <u>click here</u>.</q></blockquote>
:This is good:<blockquote><q>Read more <u>about device independence</u>.</q></blockquote>
</blockquote>
:A Wiki's content tagging system makes it really easy to create links that fail to tell the user what is a the far side of a link, especially when used with alternate devices like screen readers.
* Similar to the previous, WebAIM's <q>[https://webaim.org/techniques/hypertext/link_text Links and Hypertext/Introduction to Links and Hypertext]</q> goes into much more detail describing how link-text should be written.
* And, similar to that, there's the Nelson Norman Group's article <q>[https://www.nngroup.com/articles/title-attribute Using the Title Attribute to Help Users Predict Where They Are Going]</q>.
* Wikipedia's <q>[https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references List of XML and HTML character entity references]</q> article.
* Apple Support's <q>[https://support.apple.com/guide/mac-help/what-are-those-symbols-shown-in-menus-cpmh0011/mac What are those symbols shown in menus on Mac?]</q> page.

====CSS Styles====
'''Before you begin:'''

See:
* https://wiki.fractalaudio.com/wiki/index.php?title=MediaWiki:Common.css for the definitions in our Wiki.
* https://en.wikipedia.org/wiki/Wikipedia:About_the_sandbox for instructions to create a <q>sandbox</q> for testing edits and CSS.
* https://en.wikipedia.org/wiki/Help:User_style for instructions on how to create a <q>custom.css</q> file for your own sandbox.

'''Keycaps''': <kbd class="keycap">Command</kbd>
<pre><kbd class="keycap">Command</kbd></pre>

These are mostly used in the [[Editors]] page, particularly in the [[Editors#Keyboard_shortcuts|Keyboard shortcuts]] section.

'''Application Button''': <span class="button">A button</span>
<pre><span class="button">A button</span></pre>

'''NOTE:''' The following uses of <kbd>&lt;samp&gt;</kbd> and <kbd>&lt;code&gt;</kbd> should probably be changed to <kbd>&lt;span&gt;</kbd> with an appropriate "<kbd>class</kbd>" defined. Currently they're relying on the default MediaWiki CSS styling, which results in us being at their mercy if they change something. We should be the masters of our own destiny, or the creators of our own version of hell, something like that. It doesn't take a lot of work to let vim walk through the Wiki pages and replace occurrances if it seems the thing to do. - Greg Ferguson

The '''<kbd>&lt;samp&gt;</kbd>''' tag:

<pre><samp>This is something typed into the computer, or a file .ext</samp></pre>

is rendered as:

<samp>This is something typed into the computer, or a file .ext</samp>

The '''<kbd>&lt;code&gt;</kbd>''' tag:

<pre><code>Something from the interface/menus in Edit or Cab-Lab</code></pre>

is rendered as:

<code>Something from the interface/menus in Edit or Cab-Lab</code><br>

====Double and single quotes====
Use, and convert, straight single and double quotes when they're outside of a direct quotation. They look better.

<code>&amp;ldquo;Some text&amp;rdquo;</code> creates a matching pair of curly double quotes that looks like <code>&ldquo;Some text&rdquo;</code>. 

As a shortcut and a benefit from browsers and HTML rendering, we can usually use <code>&lt;q&gt;</code> to accomplish the same thing but it's dependent on a user's settings and the font they're using.

<code>&amp;lsquo;Some text&amp;rsquo;</code> similarly creates a matching pair of curly single quotes that looks like <code>&lsquo;Some text&rsquo;</code>.

====Quoting comments from the forum====

* To try to provide some continuity with the forum's quote style we changed the Wiki to call out <kbd>&lt;blockquote&gt;&lt;blockquote&gt;&lt;p&gt;…&lt;/p&gt;</kbd> wrapped blocks. See the CSS page mentioned above for the styling information. 
* The <kbd>&lt;p&gt;</kbd> is automatically supplied by the Wiki, we don't need to add it explicitly.
* We don't change spelling or grammar in the quotes we harvest, those are for the original speaker to change. Nor do we change any single or double quotes or other punctuation they supply.
* We can, and probably should, fix copied then pasted text if it mangles the original formatting used by the speaker because that helps convey the same intent that their using of formatting supplied. Often we see paragraphs running together which definitely can mess with the readability of the content.
* We should leave as little trace of our harvesting as possible.

'''Note:''' See the above note about using <kbd>&lt;span&gt;</kbd>, only switching to <kbd>&lt;div&gt;</kbd>, for the same reasons.

=====Fractal Audio Quotes=====

The standard quoting for FAS employees is:

<blockquote>
'''FRACTAL AUDIO QUOTES'''
<hr>

<blockquote>
[some url to the quote]
[…] if the text is a partial quote

Some sort of quote

A second paragraph of the quote.
</blockquote>
</blockquote>

And created by:

<pre>
<blockquote>
'''FRACTAL AUDIO QUOTES'''
<hr>

<blockquote>
[some url to the quote]
[…] if the text is a partial quote

Some sort of quote

A second paragraph of the quote.
</blockquote>
</blockquote>
</pre>

=====Other Quotes=====

Quotes of non-FAS employees look like:

<blockquote>
'''OTHER QUOTES'''
<hr>

The name of whoever said it:
<blockquote>
[some url to the quote]
[…] if the text is a partial quote

Some sort of quote from someone not affiliated with Fractal.

A second paragraph of the quote.
</blockquote>
</blockquote>

And are created using:
<pre>
<blockquote>
'''OTHER QUOTES'''
<hr>

The name of whoever said it:
<blockquote>
[some url to the quote]
[…] if the text is a partial quote

Some sort of quote from someone not affiliated with Fractal.

A second paragraph of the quote.
</blockquote>
</blockquote>
</pre>

=====Previous Generations=====

If we want to specifically call out comments for previous generations of the hardware, such as when it conflicts with the current generation, use:

<blockquote>
'''PREVIOUS GENERATIONS'''
<hr>

What hardware or app:
<blockquote>
[some url to the quote]
[…] if the text is a partial quote

Some sort of quote that is specific to a previous generation.

A second paragraph of the quote.
</blockquote>
</blockquote>

which is created using:

<pre>
<blockquote>
'''PREVIOUS GENERATIONS'''
<hr>

What hardware or app:
<blockquote>
[some url to the quote]
[…] if the text is a partial quote

Some sort of quote that is specific to a previous generation.

A second paragraph of the quote.
</blockquote>
</blockquote>
</pre>

=====Combining sections=====
Sometimes we have multiple quoting blocks we need to incorporate. It's easy-peasy; don't totally close, then reopoen the blockquoting, just close the immediate level, insert the new heading, then begin quoting. Fer instance:

<pre>
<blockquote>
'''FRACTAL AUDIO'''
<hr>

<blockquote>
Stuffs…
</blockquote>

'''OTHER STUFFS'''
<hr>
<blockquote>
More blah
</blockquote>
</blockquote>
</pre>

Which, in real life, looks like:
<blockquote>
'''FRACTAL AUDIO'''
<hr>

<blockquote>
Stuffs…
</blockquote>

'''OTHER STUFFS'''
<hr>
<blockquote>
More blah
</blockquote>
</blockquote>


----

===SANDBOX from here down===
----

FAQ:

=TOP 3 tips!=

# Check your cables.
# Check your cables.
# Check your cables.

The trouble is [https://forum.fractalaudio.com/threads/if-you-read-nothing-else-read-this.162537/ almost always a cable], connector, a volume knob setting, an exhausted battery, or something else very basic.

[https://forum.fractalaudio.com/threads/if-you-read-nothing-else-read-this.162537/ If you read nothing else, read this!]

[[image:Cable.jpg|100px]]

=AC Line Frequency: set for your country=

If you are using the Axe-Fx III, FM9, or FM3 in a region where AC power frequency is 50Hz instead of 60Hz, change the AC Line Frequency setting in the [[Setup menu]] for better noise gate control. Read this: [[Noise gate]]

=CPU: stay below 80%=

Keep CPU usage below the value mentioned in the [[Owners Manuals]] (around 80%). Read this: [[CPU usage]]

= Double-clicking a control in the editor does not recall the correct default value =

When double-clicking a control in the editor, it gets reset to a default value, not necessarily the default value. Only a soft-reset of the amp type (re-select) or a hard reset of the block or channel pulls the correct values from the hardware.

= Emergency boot recovery=

If, after installing new firmware, the unit no longer boots, invoke the [[Emergency boot recovery]], then use [[Fractal-Bot]] to reinstall the [[Firmware]].

=FASLINK issues=

If the [[FC-6 and FC-12 foot controllers]] won't power on properly, or if the processor shuts down or starts blinking all lights, it's almost certainly caused by the cable. Use another standard microphone cable instead. Read this: [[FASLINK]]

= FRFR, what's that? =

[[FRFR]] = full-range, flat response. This acronym is used to describe a “neutral” speaker or speaker system that is designed to reproduce the entire audible spectrum of 20 Hz – 20kHz without emphasis or de-emphasis. Examples of FRFR systems would include studio monitors and properly designed PA systems or components. Many manufacturers are also offering FRFR systems designed specifically for direct guitar applications. Read this: [[Audio in and out]]

=Global blocks won't stick=

This applies to the Axe-Fx III only: if changes to [[Global blocks]] do not longer seem to stick, or the values are off, there's no available storage space anymore.

=Hardware I/O test=

Here's how to test the input and output ports: [[Realtime Analyzer block]]

= Humbuster: which end of a cable goes where =

A [[Humbuster]] cable has a "mono" (one stripe) and a "stereo" (two stripes) end. The 'stereo" end goes into the output of the Fractal Audio device.

=Input 1 is clipping=

If a warning appears about input clipping, turn down Input 1 / Instrument Level in the [[Setup menu]]. Read this: [[Audio in and out]]

= Leaving the device switched on: is it bad? =

[http://forum.fractalaudio.com/threads/left-my-axe-fx-iii-on-a-little-too-long-oops.147864/#post-1748609 No, it doesn't]

= Mobile app: is there one? =

Use [[Third-party_software|FracPad]] to control the device on a tablet or smartphone.

= New to modeling, where do I start? =

Read [[Beginners]] and the official [[Owners_Manuals|Owner's Manual]]

The [https://forum.fractalaudio.com Fractal Audio Systems user forum] is where users gather to help each other and discuss various topics related to Fractal Audio and their products. The [https://forum.fractalaudio.com/forums/read-me.57/ Read Me] and [https://forum.fractalaudio.com/threads/forum-rules.25484/ Forum Rules] pages are recommended first stops.

=No sound=

[[image:hear.png|link=]]

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

* CHECK YOUR CABLES!
* Device has the latest firmware installed?
* Input is connected to Output on the grid through blocks or shunts?
* Bypass Mode in bypassed blocks is not set to “Mute”?
* The physical output corresponds with the Output block instance on the grid?
* Blocks are set to the correct channel?
* The Cab block doesn't point to an empty user cab slot?
* Volume block with an attached controller is not set to zero volume?
* Output level knobs on the hardware are turned up?
* FX8 has the correct "pre/post" preset config?
* The Return Level in the Return block is turned up?
* Noise Gate (in Input block or separate block) doesn't have its Threshold set too high?
* Scene output level in Output block is turned up?
* Digital audio: USB Level or AES / SPDIF is turned up in I/O?
* Gain in the Global EQ isn't turned down?
* Monitors or other amplification is turned on?

=Power on issues=

* [[Firmware#Emergency_boot_recovery|Emergency Boot Recovery]]
* [[Presets#Bypass_corrupt_preset_at_startup | Bypass a corrupt preset at startup]]
* [[Reset system| Bypass global parameters at startup]]
* [[Presets#Preset_appears_empty|Presets appear empty]]

=Reference sound clips=

[https://forum.fractalaudio.com/threads/soundclips-for-reference-purpose.174944/ Go to this forum thread] to hear sound clips of a factory preset (Plexi) without any tweaks, EQ-ing etc whatsoever, recorded with different guitars. This provides a reference when you think there might be something wrong with your rig.

=Reset system parameters=

[[Reset system|Resetting the system parameters]] can solve mysterious issues.

= Sample rate: can I change it? =

[[Audio in and out#Sample_rate_fixed_at_48kHz| No]]

=Can I copy a scene into another preset=

No.

= Second-hand unit =

* Make sure the device is connected correctly. Read this: [[Audio in and out]]
* Download and install the software driver for the device to work with your computer, if required. Read this: [[USB]] and [[Firmware]]
* Install the [[Editors|editor]]
* [[Reset system]
* Download the latest set of [[Factory presets]] and install them using [[Fractal-Bot]]

=Signal flow: use the meters=

The Axe-Fx III, FM9, and FM3 make it easy to see if (and where) the signal flow is interrupted:

# Go to Layout > Meters to see the meters for all blocks on the grid.
# Check the Input and Output meters on the front/top panel to verify that there’s an input and output signal.
# Check the blocks to detect any issues. The top two rows indicate the incoming stereo signal, the bottom two rows indicate output.

[[image:Cpu2.jpg|200px]]

= Sound is harsh and brittle =

* Perhaps you disconnected an expression pedal that controlled your Wah, and now all your presets with a Wah block have the Wah enabled.
* Verify that Power Amp Modeling in the [[Setup menu]] is not turned off.
* Verify that Cabinet Modeling in the [[Setup menu]] is not turned off.
* If you're hearing crackling noises, check the CPU usage of the preset.

= Sound at rehearsals and gigs is not as great as at home: what can I do? =

There are multiple possible reasons:

* Broken cable
* The characteristics of [[Audio in and out#Close-miking|closed-miking]]
* [[Fletcher-Munson]]
* Amplification

[[Beginners| Luckily, you can do something about it]]

=Test tone=

If you want to make sure that the hardware is capable of generating sound, create a simple test tone:

# Add a Synth block and connect it to the grid output.
# Select the Sine waveform and turn off Tracking.

= Thump: how can I get that from my traditional guitar cabinet? =

A modeler doesn't interact with a solid state amp and a traditional guitar cabinet in the same way that a tube power amp does. To get the traditional speaker cab to resonate, select an appropriate speaker impedance curve in the [[Amp block]] or detect the frequency at which your cabinet starts to resonate. To do the latter, use of these methods:

# Use a dedicated hardware meter (like from Daytona Audio) to measure the speaker.
# Send a Sine wave (using the Synth block) to the speaker and change the frequency until you hear and feel the speaker resonate. Set Low Resonant Frequency in the Amp block to that frequency.
# Disable the Cab block in the preset. Add a Filter after the Amp block, set to Peaking, Q at 5 and Gain at 10 dB. Start at 50 Hz, play some chugga-chugga (or use the Looper) and slowly adjust the frequency until you hear and feel the cabinet resonate. Remove the filter block, set the Amp block's Low Resonant Frequency to match.

=Tuner is off=

If the tuner seems off, and the device is digitally connected to another device, change the sample rate of the other device to 48kHz.

= Tuner screen doesn't appear=

Make sure that the Tuner is set at its first page.

= USB Audio / AES / SPDIF signal level is too low  =

Adjust the Return Level parameter in the [[Setup menu]].

=TO DO:=

== When will the editor be updated to match the firmware that just has been released? ==

"[[Soon]]". Editor updates are provided once a new, non-beta, firmware has been released. Editor updates usually lag by no more than a couple of business days.

== I updated to the beta/recent release firmware, and I don't see the new feature in the editor? ==

Sometimes a new version of the editor has to be released and installed to support the new firmware feature. Wait for the release.

== I installed an updated editor, but it still doesn't seem to work right? ==

If you installed the updated editor that was released to support the new feature, and it won't work as expected, [[Editors#Editor_updates| refresh its definitions]].

== Where can I get a copy of older versions of the firmware or editor? ==

Try the [http://archive.axefx.fr/AxeFX%20III/Firmwares/ AxeFX Archive] site.

== Do I need to reset the Amp blocks in my presets after updating the firmware? ==

Only if the firmware release notes tell you to do so. Read this: [[Amp_block#Resetting_the_amp|Reset Amp]]

== Where can I find the names of the real amps on which the models are based? ==

Read this: [[Amplifier models list]].

For in-depth information about each amp model, read: [[Yeks_Guide_to_the_Fractal_Audio_Amp_Models|Yek's Guide to the Fractal Audio Amp Models]]

== Where can I find more information about the stock cabs? ==

Read this: [[Cabinet models list]].

== Why doesn’t this virtual amp model sound the same as my real amp? ==

The sound of a traditional amp (combo or head + cab) is often referred to as: amp in the room. The use of a speaker cabinet with its specific directional characteristics, not being miked, differs greatly from a close-miked speaker, captured as an IR, which is then used in a direct signal going to a mixer or studio monitors or FR amplification.

The direct signal has more lows and highs too because of the proximity effect (distance between mic and speaker). Also, the directivity of studio monitors and FR speakers differs greatly from guitar speakers.

If you want the same sound, use the FAS modeler without cabinet modeling and amplify it:
* with Power Amp Modeling enabled: through a neutral power amp and a traditional guitar cabinet
* with Power Amp Modeling disabled: through a traditional guitar tube amp and a traditional guitar cabinet.

== Is a generic preamp-only or power amp-only amp type available? ==

No. But you can disable the power amp section of any [[Amp block]]. In Cygnus firmware, there's a dedicated switch for this. And you can use the TUBE PRE amp model to operate either as a generic preamp or power amp block.

== What happens when I reset an Amp block? ==

A soft reset (performed by re-selecting the amp type) resets most of the parameters. A hard reset resets all parameters. Read this: [[Amp_block#Reset_the_amp|Amp reset]]

== Is it possible to show (only) the amp controls that are present on the modeled amp? ==

Set Tone Control Display to: Authentic.

== How do I return to a scene in the state I left it? ==

The default behavior for recalling scenes is that the blocks are recalled in their stored states. Scene Revert in the [[Setup menu]] lets you change this. Set this to ON, to be able to return to a scene in the state you left it.

== How do I import a preset created on another FAS product? ==

With Fractal Audio current guitar processors presets are cross-compatible. [[Third-party_software|FracTool]] offers additional conversion functionality.

== Can I overwrite factory presets? ==

Yes. Factory presets occupy regular preset slots, which are not read-only.

== How do I reload a factory preset? ==

Read this: [[Factory presets]]

== How do I copy a channel? ==

The editors for the Axe-Fx III, FM9 ands FM3 let you copy a single channel through the Channel menu at the bottom of the window. You can also use the Layout > Tools menu on the hardware. At the time of writing, swapping channels is not supported.

== Can each scene within a single preset contain different blocks? == 

No. A preset always has 8 scenes, and all scenes have the same routing and block.

You can do the following per scene:
* set the bypass state of each block
* control the output level of the scene
* set a block to X or Y, or on the Axe-Fx III / FM9 / FM3: to a specific channel.
* set scene controllers
* name scenes

== Input Level in I/O menu: does it prevent output clipping or make the signal softer or louder? ==

No. Input Level in the [[Setup menu]] lets you the optimal input level for SNR: Signal to Noise Ratio. It does NOT prevent output clipping (indicated by the output LED) and it does NOT make the signal softer or louder and it does NOT change the gain of the amp.

== What's phase cancellation or comb filtering, and why should I worry? ==

Read this: [[Audio_in_and_out#Mono_and_stereo_audio|Mono and stereo audio]]

== Why does the volume decrease or increase when I bypass an effect in a parallel row? ==

You have to set the parameters correctly for a single effect in as parallel row. Set Mix to 100%, Bypass Mode to Mute In, and set Level as desired (or set Level to 0, and adjust Input Gain). Read this: [[Presets#Series_and_parallel_routing|Series and parallel routing]]

== How do I lower the CPU usage of a preset? ==

Read this: [[CPU usage]]

== Why should I place an effect before (PRE) or after (POST) the amp or cab? ==

Sonically speaking, the main reason to care about PRE vs. POST is that a given effect will sound different when placed BEFORE or AFTER the amp (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 produce 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.

== Why is my block stuck in bypass mode? ==

The most likely culprit is that you have a modifier assigned to a parameter in the block that is set to [[Auto-Engage]] the block when you change the external controller associated with the block. For example, you have a Wah block with an external controller assigned as a modifier of the Control parameter in the block. In that modifier definition you've set up [[Auto-Engage]] so the wah block turns on when you rock the expression and off when you return the pedal to the "toe up" position. These settings would prevent you from un-bypassing or bypassing the block using any other means other than rocking or parking the expression pedal.

== Where do I find the Metronome settings? ==

In the Tempo menu.

== Does the device provide a Limiter? ==
 
In the Compressor block, set Ratio to Infinity" to turn it into a limiter. Read this: [[Compressor block]]

== Why don't I hear repeats from the 2290 delay type? ==

The 2290 delay type has phase on one side reversed and must be heard in stereo. If the signal is summed to mono after the Delay block, delay repeats will disappear because of phase cancellation.

== Why can't I adjust the time (milliseconds) in a Delay block? ==

If the Delay block is set to a specific Tempo, e.g. "1/4", you can't adjust the number of milliseconds.

== How do I boost the volume level of my solos? ==

Add a "null" Filter or a GEQ block at the end of the chain, with increased Level (try 3 to 4 dB).

==Why don't the fuzz models sound and respond as their real counterparts? ==

The Fractal Audio device acts as a buffer and many fuzzes don't like that, because they depend on direct interaction with the guitar's pickups. It's the same with the virtual fuzz models. To improve the authentic behavior of a virtual fuzz model, make sure it's the first non-bypassed block following the Input 1 block and the input block impedance must be set to Auto. Read this: [[Drive_block]]

==Where do I find more information about a Drive model?==

Read this: [[Drive block]]

== Why am I hearing clicks and crackling noise in my preset? ==

Check the CPU usage of the preset. If it's above the limit then crackling noises may occur. Read this: [[CPU usage]]

If you hear a tick in your audio signal which syncs to the tempo, and it's not the Metronome, it's probably MIDI noise bleeding into the signal. You can easily check this by turning off Send Realtime Sysex in the Setup menu. If the noise stops, it's indeed caused by the MIDI cabling. Use better MIDI cables and keep the MIDI cables away from problematic sources.

== The Axe-Fx III display shows several lines of text information on startup. Is this normal? ==

Yes.

==Why is the output level of the Axe-Fx III lower than that of the II? ==

The default nominal output level of Output 1 and 2 on the Axe-Fx III is -10 dBv. This was done to reduce the number of support cases due to people overloading the inputs on consumer-grade interfaces, mixers, etc. Most professional gear runs at +4 dBu, so when using a pro-grade interface, mixer, etc., you may want to go into the I/O menu and change the Output Level to +4 dBu.

== I want to use Input/Output 2, 3 or 4 as an effects loop but I don't hear the signal ==

Turn up the output level knob on the front panel.

== FAQ on the Fractal Audio forum ==
Read the [https://forum.fractalaudio.com/threads/fm3-faq.158819/ FM-3 FAQ] in the forum.

== Why doesn't the editor or Fractal-Bot recognize the unit? ==

On some computers the editor and Fractal-Bot will work only if a driver has been installed. Check the system requirements and download the driver from Fractal Audio's [http://www.fractalaudio.com/support/Downloads downloads page] if needed.

== Does the editor allow offline editing? ==

No. The editor must be connected to the hardware to operate. This is a design choice which is unlikely to change.

== Why do I have to press Save twice when changing the preset title? ==

You don't have to do that. When editing the preset title field, make sure to press Enter to make the editor aware of the title. Then press Save to store.

== How do I use Manage Presets and Manage Cabs? ==

<code>Manage Presets</code> and <code>Manage Cabs</code> use a Browser pane at the left of the window. To show or hide the Browser pane click on the Browser menu at the top-left of Axe-Manage and choose "<code>Show / Hide</code>". Or use the key sequence <kbd>CTRL</kbd>+<kbd>B</kbd> on Windows or <kbd>CMD</kbd>+<kbd>B</kbd> on MacOS.

== Do I have to convert IRs in <kbd>.wav</kbd> format before using them in an editor? ==

No. The editor can import <kbd>.wav</kbd> files directly. Simply drag-and-drop any number of <kbd>.wav</kbd> files into the Browser pane to allow conversion. From the Browser pane you can now either Auto-Audition the files to a Scratchpad or drag from the Browser pane to a User cab slot.

To convert a batch of Wave files, use [[Cab-Lab]].

== Expression pedal ==

see:
https://wiki.fractalaudio.com/wiki/index.php?title=Expression_pedals_and_external_switches#Tips.2C_tricks_and_troubleshooting