Create
Initializes a new FFmpeg session for media processing operations. This is the starting point for building FFmpeg workflows.
Common Properties
- Name - The custom name of the node.
- Color - The custom color of the node.
- Delay Before (sec) - Waits in seconds before executing the node.
- Delay After (sec) - Waits in seconds after executing node.
- Continue On Error - Automation will continue regardless of any error. The default value is false.
If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.
Inputs
This node does not have any inputs.
Options
This node does not have any configurable options.
Output
- ffmpeg_id - Unique identifier for the FFmpeg session. This ID must be passed to Input nodes to add media files to the session.
How It Works
The Create node initializes a new FFmpeg session by generating a unique session identifier. This session serves as a container for your media processing pipeline, allowing you to:
- Add multiple input files
- Apply filters and transformations
- Define output files
- Execute the complete processing command
The session ID output from this node is used by subsequent nodes (Input, Filter, Output, Run) to build and execute the media processing pipeline.
Workflow Pattern
A typical FFmpeg workflow starts with the Create node:
Create → Input → Filter (optional) → Output → Run
Multiple branches can stem from a single Create node if you need to process the same inputs in different ways.
Example Usage
Basic Video Conversion Flow
Create an FFmpeg session to convert a video file:
- Create - Initialize session (outputs
ffmpeg_id) - Input - Add source video file using the
ffmpeg_id - Output - Define output file path
- Run - Execute the conversion
Multi-Input Processing
Process multiple video files in a single session:
- Create - Initialize session
- Input (1st file) - Add first video using
ffmpeg_id - Input (2nd file) - Add second video using the same
ffmpeg_id - Filter - Concatenate the streams
- Output - Define merged output file
- Run - Execute the merge
Usage Notes
- Each Create node generates a unique session ID
- The session is automatically cleaned up after the Run node executes
- You can create multiple independent sessions in the same flow for parallel processing
- The session ID is stored in the message scope and can be accessed by downstream nodes
- Sessions are lightweight - creating multiple sessions has minimal overhead
Best Practices
- Use One Create Per Pipeline: Each distinct media processing operation should start with its own Create node
- Store Session ID: The ffmpeg_id is automatically passed through the message context - ensure it flows to all related nodes
- Parallel Processing: Create separate sessions when processing multiple files independently for better performance
- Error Handling: Wrap Create and subsequent nodes in try-catch blocks to handle media processing errors gracefully
Example Scenarios
Scenario 1: Simple Format Conversion
Convert an AVI file to MP4 format.
Flow: Create → Input (video.avi) → Output (video.mp4) → Run
Scenario 2: Video with Audio Replacement
Replace audio track in a video file.
Flow:
- Create → Input (video.mp4) → Input (new_audio.mp3) → Output (result.mp4) → Run
Scenario 3: Batch Processing
Process multiple videos independently.
Flow for each video:
- Create → Input → Filter (resize) → Output → Run
Use a Loop node to iterate through multiple files, with each iteration creating its own session.
Common Errors
This node has no error conditions as it only generates a session identifier. However, ensure that:
- The ffmpeg_id output is properly connected to downstream Input nodes
- The session ID variable is not manually modified or cleared before use
Related Nodes
- Input - Adds media files to the session created by this node
- Run - Executes the FFmpeg command for this session
- Probe - Standalone node that doesn't require a Create session
- Play - Standalone node that doesn't require a Create session