Transport Controls

The transport is split between two regions of the player. The progress strip carries the two large transport buttons, Arm / Play / Pause on the left and Abort on the right. The three toggles that configure how the transition runs (Mode, Start-with-Incoming, and Tempo Ramp) live in the Menubar transition group, between the menus and the session-group icons.

Below is the lookup: what each control looks like in each state, and what clicking it does. The lifecycle these controls drive is told once, in Arming and Running a Transition.

Toggling any of the three toggles updates the persistent state message on the left of the status line. That, alongside the icon's colour change, is how the toggle confirms.

The Arm / Play / Pause button

The large left-hand button. Same button, different behaviors depending on the player state.

With Tempo Ramp armed, every Armed and Unarmed variant gains a with Tempo Ramp segment: Unarmed with Tempo Ramp, Armed with Tempo Ramp: ….

Auto Run Mode's default start trigger is press Play, so the arm control is the Play button. The Start-with-Incoming toggle flips this: when on, the button reverts to an arm dot and the transition starts when the incoming deck begins playing.

One more armed variant exists: if Start-with-Incoming is on and the incoming deck is already playing, the status line reads Armed: restart incoming deck to start. The trigger fires on the deck starting, so a deck that's already running has nothing to trigger on.

Two kinds of pause in Auto Run Mode. Pressing PAUSE stops the fusor's output while the timing window keeps ticking, so the remainder runs faster to land on the original finish time. Stopping the incoming deck in your DJ app stops the transition clock as well, and the finish time moves back by however long you waited. See Arming and Running for the detail.

The Abort button

The large right-hand button. Press and hold for roughly 0.4 seconds to fire; a radial fill grows outward from the centre while you hold, and releasing before it completes cancels the abort. A brief click does nothing. Once the hold completes, the transition is terminated immediately and permanently.

Abort is live while a transition is actually under way — running, paused, or in its setup pause. It is not live while the player is merely armed: nothing has started, so there is nothing to abort. Disarm instead, by clicking the arm dot or toggling Start-with-Incoming off.

Aborting covers what an abort leaves behind, including the fact that it re-derives deck roles from the crossfader position rather than swapping them.

Use Abort when something has gone wrong and you need to bail out fast. For "I just need a moment," use the Arm/Play/Pause button's Hold or Pause role instead. Those are resumable.

Its second face: RESTORE

This button has two states, and it is the same button either way:

RESTORE appears one second after an abort, if there is anything to put back. It's white rather than red on purpose: red is the alarm, and restoring is a deliberate choice you make, not a panic.

For the first second after an abort the button still reads Abort and still is Abort — that's a guard against the reflex double-press, and it's in the engine, so it protects a hardware controller press too. On a controller it stays one button and one command: press it once to abort, again to restore, exactly as on screen.

The full behaviour — what it restores, when it's silent and automatic, when it isn't offered at all — is in Putting things back.

The Mode toggle

The leftmost icon in the Menubar transition group, a stopwatch. Blue means Auto Run Mode; plain dark means Manual Run Mode. Manual is the default, and your last choice is remembered across sessions. See Manual Run Mode vs Auto Run Mode.

You can change modes while a fusor is loaded but not yet running. Once a transition starts the mode is locked, with one exception: in Auto Run Mode while Online, moving the crossfader performs a manual takeover and converts the run to manual from that point on. The reverse, Manual to Auto mid-transition, is not possible.

In Blind Mode the toggle is disabled, and its tooltip explains why: Manual Run Mode is driven by an actuator Fusor tracks through telemetry. Blind Mode ignores telemetry, so progress can only be time-driven (Auto Run Mode).

Switching the Mode toggle to Manual also clears Start-with-Incoming, since the opt-in is an Auto Run Mode concept.

The Start-with-Incoming toggle

A chain-link toggle in the Menubar transition group, sitting between the Mode toggle and the Tempo Ramp toggle. It picks which of Auto Run Mode's two start triggers is in force.

Toggling it is itself an arming gesture: on from idle arms the player in the Start-with-Incoming state, off from there disarms. Turning it on also switches the player to Auto Run Mode. In Manual Run Mode the toggle is enabled, and clicking it switches to Auto and arms in one gesture.

The preference is session-level: it holds across transitions until you change it, or until you switch the Mode toggle back to Manual.

When the toggle is disabled

Start-with-Incoming (deep dive) has the full treatment: how long the preference lasts, pause and resume differences, and the Tempo Ramp interaction.

The Tempo Ramp toggle

The rightmost icon in the Menubar transition group, a rising trend line with an arrowhead. It arms a tempo-sync setup sequence that runs when you arm, ahead of the transition itself.

Flip it before arming. At the end of a transition it resets to off, unless Persist tempo ramp across transitions is on in Settings → General. With that on, the ramp stays armed through completion and through an abort, ready for the next run.

In Blind Mode the toggle is disabled, tooltipped The tempo ramp needs telemetry to confirm the deck reached its target tempo. Blind Mode ignores telemetry, so the ramp can't run. A fusor containing a tempo-ramp phase refuses to arm in Blind Mode.

Apps that need the incoming deck playing

Some DJ apps can't sync or set tempo master on a stopped deck. Traktor is currently the only one. On those apps:

• If the incoming deck is already playing when you arm, the setup sequence runs straight away.
• If it isn't, the sequence is queued and the toggle blinks yellow. It fires as soon as the incoming deck begins playing.

A ramp that lands after the transition is already under way can be audible, and the status line says so: Tempo ramp late: may be audible. This never happens on Start-with-Incoming runs, since the transition can't start until the incoming deck is playing.

Hold vs Pause vs Abort: how they differ