The Editor is Going Electric
The editor now also speaks Play Electric. Same workflows you already know — fetch, sync, arranger, setlists, Stage Traxx integration — running against PE's byte layout, with the PE-exclusive Guitar Amp and Comp blocks, PE-specific style enums, and the firmware's per-style cascade defaults baked in.
Same editor, two products. The rest of this post covers how to switch between them, what changes when you do, and the rough edges still being settled.
New to the editor? (Play Electric users, welcome)
If you landed here because you have a Play Electric and you've been looking for a way to keep editing presets after VoiceSupport 2 stopped working — you're in the right place. The short version:
- It's a web app. Open the editor in Chrome or Edge, plug your PE into USB, and click the device icon top-left to connect. The editor identifies your device and switches to PE mode automatically.
- Load → From device pulls every preset off the PE so you can edit them in the browser. Save → To device sends edits back. You can also save to a
.tchfile for archive. - Live automation — the editor's Live tab can toggle effects, fire HIT, and switch presets in real time, driven from Stage Traxx / OnSong / any MIDI-capable app. See the Live tab section in the manual.
- Firmware updates work too — the editor bundles every TC Helicon firmware release for both PA and PE, with an automatic preset backup before flashing. See the Updating firmware section in the manual.
- Tablets and phones work too — iPad / iPhone Safari doesn't expose Web MIDI, but installing the free MIDIWeb Browser app gives you the same editor over USB. See Setting up on iPad with MIDIWeb Browser.
- Resources has video demos of the Preset Editor, the Arranger, Stage Traxx automation, and Widget mode on iPad — watch one or two to see the workflows before diving in.
- The Manual is currently PA-flavoured, but every workflow described there works identically on PE — fetch, edit, send, setlists, the Stage Traxx integration, the Live tab, firmware updates, all of it.
- The Play Electric technical reference documents PE's specifics — product byte 0x71, 4 data packets per preset, the 0x03 format-version byte, plus the full byte-by-byte parameter map.
If you've never touched the editor before, start by hitting Launch the Editor from the homepage, connect your PE, and click Load → From device. That's the whole flow.
How to switch
There's a small ▼ arrow next to the device image at the top-left of the editor. Click it and you'll get a two-option popup:
- Play Acoustic
- Play Electric
Picking the other product reloads the editor with a clean slate so all the in-memory state (loaded presets, snapshots, dirty markers) doesn't leak between two completely different byte layouts. If you have unsaved changes you get a confirmation first.
When you connect a real device, the editor reads its identity reply and switches to the matching product automatically — the manual switcher is mostly for working offline (editing PE preset files on a machine that has no PE plugged in).
What changes when you go electric
- The preset view renders with the Play Electric's own block layout — vocal blocks at PE's byte indices (Harmony, Double, Vocal Delay, Vocal Reverb, HardTune, Transducer, µMod), plus the PE-exclusive Guitar Amp (26 amp simulations from Clean Brit to Acoustic Shape) and Comp (4 compressor styles) blocks.
- Style cascade defaults follow PE's firmware behaviour — change the Amp Style and Drive / Level snap to the firmware's per-style defaults; change Vocal Reverb Style and Decay updates the way it does on the device.
- BodyRez is hidden — PE doesn't have it.
- The firmware-update manager shows only Play Electric firmware files (and refuses to flash anything that doesn't match the connected device).
- The sample presets and setlists in the Load menus filter by product, so you only see files that work on the active device.
- Opening a Play Acoustic
.tchin Play Electric mode (or vice versa) is refused, with a message pointing to the switcher. The byte layouts are completely different — rendering the wrong file with the wrong tables would just produce garbage labels and ranges.
Restrictions and rough edges
Play Electric support shipped on the back of one external tester's data (huge thanks, fled 🎸) plus a careful read of TC Helicon's reference manual. More testing is still needed, and a few things are still rough:
- The preset packs bundled with the editor are all Play Acoustic. PE users get an empty Load → Preset Packs list for now. If you have PE preset packs — especially the Factory Presets — and you'd be willing to share them, please get in touch via the bug-report link below; we'll bundle them so other PE users can load them.
- Some parameters may still not behave exactly as they do on the device. If you spot anything wrong, use the Report a bug link in the editor footer — every concrete report helps the PE path tighten up.
What still works the same
If you're a Play Acoustic user, none of this should affect you. The editor still boots into Play Acoustic mode by default, the icon update aside. All existing features, files, setlists, and packs work exactly as before. Same hot-keys, same fetch-from-device flow, same arranger.
A note on the existing documentation
There's now a dedicated Play Electric technical reference generated from the editor's live parameter map — same shape as the Play Acoustic page but with PE's product byte, packet count, header format byte, and full byte-by-byte parameter listings. If you want the protocol detail for PE, start there.
The Manual, FAQ, and About pages are still written from a Play Acoustic perspective — examples mention the PA, screenshots show PA-specific blocks (BodyRez, the acoustic mic types, etc.). Everything those pages describe — fetch / send / save / setlists / firmware update / Stage Traxx integration / arranger — works the same way in Play Electric mode. The byte indices are different under the hood, but the editor handles that translation for you. So if you're a PE user reading the manual: substitute "Play Electric" wherever you see "Play Acoustic" and the workflows still apply.
Properly product-aware docs are on the to-do list; until then, this post + the editor's UI + the PE technical reference are your shortest path to using the PE-specific bits.
Found something broken?
If you spot an issue specific to the Play Electric path — wrong labels, missing widgets, cascade defaults that don't match what the device does — please file an issue. The PE support is still settling in and every concrete report helps it tighten up.