Node reference

How to use Merge node in Oraphim

Use the Merge node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID fusion.merge.

Updated August 28, 2026

How to use Merge node in Oraphim

Type ID: fusion.merge
Category: Merge

What this node does

The Merge node is registered in Oraphim's Merge category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 4 sockets and 2 properties for this node. Its main registered inputs are Foreground, Background, Mask; its main outputs are Output. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Foreground in_fg Image
Background in_bg Image
Mask in_mask Mask

Outputs

Socket Key Type
Output out_color Image

Controls

Control Key Type Group Registry default
Operation operation String Controls 0.0
Mix mix Float Controls 1.0

How to use it

  1. Add Merge from node search. Use fusion.merge when you need the exact registry entry.
  2. Connect a compatible Image source to Foreground. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Operation, Mix 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 Merge. Feed a compatible source into Foreground. Change Operation 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.