Node reference

How to use Luma Keyer node in Oraphim

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

Updated August 28, 2026

How to use Luma Keyer node in Oraphim

Type ID: fusion.lumakeyer
Category: Keying

What this node does

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

The current Oraphim runtime registers 0 sockets and 5 properties for this node. Its main registered inputs are no fixed inputs; its main outputs are no fixed outputs. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

This node has no fixed input sockets in the current runtime registry.

Outputs

This node has no fixed output sockets in the current runtime registry.

Controls

Control Key Type Group Registry default
High Threshold high Float Thresholds 1.0
Low Threshold low Float Thresholds 0.0
Softness softness Float Matte 0.0
Invert invert Bool Matte 0.0
Show Matte showMatte Bool Matte 0.0

How to use it

  1. Add Luma Keyer from node search. Use fusion.lumakeyer when you need the exact registry entry.
  2. Place the node as a source/context operation; it has no fixed input socket in the current registry.
  3. Start with the registry defaults and adjust High Threshold, Low Threshold, Softness first so you can see the node's effect in isolation.
  4. Because there is no fixed output socket, validate the graph context or downstream resource that this node is intended to affect.
  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 Luma Keyer. Change High Threshold away from its registry default and compare the result. 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.