Engineered Transition Automation for DJs

01

Structured Parameter Automation

Fusor automates EQ, stems, deck levels, and FX as a transition progresses.

The crossfader (or a control of your choosing) drives transition progress. You move it, the player reads your position and the Fusor modulates the parameters. Automation can run on its own when you want, but it never takes the crossfader away from you.

• Crossfader-first: automation never displaces manual control
• Every parameter value comes from one source: how far along the transition is
• Automate the whole transition, or just the parts you want

02

Fusors: Progress-Driven Automation

A Fusor defines what gets automated and how each parameter changes as the transition moves.

You author automation against roles — incoming and outgoing — not specific decks. Fusor figures out which is which when you start.

• You can see every automated parameter and its curve in the player
• Enable or disable control groups prior to running
• Fusors are reusable across different transitions

The Fusor holds the automation. Progress — whether you or the clock is driving — triggers it.

04

Actions: Event-Driven Automation

An Action is a short sequence of MIDI commands that runs once when you trigger it. Where a Fusor responds to transition progress, an Action responds to a single command.

You can insert explicit delays between commands, so one press reconfigures your DJ app in a defined order with the timing your gear needs to settle. A single mapped MIDI key cannot do that.

• Fire from a pad, a controller key, or a Fusor's pre-run queue
• Group eight into a Pack to drive Pad Mode
• Actions are saved as user-editable text files

Fusors shape the transition. Actions reconfigure the system around it.