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, choose the "Hardcoded" method, and receive a new video file with subtitles permanently embedded.
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. |
| 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 on/off) - Hardcoded (subtitles permanently embedded) |
| Video Processing Options | Collection of optional video processing parameters: - Video Bitrate (number) - Frame Rate (fps) (number) - Resolution (string, e.g., "640x480") |
Output
The node outputs a binary video file with subtitles added according to the selected method. The output binary data is stored under the specified output binary field name. The json output typically contains metadata about the processed video or confirmation of successful processing, but the main result is the binary video file with subtitles.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg-based video processing service.
- The node depends on ffmpeg functionality exposed via an external API or service 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 may fail to fetch or read the files.
- Unsupported Subtitle Formats: The subtitle file must be in a supported format (commonly SRT or similar). Unsupported formats may cause errors.
- Incorrect Output Field Name: The output binary field name must be unique and not conflict with existing fields to avoid overwriting data.
- API Authentication Errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Video Processing Failures: Errors related to bitrate, frame rate, or resolution settings may occur if invalid values are provided. Use standard video encoding parameters.
Links and References
- FFmpeg Documentation – For understanding video processing options and subtitle embedding.
- SubRip Subtitle Format (SRT) – Common subtitle file format used with this node.
- n8n Documentation on Working with Binary Data – Guidance on handling binary inputs and outputs in workflows.