Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides various ffmpeg-related video processing functionalities within n8n. Specifically, for the "Video Processing" resource and the "Combine Audio To Video" operation, it allows users to merge an audio track with a video file. This is useful when you have separate audio and video sources and want to produce a single combined media file.
Common scenarios include:
- Adding background music or narration to a silent video.
- Replacing the original audio track of a video with a different audio source.
- Combining externally sourced audio (e.g., voiceover) with video footage.
Practical example: You have a recorded video without sound and a separate audio commentary file. Using this node, you can combine them into one video file that contains both the visuals and the new audio track.
Properties
| Name | Meaning |
|---|---|
| Video Input | A valid video URL or the name of the input binary field containing the video file. |
| Audio Input | A valid audio URL or the name of the input binary field containing the audio file. |
| Video Output Name | The name of the output binary field where the combined video file will be stored. Default is "data". |
Output
The node outputs a combined video file in the specified output binary field. The json output typically contains metadata about the processed file, such as filename, mime type, and possibly duration or codec information depending on implementation details.
If the node supports binary data output, the combined video with the merged audio track will be available as binary data under the output field named by the user (default "data").
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on an external ffmpeg API or service configured via credentials in n8n.
- No other external dependencies are explicitly required based on static analysis.
Troubleshooting
- Invalid Input URLs or Binary Fields: Ensure that the video and audio inputs are either valid URLs accessible by the service or correctly named binary fields in the incoming data.
- Missing or Incorrect Credentials: The node requires a valid API key credential for the ffmpeg service; missing or invalid credentials will cause authentication errors.
- Unsupported Media Formats: If the input video or audio formats are not supported by the ffmpeg backend, the node may fail to process the files.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields to avoid overwriting important data.
Common error messages might include:
- Authentication failures due to invalid API keys.
- File not found or inaccessible errors for input URLs.
- Format or codec unsupported errors from ffmpeg.
Resolving these usually involves verifying credentials, checking input paths/fields, and ensuring compatible media formats.