Troubleshooting

If something is not working as expected, start with the checks in the relevant section. Change one thing at a time and retest with a simple factory rig. That makes it easier to separate a connection problem from a device or rig problem.

No audio or no output signal

Turn the monitoring level down, then confirm the instrument, output, and power connections. Passive guitar and bass pickups belong on the instrument input side of IN 1 or IN 2. See Connections.
Open the menu and choose Mixer. Play and watch the meter for the input you connected. Raise that input gain only as needed. If there is no input activity, try another cable and instrument before changing the rig.
Check the meter for the physical output you connected. Raise its level and the external speaker, mixer, or interface level gradually.
In Rig Mode, confirm the chain’s IN and OUT blocks are active. A bypassed endpoint dims the whole chain and shows a warning triangle.
Confirm that required devices are not bypassed. For an FX Loop, also confirm that the selected return is connected and producing signal.
Load a factory rig. If the factory rig works, the problem is in the original rig. Bypass or remove its devices one at a time until audio returns.

If the input meter moves but the output meter does not on a simple factory rig, note the rig name and the last action you took before reporting the problem.

Clicks, pops, or dropouts

The CPU meter at the top of the screen shows how much audio processing time is in use. A dropout occurs when the audio thread misses its deadline.

Remove or bypass the most demanding devices first. Amp models, convolution, cabinets, and long reverbs generally cost more than boosts and simple EQ.
If the problem began after adding a third party plugin, test the same rig without it. Third party plugins do not all meet Axion’s audio deadline.
Close unnecessary editing activity and test without rapidly moving several parameters at once.
Open Settings, choose Audio Engine, and select a larger supported buffer size when the rig must remain complex. The new size takes effect after the next Axion startup and increases latency.
Test a factory rig. Dropouts on every factory rig point to a system or audio hardware problem rather than an overloaded user rig.

MIDI does not select the expected rig

Confirm the controller’s MIDI Out is connected to Axion MIDI In and that both devices are powered.
Send Bank Select before Program Change. The bank chooses the set list and the program number chooses the rig within it.
Remember that bank 0 is reserved for factory rigs. User set lists begin at bank 1.
Check whether the controller displays MIDI values from 1 to 128 while sending protocol values from 0 to 127. An apparent one slot offset usually comes from that display convention.
Test with one direct controller connection and a simple program change before adding MIDI routing through a DAW or another device.

For the addressing model, see Rigs and Set Lists.

WiFi or companion app connection problems

Open Settings and select General. The page shows the current Device IP and WiFi state.

Confirm WiFi is on and select the intended network. Secured networks prompt for their password.
Confirm the computer and Axion are on the same local network. Guest networks often prevent devices from talking to one another.
Enter the Device IP shown by Axion in the companion app. If discovery by name fails, the numeric IP avoids local name resolution problems.
If the IP changes after reconnecting or restarting the router, use the new value shown in Settings.
Temporarily disable a computer VPN or restrictive firewall only long enough to determine whether it blocks local connections, then restore the security setting and add a narrow local network exception if needed.

Software update and recovery

Use Settings, then Software Update to check for and install an update. Keep Axion connected to power while it downloads and restarts. The update system returns to the current working version automatically if installation does not complete successfully.

If the interface stops responding but audio continues, avoid repeated control changes and allow any visible update or reset operation to finish. If Axion does not return to its normal screen after a restart, record what appears on the display and report it. There is no user data recovery operation that requires opening the unit.

Factory reset

Factory reset is a last resort for damaged user content or configuration. It does not remove the factory amps, cabinets, impulse responses, or effects.

Open Settings, choose System, select Factory Reset, read the warning, and confirm. The audio engine restarts while the interface remains open.

Factory reset permanently erases all user set lists, rigs, saved device presets, captures, and songs. It cannot be undone. Export anything you need before resetting.

Report a bug

Use the Axion issue tracker and include:

The build number from Settings, System, About
Clear steps that reproduce the problem
What you expected and what happened instead
The rig, device, or plugin involved, including whether it is first party or third party
Photos, a short recording, or exported rig data when they help demonstrate the issue and contain no private information

For audio problems, say whether input and output meters moved, whether a factory rig worked, and whether the CPU meter was near its limit. For network problems, include the connection method and error message, but never post a WiFi password or other credential.