Actions13
- Video Actions
- Audio Actions
- Text Actions
- Image Actions
- Font Actions
Overview
This node, named "MediaFX," is designed to process video files by applying various transition effects between multiple video sources. It leverages FFmpeg capabilities to create smooth or stylistic transitions such as fades, wipes, slides, and other advanced effects that require FFmpeg 4.3 or newer. This node is useful in scenarios where you want to combine several video clips into a single output with visually appealing transitions, for example, creating highlight reels, promotional videos, or presentations.
Practical examples:
- Combining multiple short clips into one video with fade transitions.
- Creating a slideshow video from several video segments using wipe or slide effects.
- Producing a professional-looking video montage with custom transition durations and output formats.
Properties
| Name | Meaning |
|---|---|
| Video Sources | A collection of video inputs to be transitioned. Each source can be specified either by URL or binary data. |
| - Source Type | Choose whether the video source is provided as a URL or as binary data. |
| - Value | The URL string pointing to the video file (shown if Source Type is URL). |
| - Binary Property | The name of the binary property containing the video data (shown if Source Type is Binary Data). |
| Transition Effect | The type of transition effect to apply between videos. Options include Fade, Fade Black, Wipe Left, Slide Right, Circle Crop, Pixelize, Dissolve, Iris, etc. Some effects require FFmpeg 4.3+. |
| Transition Duration (seconds) | Duration of the transition effect in seconds, ranging from 0.1 to 10 seconds. |
| Output Format | The format of the output video file. Supported formats are MP4, MOV, AVI, and MKV. |
Output
The node outputs a binary video file resulting from applying the selected transition effect(s) on the input video sources. The output is available in the binary property named data (or similar), containing the processed video file in the chosen format (e.g., MP4). The json part of the output is empty ({}) since the main result is binary video data.
Dependencies
- Requires FFmpeg installed and accessible in the environment where n8n runs.
- No external API keys or services are needed; all processing is local via FFmpeg.
- The node uses helper functions to resolve input video paths from URLs or binary data.
- Some transition effects require FFmpeg version 4.3 or higher.
Troubleshooting
Common issues:
- Missing or inaccessible video source URLs or binary data will cause errors.
- Using transition effects that require FFmpeg 4.3+ on an older FFmpeg version will fail.
- Incorrect binary property names may lead to "No binary data found" errors.
- Output file write permissions or disk space issues could cause failures.
Error messages and resolutions:
"No binary data found in property '...'":Ensure the binary property name matches the actual input binary data property."Font file not found at path: ..."(not directly related to this operation but present in code): Verify the font file path if using font-related features."Operation 'multiTransition' on resource 'video' did not produce an output.": Check input sources and parameters; ensure valid video inputs and supported transition effects.- If the node fails silently or produces no output, verify FFmpeg installation and version compatibility.