helixgen-core
The core Python library + CLI behind helixgen: generate Line 6 Helix
Stadium .hsp presets (and legacy .hlx) from JSON tone recipes, edit them
surgically in place, manage impulse responses by Stadium-exact content hash,
and control a Helix Stadium directly over the LAN (OSC-over-ZeroMQ — no
editor app).
⚠️ Unofficial tool — use at your own risk. Not affiliated with or endorsed by Line 6 / Yamaha (see Trademark notice). Loading any user-generated preset on your hardware carries risk — rejected loads, corrupted preset slots, on-device crashes. Review what you import. The MIT LICENSE disclaims all warranty.
Repo family
| Repo | What it is |
|---|---|
| helixgen-core (this repo) | The helixgen Python package: libs + CLI (the engine's only surface) |
| helixgen | The Claude Code plugin — /tone, /setup, /device skills + marketplace |
| helixgen-tui | Terminal UI for tones, setlists, and device control |
Want natural-language preset generation inside Claude Code? Install the plugin — you don't need this repo directly. This repo is for using the CLI/library standalone, or developing against it.
Install
Requires Python 3.11+. Published to PyPI:
pip install 'helixgen[device]'
Extras: device (network device control: pyzmq, msgpack, paramiko),
dev (pytest).
A standalone install starts with an empty block library — seed it first from
your own device exports (or point $HELIXGEN_LIBRARY at an existing library):
helixgen ingest ~/MyPresets/
Computing IR hashes from WAVs (register-irs <wav>, ir-scan) additionally
needs libsndfile (brew install libsndfile / apt install libsndfile1).
Quick tour
helixgen list-blocks --category amp # browse the block library
helixgen show-block "Brit Plexi Brt" # exact param names/ranges
helixgen generate recipe.json -o tone.hsp # author a preset from a recipe
helixgen set-param tone.hsp "Tape Echo" Mix 0.3 # surgical edit
helixgen view tone.hsp # read a .hsp back as a recipe
helixgen device list # talk to a Stadium on the LAN
helixgen device sync my-setlist # mirror a managed setlist onto it
Full references:
docs/CLI.md— every verb, including the completehelixgen devicereference.docs/recipe-reference.md— the exhaustive recipe schema (paths, splits, snapshots, footswitches, expression, MIDI, Command Center, IRs).docs/ir-hash-algorithm.md— the reverse-engineered Stadium IR hash, field-validated.docs/helix-protocol.md— the network protocol.
Tests
Run from a source checkout with the package on PYTHONPATH:
PYTHONPATH=$PWD/src python -m pytest
Live integration suite (tests/live/)
An opt-in suite that drives the real CLI via subprocess against the
user's real block library and a real Helix Stadium on the LAN. It is
skipped entirely (fast, green) unless HELIXGEN_LIVE=1:
HELIXGEN_LIVE=1 PYTHONPATH=$PWD/src python -m pytest tests/live -q
Tests are grouped by impact area with registered markers — authoring,
library, ir, device_read, device_write, liveops, setlists,
sync, device_ir, locks, discover (plus live on everything and
live_global for the
extra-gated global-settings write) — so a targeted change can run just its
blast radius, e.g.:
HELIXGEN_LIVE=1 PYTHONPATH=$PWD/src python -m pytest -m "live and sync" tests/live
The device_write module's #38 regression guard only guards when the active
preset's edit buffer is dirty — that is the state that made
/CreateContent answer status field 3 = 1, which pre-0.30.0 clients misread
as an error and "cleaned up". A clean buffer answers 0 and exercises the
uninteresting path. The dirty_edit_buffer fixture establishes that state
itself (a manual tweak wouldn't survive: an earlier device load in the same
module clears the flag), and skips rather than passing green if it can't —
so a skip there means the guard did not actually run. See each module's
docstring.
Safety is enforced by fixtures: all local state (manifest, IR mapping,
IR-hash cache, prefs, backups) is redirected to a scratch dir; an upfront
device backup runs; device state is diffed before/after (the suite fails
itself on any leak); every artifact is HGTEST-prefixed and torn down even
on failure. See tests/live/conftest.py for the full safety model and the
list of deliberately excluded verbs.
Acknowledgments
sensorium/phelix — a
community-maintained, hand-curated repository of Helix block JSON files — was
the reference that made the block/param vocabulary legible while helixgen's
own ingest was being written. helixgen no longer reads it: the shipped block
library is built from real .hsp device exports (helixgen ingest), and
model/param ranges come from src/helixgen/device/_defs_data.json.
Trademark notice
helixgen is an unofficial community project. Line 6, Helix, HX,
and related product names are trademarks of Yamaha Guitar Group, Inc.
helixgen is not affiliated with, endorsed by, or sponsored by Line 6 or
Yamaha. References in this project to Line 6 hardware, file formats (.hlx,
.hsp), and model identifiers are descriptive — helixgen generates files
intended to be compatible with Line 6 Helix devices but is not a Line 6
product.
If you are a representative of Line 6 / Yamaha and have concerns about this project's name or scope, please open an issue.
1 maintainer
Metadata
1 maintainer
Release files for helixgen 0.54.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| helixgen-0.54.0.tar.gz | 1.6 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| helixgen-0.54.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.9 MB
Release files / helixgen-0.54.0.tar.gz
| Download URL | helixgen-0.54.0.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b00a3b51f8df83f31b1c184eba6c36d84b8f11b5e818147e1579877983769ab7
|
|
BLAKE2b-256 checksum How to use checksums |
a26c3ba56d7a7dd8673a3f72c0acdcca2e8c4ef80644997b76f5de06677944b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency logRelease files / helixgen-0.54.0-py3-none-any.whl
| Download URL | helixgen-0.54.0-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9c41f8ec4ede31467c8ec4128b9c1ba19fc576033fbba920143002b91217edb2
|
|
BLAKE2b-256 checksum How to use checksums |
00f8bded19f477ec472ca4fc7d3e69d55d80da55ea3c75c82e69ea648e96638f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency logSecurity for helixgen 0.54.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for helixgen-0.54.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
