Devices · sources · Method
how these guides are made
How these are made
four rules on every page
Deep, sourced guides to the guitar modelers you own.
Gridleak's device pages are independent, deeply-sourced manuals for guitar amp modelers: interactive control maps, signal chains, rig setup wizards, tone recipes and troubleshooting references, with a source on every claim.
every source, then a citation on every claim
Manufacturer documentation, firmware release notes, dealer specs, professional reviews and thousands of owner reports, read in full, then cross-checked. Each fact carries where it came from and how well evidenced it is. Anything we can't confirm is marked unverified.
version-stamped against firmware
Each guide says which firmware release it is checked against. When a release changes what's true, the guide says which older advice it invalidated.
interactive where a table won't do
Clickable control maps, signal chains you can inspect slot by slot, and setup wizards that turn “what am I plugging into?” into actual settings.
open about what is unknown
Reading every source shows where they disagree. Where a manufacturer's own documents contradict each other, we show both sides of the conflict.
the sourcing method
every source, not one opinion
A guide written from a single modeler describes one device, on one firmware version, filtered through one person's memory. These guides start from every published source instead. For the Nano Cortex that meant reading the manufacturer's manual, support FAQ, every getting-started article and every firmware release note. All of it was then cross-checked against dealer specification sheets, six professional reviews, and several thousand owner reports on Neural DSP's own community forum.
Where those sources agree, we state it plainly and cite it. Where they conflict, we show the conflict. On this device the manufacturer's own documents conflict in a few places. Where a figure has never been published, we say so instead of filling the gap with a plausible-sounding number. Reading every source catches things no single owner would, and it stays true across firmware releases.
It also closes open questions. Checking the manual against the presets guide, the device list and three dealer listings settled three of them: the factory preset mode, the factory capture count and whether a power supply ships in the box. It also turned a vague “sources disagree on the SAVE hold” into a precise conflict between two Neural DSP documents. Five open items became two.
We own a Nano Cortex and a Quad Cortex, and their panel diagrams are checked against the hardware. Every knob, button, indicator and jack is where it sits on the modeler and carries the name printed on the chassis. We do not own a Helix or a Fractal. Those diagrams are drawn from the manufacturer's own labeled panel drawings, so nothing in those guides is labeled measured.
the code enforces sourcing
Every fact on a Gridleak device page carries a source and a reliability label, and the code checks it. A claim without at least one source won't compile. A claim's reliability defaults to its weakest source, so adding a forum post to an official claim can only downgrade it.
where sources disagree, both are shown
Manufacturer documentation drifts, especially across several firmware releases. Those disagreements get their own page in each guide, with both sides cited.
see the Nano Cortex contradictionsreliability labels
- Official
- The manufacturer's own manual, support FAQ, getting-started articles and firmware release notes. The strongest source available.
- Retail
- Authorized dealer spec sheets. Used mainly for electrical specifications manufacturers don't publish directly, such as jack impedances.
- Review
- Professional reviews, used for measured observations and for criticism that marketing copy omits.
- Community
- Owner reports, mostly from manufacturer-run forums. Used for real-world gotchas and corroboration, never as the sole basis for a technical claim.
- Our reading
- Our own interpretation, flagged as such. The biggest example is the Nano Cortex factory capture decoder. Neural DSP never uses real brand names, so each mapping is an informed guess with its own confidence level.
- Unverified
- Something we could not confirm from any source, or where sources disagree. Shown with a marker.
- measured
- Read off the hardware by us, not taken from a document.
- official
- From the manufacturer's manual, FAQ, guides or release notes.
- retail spec
- From an authorized dealer's published specification.
- review
- Observed and published by a professional reviewer.
- community
- Reported by owners and used to corroborate, not as a primary spec.
- our reading
- Our interpretation, not something the manufacturer states.
- unverified
- We could not confirm this, or sources disagree.
when we get it wrong, the fix is public
The Helix Rack guide shipped saying it was 2U. It is 3U. The figure was not in the manual or the cheat sheet it was cited to. Neither states any dimensions, so the number had been invented and given a real-looking source. A reader caught it.
The sourcing check confirms that a citation exists, not that the citation says the thing. So there is now an editorial rule: a number describing physical hardware is stated only if it can be pointed at in a document. Where a manufacturer publishes no dimensions, as Fractal do not, the guides give none.
comparing across a family
Within a family these devices mostly share a sound engine, so choosing between them comes down to a handful of lines. Each guide covers only its own modeler, so the comparisons are separate pages, built from the same sourced data.
deciding which one to buy
The lines that differ, side by side, with a source on each.
corrections welcome
If you own the gear and something here is wrong, email us and it gets fixed. Each guide should stay true as firmware moves.
[email protected]the modelers
15 modelersone modeler at a time
Each guide is built from everything published about the device, not a paraphrase of the manual. A guide ships when the available sources are exhausted, not on a schedule.
- Neural DSPQuad Cortexscenes, the four-row grid, and the DSP limits that bite before the CPU meter fills.open guide
- Neural DSPNano Cortexcaptures instead of amp models, the cab-sim rule, the rotary footswitches and the four presets under your feet.open guide
- Line 6Helix Floortwo paths, 32 blocks, capacitive footswitches, and the DSP rule that stops you at four amps.open guide
- Line 6Helix LTthe same processing as the Floor with the I/O trimmed back, and what you give up.open guide
- Line 6Helix Rackthe same brain in 3U, plus wordclock, AES/EBU in and a buffered guitar thru. the Control footswitch board is sold separately.open guide
- Line 6HX Stompeight blocks, three snapshots and three footswitches, and how to spend a small budget well.open guide
- Line 6HX Stomp XLan HX Stomp with eight footswitches, and how that changes the way you build presets.open guide
- Line 6Helix Stadium Floorthe touchscreen Helix: clones, songs and flags, the Matrix mixer, and eight knobs that change job with the block.open guide
- Line 6Helix Stadium XL Floorthe Stadium with more footswitches and a second expression pedal, on the same processing.open guide
- Line 6HX Effectsevery HX effect and no amp models, for people who already have an amp they like.open guide
- Line 6HX Oneone stereo effect at a time from the full HX library, in one pedal for the board.open guide
- Fractal AudioAxe-Fx IIIfour independent grids, Cygnus amp modeling, and where to start with that much depth.open guide
- Fractal AudioAxe-Fx IIAres firmware, tone matching, and getting Axe-Edit out of your way.open guide
- Fractal AudioFM9most of an Axe-Fx III in a floorboard, and the DSP ceiling that comes with it.open guide
- Fractal AudioFM3three blocks of headroom, one amp block, and where the budget goes.open guide