Frame Command
Defines a command that may run during frame processing.
← Fusion node reference
Utility / AutomationAdvanced
RunCommand
Trigger external commands from Fusion
Runs external commands or scripts at start, end or per-frame processing stages and can pass numeric or string parameters into the command.
RunCommand
DaVinci Resolve · Fusion
RunCommand is a pipeline-oriented utility for integrating Fusion with external tools, scripts and automation. It can trigger a command at defined processing stages and optionally wait for completion.
Overview
What RunCommand does
Frame Command can execute during frame processing, while Start Command and End Command provide lifecycle hooks around a render or processing range.
Parameter placeholders allow Fusion values or user-provided strings to be inserted into the external command. This makes the node useful for render-farm hooks, file conversion, notifications and custom pipeline integration.
External command execution is powerful and should be treated carefully. Paths, quoting, permissions and blocking behavior must be tested on the actual deployment environment.
Mental model
Think of RunCommand as a controlled doorway from the Fusion Flow to the operating system: Fusion reaches a defined stage, then launches an external tool with the parameters you provide.
Common uses
Trigger a post-render script
Launch an external conversion utility
Call a pipeline notification hook
Generate sidecar files
Integrate custom command-line tools with a Fusion render
Flow anatomy
Inputs & outputs
The port structure shows how this node fits into a Fusion graph.
Image Input
Source image for the operation.
Effect Mask
Optional mask that limits where the node affects the image.
RunCommand
Fusion node
Image Output
The processed result from this node.
Inspector
Important parameters
Start with these controls before reaching for more complicated workarounds.
Start Command
Runs at the beginning of the relevant process or range.
End Command
Runs when the process or range completes.
Hide
Controls whether the spawned command window is hidden where supported.
Wait
Controls whether Fusion waits for the command to finish.
A blocking command can stall rendering if the external process hangs.
Command
Sets the command line, executable or script that RunCommand launches.
Browse
Opens a file browser for the related path or resource.
Interactive
Controls interactive command behavior where supported.
Number A (%a)
Sets the numeric value substituted wherever %a appears in the command.
Number B (%b)
Sets the numeric value substituted wherever %b appears in the command.
Number C (%c)
Sets the numeric value substituted wherever %c appears in the command.
Number D (%d)
Sets the numeric value substituted wherever %d appears in the command.
String (%s)
Sets the text substituted wherever %s appears in the command.
Practical setup
A reliable workflow
- 1
Test the external command manually in the operating system first.
- 2
Choose whether it belongs at Start, End or per-frame execution.
- 3
Add only the parameters the external tool requires.
- 4
Decide whether Fusion should Wait for completion.
- 5
Test on a short range before using it in production.
Typical node chain
Fusion event→
RunCommand→
External process
Examples
Where this node fits in real work
Post-render hook
Trigger an external packaging script after a Fusion output completes.
Fusion resultSaverRunCommand
Troubleshooting
Common mistakes
Running untested shell commands from a production comp
Forgetting quoting around paths with spaces
Enabling Wait on a command that may hang
Using per-frame execution for a command that should run only once
Assuming commands are portable across operating systems
Production notes
Practical tips
Keep commands version-controlled outside the comp when possible.
Use absolute or well-defined paths in production environments.
Treat RunCommand as automation infrastructure and document exactly what it launches.
Related nodes