Reference Overview

Reference

Technical reference for Fusor Studio — the tables, formats and codes you look things up in.

For how a feature works, see the Manual. For a sequence to follow, see the Tutorials.

Available references

  • MIDI Mapping. The complete canonical MIDI channel layout, CC numbers, and control types used to communicate with DJ software.
  • Teach Mode. The Settings tab that walks the canonical mapping one binding at a time. The recommended way to build or validate a DJ-app MIDI mapping. Includes the Traktor Crossfader Assign recipe.
  • Troubleshooting. Common issues and fixes for MIDI, application, and transition problems.
  • Logging. Log file locations, verbose mode, per-category log levels, and bug-report workflow.
  • Start-with-Incoming (deep dive). Extended reference for the Auto Run Mode start trigger: the press-Play default, the Start-with-Incoming opt-in, pause and resume differences, and tempo-ramp interaction in Traktor.
  • Action File Reference. The .faction file format: top-level shape, step types (SET, WAIT, WAIT_UNTIL, CAPTURE, RESTORE, IF), symbolic values, predicates, role addresses, nesting rules, and duration estimation.
  • Hardware Controller. Mapping a MIDI controller to Fusor Studio: profiles, MIDI Learn, the binding model, the two Shift keys, and the .fcontroller file format.
  • Status Messages. Every code the status line can show — CAP4, GATE2, TR8 and the rest — what it means, and what to do about it. Start here when Fusor refuses to do something.
  • Settings. The Settings window tab by tab. Connection, General, Guards and Output Mapping in full, including the ERA guards; the other four tabs point at the chapters that own them.
  • Supported Parameters. Every parameter a fusor can automate, by domain: addresses, control types, value ranges, per-app availability, and how many of each a fusor may hold.
  • Control Types. Curves and gates: how each is evaluated across the transition, what unipolar and bipolar mean when you place an anchor, and what reaches the DJ app.
  • Fusor File Reference. The .fusor file format: top-level shape, the meta block, domains, bindings, curves and anchors, the actions block, and validation rules.
  • Keyboard Shortcuts. Every key binding, from the application shortcuts to the editing keys in the Library popover.
  • Updating Fusor Studio. Where the version number lives, how a new build downloads and installs, why an update sometimes waits for the mix to end, and where update failures are logged.