Shape tones.
Own the stage.

Connect RushLink to your pedal

Install and open the desktop alpha, place both devices on the same trusted LAN, then choose your connection method.

1. Open Settings → Connection.Select Flex Prime, Prime or Core to use that model’s standard hostname.
2. Try automatic discovery.If discovery is unavailable, enter the pedal’s .local hostname or private IP.
3. Confirm the live device card.The sidebar shows the connected device and host. RushLink then keeps visible workspaces synchronized.
4. Choose how edits apply.On the first change, RushLink explains live apply. You can keep immediate changes or use staged writes.

Audition a capture through a real test chain

ToneMod keeps Tone3000 and HeadRush Cloud separate, loads results in manageable batches, and adapts the test chain to the selected capture.

1. Choose a source.Open Tone3000 or HeadRush Cloud. Cloud data is only requested when its tab is selected.
2. Filter before loading more.Narrow by capture type, platform format, style, gear and ordering. Search runs against the active source.
3. Review automatic classification.RushLink identifies amp, effect, amp+IR, IR or full-rig content. Override it manually when the source metadata is incomplete.
4. Prepare the Test Rig Studio.Choose or edit a template. Locked host slots keep drive, amp, NAM and IR content in valid positions; other blocks remain movable.
5. Press “Audition on HeadRush”.RushLink loads the complete test chain, inserts the selected file into its NAM or IR host, and keeps your previous rig available for restoration.
6. Finish the audition.Return to the original rig or save the result intentionally. Test rigs never silently overwrite existing rigs.

Build a live surface around the set

StageHand separates layout work from performance so accidental edits stay out of the show.

1. Create or select a stage.A stage can be independent or attached to a rig so the layout follows rig changes.
2. Open Stage edit.Choose 1–4 rows and 1–8 columns, shorten the first row, and tune horizontal, vertical and outer spacing.
3. Add controls.Drag scenes, block toggles, rig actions, tuner, drummer or supported multi-button decks into the grid.
4. Edit one control.Choose its label, colour, action, tap behavior and—where safe—a compatible hold behavior.
5. Optionally use MIDI Learn.RushLink can learn from controllers exposed by the operating system. Device actions themselves use the reflected device API.
6. Lock the layout.Enter performance mode for large, reliable targets and clear visual press feedback.

Edit the signal path with context

RushLink visualizes the connected Prime-family device’s signal path as a responsive chain. Select a block to edit its parameters, presets, EQ response or device-backed file assignment. Drag populated blocks to reorder them. Split routes are drawn according to the current device topology, while Input, Mix and Output controls stay focused on parameters that actually apply.

Explore an idea without losing your way back

Change History belongs to each rig and records completed, meaningful edits. Temporary scene changes and routine effect bypass actions stay out of the timeline so it remains useful.

1. Edit naturally.RushLink waits for a parameter gesture or structural change to finish, then records the useful before-and-after state.
2. Understand the timeline.Entries describe actions such as moving a block, changing a preset or adjusting an amp—not a stream of anonymous values.
3. Preview an older state.Select an entry to hear and inspect it. Preview navigation does not create another history entry.
4. Choose the outcome.Return to the current live device state, restore the previewed version, or deliberately overwrite the current state.
5. Keep the record.History is preserved for the rig, with the current device state always available as the safe destination.

The pedal remains the source of truth

RushLink listens for device events and uses efficient page-scoped polling as a fallback. Immediate edits are designed to feel direct, while history and snapshots provide recovery. Network requests are restricted to .local, loopback and private/link-local addresses; arbitrary remote targets, redirects, credentials and non-API routes are rejected by the native transport.