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 video recorded without sound and a separate audio commentary track; this node can merge them into one video file ready for distribution.
Properties
| Name | Meaning |
|---|---|
| Video Input | A valid video URL or the name of the input binary field containing the video file to process. |
| Audio Input | A valid audio URL or the name of the input binary field containing the audio file to add. |
| Video Output Name | The name of the output binary field where the resulting combined video file will be stored. |
Output
The node outputs a binary file containing the video with the newly combined audio track. This output is accessible via the specified output binary field name (default is "data"). The json output typically contains metadata about the processed file or confirmation of successful processing, but the main result is the binary video data with audio embedded.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on the ffmpeg backend service configured within n8n to perform video and audio processing.
- Input video and audio can be provided either as URLs or as binary data fields 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. Incorrect names or inaccessible URLs will cause failures.
- Unsupported Media Formats: The node relies on ffmpeg's supported formats. Using unsupported video or audio formats may lead to errors or failed processing.
- Missing API Credential: The node requires a valid API authentication token for the ffmpeg service. Missing or invalid credentials will prevent execution.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow to avoid overwriting important data.