Node reference

How to use Temporal Motion Repair node in Oraphim

Use the Temporal Motion Repair node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID fusion.temporalmotionrepair.

Updated August 28, 2026

How to use Temporal Motion Repair node in Oraphim

Type ID: fusion.temporalmotionrepair
Category: Distort

What this node does

The Temporal Motion Repair 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 38 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_warp_stabilizer
Analysis Status analysisStatus String Analysis 0.0
Analysis Backend analysisBackend String Analysis 0.0
Analysis Confidence analysisConfidence Float Analysis 0.0
Analysis Smoothness analysisSmoothness Float Analysis 50.0
Coordinate Space coordinateSpace String Analysis Auto
Method method String Model Position Scale Rotation
Strength strength Float Model 100.0
Tracked X trackedX Float Tracked Motion 0.0
Tracked Y trackedY Float Tracked Motion 0.0
Tracked Rotation trackedRotation Float Tracked Motion 0.0
Tracked Scale trackedScale Float Tracked Motion 100.0
Tracked Skew X trackedSkewX Float Tracked Motion 0.0
Tracked Skew Y trackedSkewY Float Tracked Motion 0.0
Target X targetX Float Smoothed Motion 0.0
Target Y targetY Float Smoothed Motion 0.0
Target Rotation targetRotation Float Smoothed Motion 0.0
Target Scale targetScale Float Smoothed Motion 100.0
Target Skew X targetSkewX Float Smoothed Motion 0.0
Target Skew Y targetSkewY Float Smoothed Motion 0.0
Framing cropMode String Framing Stabilize Crop
Auto Scale autoScale Bool Framing 1.0
Maximum Auto Scale maxAutoScale Float Framing 130.0
Additional Scale additionalScale Float Framing 100.0
Scan Direction scanDirection String Rolling Shutter Top to Bottom
Scan Phase scanPhase Float Rolling Shutter 0.0
Top X topX Float Rolling Shutter Top 0.0
Top Y topY Float Rolling Shutter Top 0.0
Top Rotation topRotation Float Rolling Shutter Top 0.0
Top Scale topScale Float Rolling Shutter Top 100.0
Bottom X bottomX Float Rolling Shutter Bottom 0.0
Bottom Y bottomY Float Rolling Shutter Bottom 0.0
Bottom Rotation bottomRotation Float Rolling Shutter Bottom 0.0
Bottom Scale bottomScale Float Rolling Shutter Bottom 100.0
Row Smoothness rowSmoothness Float Rolling Shutter 25.0
Edge Mode edgeMode String Edges Mirror
Quality quality String Quality High
Preserve Alpha preserveAlpha Bool Alpha 1.0

How to use it

  1. Add Temporal Motion Repair from node search. Use fusion.temporalmotionrepair 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 Analysis Status, Analysis Backend, Analysis Confidence 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 Temporal Motion Repair. Feed a compatible source into Input. Change Analysis Status 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.