Node reference
How to use 3D Camera Tracker node in Oraphim
Use the 3D Camera Tracker node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID fusion.cameratracker.
Updated August 28, 2026How to use 3D Camera Tracker node in Oraphim
Type ID: fusion.cameratracker
Category: Tracking
What this node does
The 3D Camera Tracker node is registered in Oraphim's Tracking category and performs the graph operation represented by its sockets and controls below.
The current Oraphim runtime registers 2 sockets and 41 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_3d_camera_tracker |
| Solve Status | solveStatus |
String |
Analysis | Not Analyzed |
| Solve Message | solveMessage |
String |
Analysis | Analyze footage to reconstruct a 3D camera. |
| Backend | solveBackend |
String |
Analysis | OpenCV Multi-View SfM |
| Shot Type | shotType |
Float |
Solve Model | 0.0 |
| Solve Method | solveMethod |
Float |
Solve Model | 0.0 |
| Frame Step | frameStep |
Float |
Analysis Range | 1.0 |
| Maximum Frames | maxFrames |
Float |
Analysis Range | 360.0 |
| Maximum Features | maxFeatures |
Float |
Feature Tracking | 1200.0 |
| Minimum Track Length | minTrackLength |
Float |
Feature Tracking | 4.0 |
| Assumed Field Of View | assumedFov |
Float |
Lens | 50.0 |
| Sensor Width | sensorWidth |
Float |
Lens | 36.0 |
| Sensor Height | sensorHeight |
Float |
Lens | 24.0 |
| Refine Focal Length | refineFocalLength |
Bool |
Lens | 1.0 |
| Refine Principal Point | refinePrincipalPoint |
Bool |
Lens | 0.0 |
| Solve Lens Distortion | refineLensDistortion |
Bool |
Lens | 1.0 |
| Maximum Lens Distortion | maximumRadialDistortion |
Float |
Lens | 0.75 |
| Reject Dynamic Tracks | rejectDynamicTracks |
Bool |
Optimization | 1.0 |
| Global Bundle Adjustment | enableGlobalBundleAdjustment |
Bool |
Optimization | 1.0 |
| Bundle Iterations | bundleAdjustmentIterations |
Float |
Optimization | 80.0 |
| Robust Loss Scale | robustLossScale |
Float |
Optimization | 2.0 |
| Detect Scene Planes | detectPlanes |
Bool |
Scene | 1.0 |
| RANSAC Threshold | ransacThreshold |
Float |
Advanced | 1.5 |
| Maximum Reprojection Error | maxReprojectionError |
Float |
Advanced | 3.0 |
| Minimum Parallax | minimumParallax |
Float |
Advanced | 3.0 |
| World Scale | worldScale |
Float |
Scene | 1000.0 |
| Quality Score | qualityScore |
Float |
Results | 0.0 |
| Median Reprojection Error | reprojectionError |
Float |
Results | 0.0 |
| Inlier Ratio | inlierRatio |
Float |
Results | 0.0 |
| Solved Frames | solvedFrameCount |
Float |
Results | 0.0 |
| 3D Points | landmarkCount |
Float |
Results | 0.0 |
| Scene Planes | planeCount |
Float |
Results | 0.0 |
| Dynamic Reject Ratio | dynamicRejectRatio |
Float |
Results | 0.0 |
| Bundle Cost Reduction | bundleCostReduction |
Float |
Results | 0.0 |
| Lens K1 | lensK1 |
Float |
Results | 0.0 |
| Lens K2 | lensK2 |
Float |
Results | 0.0 |
| Lens P1 | lensP1 |
Float |
Results | 0.0 |
| Lens P2 | lensP2 |
Float |
Results | 0.0 |
| Lens K3 | lensK3 |
Float |
Results | 0.0 |
| Solve Data | solveDataJson |
String |
Internal | 0.0 |
| Solved Camera Layer | solvedCameraLayerId |
String |
Internal | 0.0 |
How to use it
- Add 3D Camera Tracker from node search. Use
fusion.cameratrackerwhen you need the exact registry entry. - Connect a compatible
Imagesource to Input. Add the other inputs only when the operation needs them. - Start with the registry defaults and adjust Solve Status, Solve Message, Backend first so you can see the node's effect in isolation.
- Route Output (
Image) into a compatible downstream node, viewer, or output path. - 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 3D Camera Tracker. Feed a compatible source into Input. Change Solve 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.
Related nodes
- Optical Flow —
fusion.opticalflow - Advanced Color Correction —
fusion.advanced_color_correction - Audio Generate —
fusion.audio_generate - CC Blobbylize —
fusion.blobbylize - Channel Process —
fusion.channel_process
Return to the complete Oraphim node reference.