Question 1

It sounds muffled, boxed-in or dark

Accepted Answer

Double cab. The capture already contains a mic'd cabinet, and the IR Loader is stacking a second speaker on top of it. Turn the IR Loader off — turn Footswitch II past the last slot until no indicators are lit. Amp-and-cab captures have the cabinet permanently baked in and it cannot be separated. The IR's high-cut is set very low, or the mic position is dark. Move the mic position further from the centre of the cone and raise the high-cut. Mic and position selection only works on the factory IRs, not on your own uploads.

Question 2

It sounds raspy, buzzy or fizzy

Accepted Answer

No cab at all. The capture is amp-only and the IR Loader is bypassed, so you're hearing a raw amp with no speaker in the way. Turn the IR Loader on and pick a cab. The community's own diagnostic is worth memorising: if the IR is off and it sounds bad, the capture probably has no cab; if the IR is on and it sounds bad, the capture probably includes one. Digital fizz in the top end, common to all modelling. High-cut around 8–10 kHz on the IR, and low-cut 80–100 Hz to tighten the bottom. Also try less gain than feels right.

Question 3

My presets are all at different volumes

Accepted Answer

You're using the LEVEL knob, which is a global master rather than a per-preset level. Hold CAPTURE for two seconds to open the Capture Volume view, then use LEVEL there. Range is −24 dB to +12 dB, default 0.0. Save before moving on. Cloud captures are gain-staged inconsistently by whoever uploaded them, and perceived loudness tracks spectral density rather than dB — so a clean and a high-gain capture can measure the same and sound nothing alike. Level-match by ear at playing volume against a factory preset as your reference. The 25 factory captures are curated and consistent; the cloud is not. IR level differs between presets. IR level is per-preset and doesn't affect other presets using the same IR, so it's a safe second lever.

Question 4

The quarter-inch outputs sound quieter and duller than headphones

Accepted Answer

You're using TS instrument cables on balanced TRS outputs, which costs about 6 dB and some clarity. Use TRS cables, or TRS-to-XLR. An entire forum thread about the device's audio quality resolved to exactly this. Only one output is connected, so panned content is missing. Enable analog output auto-sum, added in NanOS 2.2.0, so a single cable receives a proper mono sum.

Question 5

It clips badly when I turn the cab sim off

Accepted Answer

The IR's low-pass was doing level management as well as tone shaping. Removing it dumps a hotter, full-range signal downstream. Pull the per-preset capture volume down, and add a Low-High Cut EQ in a post slot to replace the filtering the IR was doing.

Question 6

There's hum, buzz or hiss

Accepted Answer

Powering over USB-C while running unbalanced cables to other gear, which creates a ground loop. This is the documented number-one cause. Power from the DC jack with a regulated supply, or switch to balanced TRS runs — ideally both. Ground loop through the outputs. Engage the GND ground-lift switch. Full fix for some, partial for others. An undersized power supply. The device needs 600 mA minimum, and 500 mA supplies are below spec. Use 9–12 V DC, 600 mA or more, centre-negative, 2.1/5.5 mm. The Quad Cortex supply works. Owners confirm the Truetone 1SPOT, Boss PSB-1U and Cioks DC7. The capture or IR itself is noisy — plenty of cloud content is. Use the Input Gate in the Capture Volume view, and try a different capture to confirm.

Question 7

My knobs and footswitches do nothing

Accepted Answer

Parameter Lock is on. Hold EXIT for three seconds. This is common enough that Neural DSP put it in their FAQ. Knob Operation Mode is set to Latching, so a knob does nothing until it passes through the stored value. Sweep the knob through its range, or switch to immediate mode in the app's settings.

Question 8

The footswitches feel laggy

Accepted Answer

They fire on release rather than on press — deliberately, so that press-and-hold can address the tuner and tap tempo on the same two switches. There is no setting to change this and no workaround. Worth knowing it's by design, not a fault. It does genuinely hurt accuracy when starting a looper.

Question 9

There's an audible gap when I change preset

Accepted Answer

Around 60 ms of silence, introduced deliberately in NanOS 2.0.0 to allow the flexible signal chain. Delay and reverb trails do continue across the change. Keep the modulation, delay and reverb identical across all four presets — several owners report this makes it inaudible. Better still, switch effects via expression pedal or MIDI CC, which isn't a preset change and so has no gap.

Question 10

I can only reach four presets with my feet

Accepted Answer

