Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides video processing capabilities specifically for adding subtitles to videos. It supports two subtitle embedding methods: softcoded (subtitles can be toggled on/off) and hardcoded (subtitles are permanently burned into the video). This functionality is useful in scenarios such as:
- Adding accessibility features by embedding subtitles into videos.
- Preparing videos for platforms that require hardcoded subtitles.
- Combining external subtitle files with video content dynamically.
For example, a user might input a video file and an SRT subtitle file, then choose to hardcode the subtitles into the video output for sharing on social media platforms that do not support separate subtitle tracks.
Properties
| Name | Meaning |
|---|---|
| Video Input | A valid video URL or the name of the input binary field containing the video file. |
| Subtitle Input | A valid subtitle file URL or the name of the input binary field containing the subtitle file (e.g., SRT). |
| Video Output Name | The name of the output binary field where the processed video file with subtitles will be stored. |
| Add Method | Method to add subtitles: "Softcoded" (subtitles can be toggled) or "Hardcoded" (subtitles burned in). |
| Video Processing Options | Collection of optional video settings: - Video Bitrate (number) - Frame Rate (fps, number) - Resolution (string, e.g., "640x480") |
Output
The node outputs a binary video file with the subtitles added according to the selected method. The output binary data is stored under the specified output field name. The JSON output typically contains metadata about the processed video, but the main result is the binary video file ready for further use or download.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg-based video processing service.
- The node depends on ffmpeg functionality exposed via an API endpoint configured in n8n credentials.
- Input video and subtitle files 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 subtitle inputs are correctly specified as accessible URLs or valid binary fields; otherwise, the node will fail to retrieve the files.
- Unsupported Subtitle Formats: Only certain subtitle formats (commonly SRT) may be supported. Using unsupported formats could cause errors.
- Incorrect Output Field Name: If the output field name conflicts with existing fields or is missing, the node may overwrite data or fail.
- API Authentication Errors: Missing or invalid API credentials will prevent the node from executing.
- Video Processing Failures: Errors related to ffmpeg processing (e.g., unsupported codecs, resolution mismatches) may occur if video options are set incorrectly.
To resolve these issues, verify all inputs, ensure correct credential setup, and check the video processing options for compatibility.