Control Types

Every parameter a fusor can automate is one of two control types, fixed by the parameter itself. A knob or fader is a curve. An enable switch is a gate. You cannot make one behave as the other, and the Domain Editor offers a different set of controls for each.

Which parameters are which is listed in Supported Parameters.

Curves

A curve parameter holds a value between 0 and 1 for every point of the transition. The runtime reads the progress meter, evaluates the curve at that progress, and sends the result.

The shape between two anchors follows the interpolation mode of the anchor on its left: Bezier, Linear, or Hold. The modes, the handles, and what happens at the top and bottom of the canvas are covered in the Curve Editor.

A curve holds between 2 and 16 anchors. The first sits at 0% progress, and on a continuous curve the last sits at 100%.

Unipolar and bipolar

Curve parameters differ in what the middle of the range means:

• Unipolar. 0 is off or silent, 1 is full. Channel faders, FX amounts and stem levels work this way, and a curve to 0 is how a fusor silences something.
• Bipolar. 0.5 is unity, below it cuts and above it boosts. EQ bands, stem filters and Mixer FX Adjust work this way, so an EQ curve that should leave a band alone sits flat at the middle of the canvas.

The wire side of the same distinction is in MIDI Mapping → Control semantics.

Stepped curves

A curve can be constrained to a small set of named levels, in which case it holds each level until the next anchor instead of interpolating. That is an authoring choice made per binding, either by attaching a step set or by setting interpolation to Hold. See Stepped Output.

Gates

A gate parameter has two positions, Off and On. Fusor Studio uses it for the signal-path enables a knob genuinely needs to work: Mixer FX Enable, an FX slot enable, a per-stem FX-send enable.

A gate is authored on the same canvas as a curve, with two differences:

• The ladder is fixed at two levels. Right-clicking a level lets you rename it. There is no add, no delete, and no step set to attach, change or save, so the property strip's step-set buttons are absent and its Interp control stays pinned to Hold.
• Anchors set the timing. Every anchor sits on Off or On, so what you author is when the switch flips. A new gate binding starts Off and flips On at the halfway point. Drag that middle anchor to move the flip, or add anchors to flip it more than once.

On the wire a gate travels as a note, which is why it has no in-between. See MIDI Mapping → Message types.

What reaches the DJ app

Three things happen between the curve you drew and the message the DJ app receives.

• Quantization. A continuous value is rounded to one of 128 steps before it is sent. Two anchors a hair apart can therefore produce the same output.
• Repeat suppression. A value identical to the one already sent for that address is not sent again. A curve sitting flat sends nothing until it moves, and a gate held On sends one message rather than one per tick.
• Clamping. Values stay inside 0 to 1. The curve you see on the canvas is the value that goes out; see Curve limits.

Fusor Studio drives the control to the value the curve says, and the DJ app decides what that sounds like.

Addresses a fusor cannot drive

Some addresses in the canonical mapping only ever travel from the DJ app to Fusor Studio. Deck play state is the clearest example. A domain binding cannot reach one, because a binding may only target a parameter its own domain owns. An action step that tries is rejected by name, with the message Cannot SET read-only address "<addr>" (telemetry only). Either way the failure lands at load time, with the transition still ahead of you.

Fusor Studio also never commands deck transport. Play, cue and stop stay with you.