By design. There are 64 presets but only two footswitches, giving IA/IB and IIA/IIB. The BANK button moves through capture banks, not preset banks, and it's hand-operated. Add a MIDI foot controller over TRS MIDI Type A — presets map automatically to Program Change 0–63. Neural DSP staff have endorsed the Nektar Pacer, Morningstar MC6, Behringer FCB1010, Harley Benton MP-100 and Fortin Hydra. Otherwise, build a setlist around four combined sounds.

Question 11

The cab block keeps switching itself off mid-rehearsal

Accepted Answer

A confirmed bug with MIDI over the TRS port: the controller sends CCs that the cab and capture blocks mishandle. Neural DSP support has acknowledged it as a known issue with a fix planned and no date. Drive MIDI over USB-C instead, which costs you the audio-interface use of that port. There is no other workaround.

Question 12

I can't play backing tracks over Bluetooth

Accepted Answer

Bluetooth on this device is for pairing with the Cortex Cloud app only. There is no Bluetooth audio and no wireless headphone support. Send audio over USB-C from a phone, tablet or laptop — iOS works well, Android is reported to crackle and isn't supported. Alternatively use an FRFR with its own Bluetooth or aux, or a small mixer.

Question 13

The app won't connect over Bluetooth

Accepted Answer

The unit isn't in pairing mode. Hold EXIT and CAPTURE together for one second. The GAIN ring sweeps clockwise and the Footswitch I LED blinks slowly. Then choose Add New in the app. On Android, the app lacks Location permission, which BLE scanning requires. Grant Location permission to the Cortex Cloud app. Stale Bluetooth state. Power-cycle the pedal and restart the phone. No firmware fix has been announced.

Question 14

It won't turn on

Accepted Answer

A bug in NanOS 2.2.0 could prevent booting when an expression or MIDI pedal is connected. NanOS 2.2.1 exists specifically to fix it. Unplug the expression or MIDI pedal to boot, then update to 2.2.1 or later. Power. USB-A cannot run this device, and undersized supplies cause intermittent failures. Use 9–12 V DC at 600 mA or more, or a genuinely USB-C-compliant 5 V / 1.5 A source. Data works over USB-A but power does not.

Question 15

My DI track is very quiet in the DAW

Accepted Answer

There is no input gain control on the device, and the operating system's input level for it defaults low. Raise the input volume in your OS sound settings for the Nano Cortex before opening your DAW. On macOS that's System Settings → Sound → Input.

Question 16

Audio stutters or drops out over USB

Accepted Answer

Connected through a USB hub. Connect directly to a motherboard port. Neural DSP explicitly discourages hubs. Powered from USB and an external supply simultaneously. Use one power source. One owner's glitching vanished when they removed the second. Session sample rate isn't 48 kHz. The device is fixed at 24-bit / 48 kHz. Set your session to match rather than resampling.

Question 17

The capture fails with a level error

Accepted Answer

There's a separate sanity check during the capture itself, stricter than the calibration meter. Green LEDs during calibration do not guarantee the capture will pass. Lower the source device's output rather than the Nano's gain, and drop capture gain significantly even if the meter then reads blue. One owner needed four attempts. Solid-state gear triggers this more readily than tube amps. BOOST engaged with GAIN already up. Set GAIN to minimum before engaging the +26 dB BOOST. Neural DSP repeats this warning in three separate documents.

Question 18

My capture doesn't sound like the real thing

Accepted Answer

The IR Loader was engaged while capturing, baking a second cab in. Turn the IR off before capturing, and A/B with Footswitch I as you go. Capture level was too low, which repeatedly shows up as captures with less gain than the source. Recalibrate for a solid green reading, and expect to take several attempts. You're capturing a software amp sim. Multiple owners report captures of plugins missing distortion and sounding wrong, while pedal captures work fine for the same people. No resolution has been published for this. Treat plugin capturing as unreliable on this device.

Question 19

I want to put my own pedals in the loop

Accepted Answer

There is no effects loop on this device. Either capture the external preamp and load it into the capture slot, or save a preset with no capture active and run your real pedal in front, using the Nano only for cab, delay and reverb. Never route a speaker-level signal back into it.

Question 20

My Quad Cortex presets won't load

Accepted Answer

Presets are incompatible — the Nano's fixed chain can't represent Quad Cortex routing. Captures, however, are fully interchangeable and officially the same resolution. Since November 2025 over a thousand Quad Cortex factory captures are available to Nano owners, and NanOS 2.2.0 added a Capture V2 player. Note the Nano can play V2 captures but cannot create them.

Troubleshooting

The four that destroy hardware