Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides functionality to combine audio with video files using ffmpeg capabilities. Specifically, the "Combine Audio To Video" operation allows users to take a video input and an audio input (such as a subtitle or audio file) and merge them into a single video output that contains the new audio track.
Common scenarios where this node is beneficial include:
- Adding a separate audio commentary or soundtrack to an existing video.
- Merging external subtitle or audio tracks into videos for enhanced accessibility.
- Creating custom video content by combining different media sources.
For example, you might have a silent video file and a separate audio narration track; this node can combine them into one playable video file with sound.
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 or subtitle file URL or the name of the input binary field containing the audio/subtitle file. |
| Video Output Name | The name of the output binary field where the combined video file will be stored. |
Output
The node outputs a binary file in the specified output field containing the video merged with the provided audio track. The json output typically includes metadata about the processed file, but the main result is the binary data representing the combined video.
If the input was binary data, the output binary field will contain the newly created video file with the audio track embedded.
Dependencies
- Requires an API key credential for accessing the ffmpeg service.
- Relies on ffmpeg functionality exposed via an external API or service configured within n8n.
- The node expects valid URLs or binary fields for both video and audio inputs.
Troubleshooting
- Invalid Input URLs or Binary Fields: Ensure that the video and audio inputs are correctly specified either as accessible URLs or valid binary fields in the workflow.
- Unsupported File Formats: The node depends on ffmpeg's supported formats. Using unsupported video or audio formats may cause errors.
- API Authentication Errors: Verify that the API key credential is correctly set up and has permissions to use the ffmpeg service.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow to avoid overwriting data unintentionally.
Common error messages might indicate missing inputs, invalid URLs, or authentication failures. Checking the input parameters and credentials usually resolves these issues.
Links and References
- FFmpeg Official Documentation
- n8n Documentation on Working with Binary Data
- n8n Community Forum for user discussions and troubleshooting tips