Node reference

How to use Slider Control node in Oraphim

Use the Slider Control node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID fusion.expr.slider.

Updated August 28, 2026

How to use Slider Control node in Oraphim

Type ID: fusion.expr.slider
Category: Utility

What this node does

Publishes a reusable slider control value for other graph operations.

The current Oraphim runtime registers 3 sockets and 10 properties for this node. Its main registered inputs are Input; its main outputs are Output, Slider. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Input in_color Image

Outputs

Socket Key Type
Output out_color Image
Slider out_value Float

Controls

Control Key Type Group Registry default
Control Type effectType String Control fx_slider_control
Layer ID layerId String Routing 0.0
Master Node ID masterNodeId String Routing 0.0
Publish to Template publishToTemplate Bool Publishing 1.0
Comment controlComment String Publishing 0.0
Slider sliderValue Float Value 0.0
Minimum sliderMin Float Range -100.0
Maximum sliderMax Float Range 100.0
Step sliderStep Float Range 1.0
Clamp Output clampOutput Bool Range 0.0

How to use it

  1. Add Slider Control from node search. Use fusion.expr.slider when you need the exact registry entry.
  2. Connect a compatible Image source to Input. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Control Type, Layer ID, Master Node ID first so you can see the node's effect in isolation.
  4. Route Output (Image) into a compatible downstream node, viewer, or output path.
  5. Preview a representative frame, change one input/control at a time, and save/reopen reusable graphs to verify persistence.

Practical example

Create a small test graph with Slider Control. Feed a compatible source into Input. Change Control Type away from its registry default and compare the result. Connect Output to a compatible downstream stage so the result is visible. Keeping this test graph small makes socket-type, context, and parameter mistakes easier to diagnose before the node is used in a production graph.

Troubleshooting

  • If a connection is rejected, compare the exact socket data types in the tables above; Oraphim graph connections are typed.
  • If the result looks unchanged, confirm this node is on the active path to the viewer/output and that the expected graph/resource is selected.
  • If a control is unavailable, check required inputs and whether the property belongs to an internal or mode-dependent group.
  • If a saved graph behaves differently later, reopen it and verify node identity, connections, and edited property values before rendering.

Return to the complete Oraphim node reference.