Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides video processing capabilities using ffmpeg, specifically supporting an operation to combine audio with a video. The "Combine Audio To Video" operation allows users to merge an audio track into an existing video file, producing a new video output that includes the added audio.
Common scenarios for this node include:
- Adding background music or narration to silent videos.
- Replacing or overlaying audio tracks in video files.
- Combining separate audio and video sources into a single media file for publishing or further editing.
For example, you might have a recorded video without sound and a separate audio commentary track; this node can merge them into one video file with synchronized audio.
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 resulting video file (with combined audio) will be stored. |
Output
The node outputs a binary file representing the video with the combined audio track. This output is stored in the specified output binary field name (default is "data"). The json output typically contains metadata about the processed file or success status, but the main content is the binary video data with the newly merged audio.
Dependencies
- Requires access to an ffmpeg API service configured via an API key credential in n8n.
- The node depends on the external ffmpeg processing backend to perform the actual media merging.
- Input video and audio must be accessible either as URLs or as binary data within the workflow.
Troubleshooting
- Invalid Input URLs or Binary Fields: Ensure that the video and audio inputs are correctly specified as valid URLs or existing binary fields in the workflow. Incorrect references will cause processing failures.
- Unsupported Media Formats: The ffmpeg backend may not support certain video or audio formats. Verify compatibility before processing.
- API Authentication Errors: If the ffmpeg API credentials are missing or invalid, the node will fail to connect. Confirm that the required API key is properly set up in n8n.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields to avoid overwriting important data.