v0.6.1

fretwire 0.6.1

The Helix Rack is verified, a shared footswitch shows every block on it, and Mac backups
convert correctly. A Rack owner's three rounds of testing took it from untested to verified,
including the first edits ever sent to one. A second POD Go owner found two bugs and calibrated
the POD Go's DSP ceiling. Their backups and dumps also fixed several bugs in backup conversion.

14 commits since v0.6.0.

---

Helix Rack: verified

An owner ran 0.6.0 against a Rack on firmware 3.80.0 and everything worked unmodified (#24). It
identifies as the Floor's P21, so it uses the Floor's edit builders, which were already checked
byte-for-byte against a Floor. On the Rack, parameter edits on both DSPs, a bypass and a revert
all worked, each confirmed on the unit's screen. The device table now has its real geometry: two
DSPs, eight snapshots, eight setlists of 128, presets numbered 01A-32D, and the backup device
ID 0x00210002, so show-backup names a Rack's .hxb. The survey is in
docs/helix-rack.md.

Footswitches

• A switch carrying several blocks shows all of them. Only the first block assigned to a
  footswitch was read, so a switch toggling two bypasses showed up on one block only (#25).
• The expression pedal's toe switch is labelled "Toe", not "FS13" on a Helix or "FS9" on a
  POD Go. The chain badge, the bypass picker, the CLI and the history labels all use it, and the
  tooltip gives the editor's own name ("EXP Pedal Toe" in HX Edit, "EXP Toe" in POD Go Edit).

Backup conversion (hxb-convert)

• Mac backups convert with the right number types. Mac HX Edit writes whole-number knobs as
  JSON integers, and the converter passed them through, so it wrote integers where the device
  stores floats. Every value is now typed from the model data, which matched all 1,025 stored
  values checked across five device types.
• Input and output nodes are converted on the Helix family: a gate, pan or gain is stored only
  while the node is routed. The POD Go and the Stomp still keep the donor preset's values.
• The preset tempo and the focused block come across from the backup.
• Topology AB (a DSP the paths only pass through) converts instead of being refused.
• A converted Rack preset now matches the Rack's own copy apart from float noise.

POD Go

• The DSP meter reads against the POD Go's own ceiling. The pedal accepted a raw load of
  77.9 and refused 79.6, so a POD Go preset is now scaled against 78 instead of the Stomp's 75.
  The old scale had stopped the owner adding blocks at 57.9.
• FS7 is confirmed as controller ordinal 9, which settles the order of the switch run.
• A Volume or Wah block storing an out-of-range cab index no longer reads as having a cab.

MCP server

The catalog tools (catalog_categories, catalog_models, model_params) read the connected
pedal's catalog, or the one named by a new optional device argument ("pod-go" or "hx").
Before, they always read the HX family's, so a POD Go owner who had imported only POD Go Edit's
data was told to import (#26). backup_describe and backup_diff go by the device each preset
came from. A failed catalog load is no longer cached until restart.

Also

• fretwire models lists every model with the index add-block and swap take, its
  category and its DSP cost, optionally filtered by name (--pod-go for the POD Go's).
• The CLI's save and rename refuse to write into another setlist unless
  FRETWIRE_SETLISTS=1, as the GUI already did.
• pull no longer flags every path-B block "past-mixer!" on a preset whose paths span both
  DSPs. It now says there is no mixer on that DSP.
• presets no longer calls out-of-slot stored presets "reordered on the device". A
  factory-reset unit has them too.

Known limits

• Serve mode has no TLS of its own; put it behind a tunnel or a proxy beyond a trusted LAN.
• Favorites and user defaults are backed up but not restored.
• A converted preset has never been sent to a pedal.
• Assigning a block to a switch that already has one is assumed to replace it, not add to it.
  This has not been captured.
• Grid and routing planning is still DSP-0 only; the settings namespace is mapped in part;
  IR reorder is delete-and-re-upload.
• No firmware, flash or DFU traffic, by design and permanently. See
  docs/safety.md.

Installing

Grab the .deb, .rpm, .AppImage or the Arch .pkg.tar.zst for the GUI, or the static
tarballs that run on any distro, x86-64 or arm64: fretwire-cli-* (the CLI),
fretwire-serve-* (the daemon, one file with the editor inside) and fretwire-mcp-*
(the MCP server). The deb, rpm and Arch package install the udev rule and the CLI alongside the
app; for the AppImage or the tarballs, install packaging/70-hxstomp.rules yourself and replug
the pedal. The rule's Helix Rack comment changed; its device lines didn't.

On first run the app imports the model and preset reference data from your own HX Edit
installation (POD Go owners: from POD Go Edit). Nothing proprietary is shipped in these
packages, and nothing is sent anywhere unless you say yes to the update check.

Thanks

@hunterbring, who surveyed, edited and backed up a Helix Rack over three rounds (#24).
@dmick, whose POD Go found #25 and #26 and answered the open POD Go questions on #15.
@jamesremuscat, still testing the POD Go on #15.