Candidate Devices for MatchPatch Support
Evaluation Criteria
| Criterion |
Why it matters |
| Snapshots / Scenes |
Per-sound normalization inside a preset |
| USB preset/scene switching |
Fully automated measurement workflow |
| USB audio I/O |
Automated reamping and loudness analysis |
| Editable preset files |
Programmatic gain compensation |
| Community openness |
Easier reverse engineering and contributions |
Highly Attractive Targets
| Device Family |
Snapshots / Scenes |
USB Audio I/O |
Remote Control via USB/MIDI |
Preset File Accessibility |
MatchPatch Potential |
| Line 6 Helix Floor / LT / Rack |
8 Snapshots |
Excellent |
Excellent |
.hlx JSON, .hls setlists |
⭐⭐⭐⭐⭐ |
| Line 6 Helix Stadium / Stadium XL |
8 Snapshots |
Excellent |
Excellent |
.hsp JSON presets, .hss compressed JSON setlists |
⭐⭐⭐⭐⭐+ |
| Fractal Axe-Fx III |
8 Scenes |
Excellent |
Excellent |
.syx SysEx files |
⭐⭐⭐⭐☆ |
| Fractal FM9 |
8 Scenes |
Excellent |
Excellent |
.syx SysEx files |
⭐⭐⭐⭐☆ |
| Fractal FM3 |
8 Scenes |
Excellent |
Excellent |
.syx SysEx files |
⭐⭐⭐⭐☆ |
| HeadRush Prime |
Scenes |
Excellent |
Good |
File-based preset management |
⭐⭐⭐⭐☆ |
| HeadRush Flex Prime |
Scenes |
Excellent |
Good |
File-based preset management |
⭐⭐⭐⭐☆ |
Why These Are Attractive
Helix Family
Pros
- Snapshot architecture already matches MatchPatch perfectly.
- Presets are editable JSON files (
.hlx).
- Existing MatchPatch implementation already works.
- Full USB audio and MIDI automation.
- Large community.
Helix Stadium
Pros
- Snapshot workflow remains intact.
.hsp preset format appears JSON-based.
.hss setlists appear compressed JSON.
- Official import/export workflow exists.
- Direct migration path from the Helix ecosystem.
Why it matters
Helix Stadium may become the single best MatchPatch target after Helix Classic.
Fractal FM3 / FM9 / Axe-Fx III
Pros
- 8 Scenes per preset.
- Excellent USB audio support.
- Extensive MIDI and USB automation.
- Large professional user base.
Cons
- Presets use SysEx (
.syx) instead of JSON.
- Requires dedicated parser implementation.
Why it matters
Probably the strongest non-Line-6 candidate.
HeadRush Prime / Flex Prime
Pros
- USB audio interface.
- Scene-style workflow.
- Presets are transferred as files rather than hidden cloud objects.
- Modern architecture.
Open Questions
- Exact preset format.
- Degree of external editability.
- Scene storage structure.
Why it matters
Would benefit greatly from community contributors who own the hardware.
Potentially Interesting Targets
| Device Family |
Snapshots / Scenes |
USB Audio I/O |
Remote Control |
File Accessibility |
MatchPatch Potential |
| Neural DSP Quad Cortex |
Scenes |
Excellent |
Good |
Unknown / Limited |
⭐⭐⭐☆☆ |
| HeadRush Pedalboard |
Basic Scenes |
Excellent |
Good |
Moderate |
⭐⭐⭐☆☆ |
| Line 6 POD Go |
No true snapshots |
Excellent |
Good |
Similar to Helix |
⭐⭐☆☆☆ |
Quad Cortex
Pros
- Excellent audio platform.
- Scene system.
- USB audio.
Cons
- More closed ecosystem.
- Less known about external preset manipulation.
- Harder reverse-engineering path.
Why it matters
Could become attractive if contributors uncover editable preset structures.
Less Attractive Targets
| Device Family |
Main Limitation |
| Boss GX-100 |
Preset format not easily editable |
| Boss GT-1000 |
More editor-centric workflow |
| Mooer GE Series |
Smaller ecosystem, unclear file formats |
| Hotone Ampero Series |
Limited documentation and tooling |
| Valeton GP Series |
Small ecosystem, little reverse-engineering activity |
Why These Are Less Suited
Most of these devices provide:
- USB audio
- MIDI switching
- Preset export/import
However, they often lack one or more of:
- Snapshot/scene-centric workflows
- Accessible preset formats
- Active developer communities
- Well-documented automation paths
As a result, development effort is significantly higher while user impact is lower.
Suggested MatchPatch Support Priority
- Line 6 Helix Floor / LT / Rack
- Line 6 Helix Stadium / Stadium XL
- Fractal FM9
- Fractal FM3
- Fractal Axe-Fx III
- HeadRush Prime / Flex Prime
- Neural DSP Quad Cortex
Looking for Contributors
MatchPatch is especially interested in contributors who own:
- Helix Stadium / Stadium XL
- Fractal FM3
- Fractal FM9
- Fractal Axe-Fx III
- HeadRush Prime
- HeadRush Flex Prime
- Neural DSP Quad Cortex
Particularly valuable would be help investigating:
- Preset file formats
- Setlist formats
- Scene/snapshot storage
- Gain parameter locations
- MIDI/USB automation workflows
- Preset import/export behavior
The loudness-analysis engine itself is device-independent. The primary challenge is implementing device-specific preset parsing and gain-writing backends.
Candidate Devices for MatchPatch Support
Evaluation Criteria
Highly Attractive Targets
.hlxJSON,.hlssetlists.hspJSON presets,.hsscompressed JSON setlists.syxSysEx files.syxSysEx files.syxSysEx filesWhy These Are Attractive
Helix Family
Pros
.hlx).Helix Stadium
Pros
.hsppreset format appears JSON-based..hsssetlists appear compressed JSON.Why it matters
Helix Stadium may become the single best MatchPatch target after Helix Classic.
Fractal FM3 / FM9 / Axe-Fx III
Pros
Cons
.syx) instead of JSON.Why it matters
Probably the strongest non-Line-6 candidate.
HeadRush Prime / Flex Prime
Pros
Open Questions
Why it matters
Would benefit greatly from community contributors who own the hardware.
Potentially Interesting Targets
Quad Cortex
Pros
Cons
Why it matters
Could become attractive if contributors uncover editable preset structures.
Less Attractive Targets
Why These Are Less Suited
Most of these devices provide:
However, they often lack one or more of:
As a result, development effort is significantly higher while user impact is lower.
Suggested MatchPatch Support Priority
Looking for Contributors
MatchPatch is especially interested in contributors who own:
Particularly valuable would be help investigating:
The loudness-analysis engine itself is device-independent. The primary challenge is implementing device-specific preset parsing and gain-writing backends.