Vol. 04 · Issue 14 · APR 2026
Stop tweaking. Start playing.
Line 6

Helix

The amp-modeler that rewrote the rulebook on live guitar tone.

About the Helix family

The Helix family runs the same HX modeling engine across every form factor. A patch built on a Floor loads on an LT and a Stomp without conversion. Recipes here download as .hlx files; import once and they live in your unit forever.

Models in this family

  • Helix Floor / LTFull-fat unit — 2 paths, 32 blocks, all the I/O
  • Helix StadiumNext-gen Agoura engine, more headroom for cabs
  • HX Stomp / Stomp XLPedalboard-friendly, 6 / 8 blocks
  • HX EffectsEffects-only — runs the FX from any patch
  • HX OneSingle-block stompbox, snapshots included
  • POD GoFixed signal flow, runs the same models

Patch conventions on Fader & Knob

  • Every patch ends in a Tilt EQ — global brightness adjustment without reaching for an amp's tone stack
  • Volume Pedal as block 1 so you can ride dynamics from the expression pedal
  • Multi-drive recipes ship with the alternate drive blocks bypassed; stomp them in for variants
  • Cab + Mic always uses WithPan when the dual-mic blend is part of the original tone

Loading a Helix recipe

  1. Download the .hlx file from the recipe's platform switcher (the one labelled HELIX).

  2. Connect your Helix to the computer via USB. The unit doesn't need to be in any special mode.

  3. Open HX Edit (free from Line 6). Your unit shows up in the device picker at the top of the window.

  4. File → Open Preset (or ⌘O / Ctrl+O) and pick the .hlx file. The preset loads into the current edit buffer.

  5. Drag the preset from the edit buffer to a setlist slot — for example, Setlist 1 → 01A. That's the permanent home.

  6. HX Edit auto-syncs the slot to the unit. Confirm by stepping to the slot on the Helix itself; the title should match the recipe.

How we build Helix patches

Era-correct models. Every Helix recipe targets the actual amp, cab, and pedals on the original session, mapped to the closest HX models. We don't substitute models that just sound similar — if the song was a Tweed Bassman, we use Tweed Blues / Tweed Brt, not a generic clean.

Real ranges. Amp gain sits in dB-equivalent territory, not on an abstract 0–10 scale. Delay times are real ms values. EQ frequency points are real Hz. Where the model exposes a Bias knob, we set it the way a tech would, not the way a knob graphic suggests.

Hardware-tested. Every patch is loaded onto a Helix Floor or LT and A/B'd against the reference recording before it ships. Mic + cab choices are picked by ear against the original master, with the dual-mic balance documented (e.g. 57 + 121 on a 4x12 G12M, 70/30 toward the 57).

Things to watch for

  • .hlx vs. .hlb — recipes ship .hlx (single preset) so importing won't overwrite your other patches. .hlb files are full setlist backups; we never publish those.
  • Helix Stadium parity. Stadium runs the new Agoura engine; legacy patches load fine but cabs read slightly different. Recipes built for Stadium are flagged in the recipe note.
  • Snapshot recall mode. If a recipe uses snapshots for clean → drive → solo, set the unit's snapshot recall to Discrete (Global Settings → Footswitches). Recall mode set to Recall will smooth the parameter changes and you'll lose the envelope step between snapshots.

Why Helix players use Fader & Knob

  1. Block names you can search

    Every recipe lists the exact Helix block names — the same strings that show up in the editor or your unit's display. No guessing which model matches what.

  2. Parameters in your units

    Settings are translated to your platform's actual ranges — not generic 0–10 marks. dB is dB. Hz is Hz. Time is ms.

  3. Snapshots & routing included

    Where the original tone uses snapshot switching, parallel routing, or a specific footswitch assignment, we say so. You shouldn't have to reverse-engineer it.

The Helix archive

See all Helix recipes →

Field notes for Helix players

Other modelers