How these guides are made

Every source, not one opinion

A guide written from a single unit describes one device, on one firmware version, filtered through one person's memory. These are built the other way round. For the Nano Cortex that meant reading the manufacturer's manual, support FAQ, every getting-started article and every firmware release note, then cross-checking all of it 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 — and on this device the manufacturer's own documents conflict in a few places — we show the conflict instead of quietly picking a side. Where nobody has published something, we say so rather than filling the gap with a plausible-sounding number. That aggregation is the product: it catches things no single owner would, and it stays true across firmware in a way one person's notes don't.

It also means open questions get closed rather than left standing. Cross-checking the manual against the presets guide, the device list and three dealer listings settled the factory preset mode, the factory capture count and whether a power supply ships in the box — and turned a vague “sources disagree on the SAVE hold” into a precise, attributable conflict between two Neural DSP documents. Five open items became two.

The Nano Cortex and Quad Cortex panel diagrams are validated directly against the hardware — we own both — so every knob, button, indicator and jack is where it actually sits 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 labelled panel drawings, which is a better source than a photograph but is not the same as holding the box, and nothing in those guides is labelled measured as a result.

Sourcing is enforced, not promised

Every fact in a Gridleak Guide carries a source and a reliability label, and that's checked by the code rather than by discipline — a claim without at least one source won't compile, and a claim's reliability defaults to its weakest source. Adding a forum post to an official claim can only ever downgrade it.

Where sources disagree, both are shown

Manufacturer documentation drifts, especially across several firmware releases. Rather than pick a side and look authoritative, those disagreements get their own page in each guide.

Reliability labels

Official

The manufacturer's own manual, support FAQ, getting-started articles and firmware release notes. The strongest source available — and, for the Nano Cortex at least, better than almost all of the video content about it.

Retail

Authorised dealer spec sheets. Used mainly for electrical specifications manufacturers don't publish directly, such as jack impedances.

Review

Professional reviews. Useful for measured observations and for honest 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, clearly flagged. The Nano Cortex factory capture decoder is the biggest example: Neural DSP never uses real brand names, so those mappings are informed guesses carrying a confidence level each.

Unverified

Something we could not confirm from any source, or where sources disagree. Shown with a marker rather than quietly asserted.

When we get it wrong, the fix is public

The Helix Rack guide shipped saying the unit 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 it had been invented and then given a real-looking source. A reader caught it.

That is the one failure the sourcing contract cannot catch: it checks that a citation exists, not that the citation says the thing. The rule it produced is now enforced editorially — a number describing physical hardware is only stated if it can be pointed at in a document. Where a manufacturer publishes no dimensions, as Fractal do not, the guides say nothing rather than estimating.

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. No single guide can answer that, because each one only knows about its own box — so the comparisons are their own pages, built from the same sourced data.

Corrections welcome

If you own the gear and something here is wrong, it should be fixed. The goal is a guide that stays true as firmware moves, which is exactly where most gear coverage falls down.