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 a video file, which is useful in scenarios such as adding background music, voiceovers, or replacing the original audio of a video.
Practical examples include:
- Adding a commentary audio track to a recorded video.
- Combining a separately recorded audio narration with a silent video.
- Replacing the audio in a video with a different soundtrack.
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 (with combined audio) will be stored. |
Output
The node outputs a binary file containing the processed video with the combined audio track. This output is stored in the binary property named as specified by the "Video Output Name" input property (default is "data"). The json output field typically contains metadata about the processed file or confirmation of successful processing, but the main content is the binary video data with the new audio track embedded.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Relies on ffmpeg functionality exposed via an external API or service configured within n8n.
- The node expects valid URLs or binary fields containing media files as inputs.
Troubleshooting
- Invalid Input URLs or Binary Fields: Ensure that the provided video and audio inputs are accessible URLs or correctly referenced binary fields. Invalid or inaccessible inputs will cause processing failures.
- Unsupported Media Formats: The node depends on ffmpeg's supported formats. Using unsupported video or audio formats may result in errors.
- Missing or Incorrect API Credentials: The node requires a valid API key credential 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 to avoid overwriting important data.
Common error messages might indicate issues like "input file not found," "unsupported codec," or "authentication failed." Resolving these involves verifying input paths, ensuring format compatibility, and checking credential validity.