Node reference

How to use Detail-preserving Upscale node in Oraphim

Use the Detail-preserving Upscale node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID fusion.detailpreservingupscale.

Updated August 28, 2026

How to use Detail-preserving Upscale node in Oraphim

Type ID: fusion.detailpreservingupscale
Category: Distort

What this node does

The Detail-preserving Upscale node is registered in Oraphim's Distort category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 2 sockets and 7 properties for this node. Its main registered inputs are Input; its main outputs are Output. 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

Controls

Control Key Type Group Registry default
Effect Type effectType String Internal fx_detail_preserving_upscale
Fit fitMode String Scale Manual
Scale scale Float Scale 100.0
Reduce Noise reduceNoise Float Detail 0.0
Detail detail Float Detail 50.0
Alpha alphaMode String Alpha Bicubic
Quality quality String Quality High

How to use it

  1. Add Detail-preserving Upscale from node search. Use fusion.detailpreservingupscale 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 Fit, Scale, Reduce Noise 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 Detail-preserving Upscale. Feed a compatible source into Input. Change Fit 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.