UI

Read with AI
All docs in one file (llms-full.txt)

Controls you place inside the graph. 3 in total. They are the entry point for creating values by hand, and also the window through which values from MIDI or OSC are pulled into the graph.

Node list

NodePortsWhat comes out
SliderMin / Max / ValueOutThe knob position (float)
ButtonInBool Outputtrue only while it is held down
ToggleInBool OutputAlternates between true / false on each press

Slider can be switched between vertical and horizontal.

The most important thing about this category

The input ports are not a “pass-through” for values — they move the control itself.

// 外部信号でUIの状態を駆動する
valueInput.OnFloatChanged.Subscribe(value => { sliderValue.Value = value; }).AddTo(this);

All three are built the same way: plug a value into the input port and the on-screen knob or button actually moves, and the result flows to the output. In other words:

  • You can plug OSC or MIDI values straight in. A control shown in a separate window or the Widget Panel moves in sync with external gear
  • Whether you move it by hand or drive it from outside, the behavior looks the same downstream
  • The output is not an “echo of the input” but the control’s current value. Changes you make by hand come out the same way

It is the same bidirectional idea as the Layer family of nodes.

Slider’s Min / Max

Min and Max are ports too. You can drive the movable range itself from another node during a performance. The knob’s current value is the Value port (or sliderValue), which can also be fed from outside.

  • The OSC input and output nodes have moved to the I/O category, and Tap Tempo to the Tempo category
  • Holding and re-sending values is in Variable, and testing is in Operation

Pages linking here

Also referenced from