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. The json output typically contains metadata about the processed file or confirmation of successful processing, but the main content is the binary video data with the merged audio.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on the ffmpeg backend service accessible via the configured API.
- The node expects valid URLs or binary fields containing the video and audio inputs.
Troubleshooting
- Invalid Input URLs or Binary Fields: Ensure that the provided video and audio inputs are valid URLs or correctly named binary fields containing the respective media files.
- API Authentication Errors: Verify that the API key credential is correctly configured and has the necessary permissions.
- Unsupported Media Formats: The node relies on ffmpeg's supported formats; incompatible or corrupted media files may cause errors.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow data.
Common error messages might indicate missing inputs, authentication failures, or processing errors from ffmpeg. Resolving these usually involves checking input correctness, credential validity, and media compatibility.