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 are added as a separate selectable track, allowing viewers to toggle them on or off.
- Hardcoded: Subtitles are permanently burned into the video frames.
Common scenarios include enhancing accessibility by adding subtitles to videos, localizing content with translated subtitles, or preparing videos for platforms that require embedded subtitles.
For example, you can input a video file and a subtitle file (such as an SRT file), choose whether to hardcode or softcode the subtitles, optionally adjust video bitrate, frame rate, and resolution, and receive a processed video output with subtitles applied.
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 as selectable track) - Hardcoded (burned-in) |
| Video Processing Options | Optional settings for video encoding: - Video Bitrate (number) - Frame Rate (fps) (number) - Resolution (string, e.g., "640x480") |
Output
The node outputs the processed video file in a binary field named as specified by the "Video Output Name" property. This binary data contains the video with subtitles either softcoded or hardcoded according to the selected method.
The json output field typically includes metadata about the processed video, such as file size or format details, but the main output is the binary video data ready for further use or export.
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 within n8n.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Invalid Input URLs or Binary Fields: Ensure that the video and subtitle inputs are correctly specified as accessible URLs or valid binary fields in the workflow.
- Unsupported Subtitle Formats: The subtitle file must be in a supported format (commonly SRT). Unsupported formats may cause processing errors.
- API Authentication Errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Processing Failures: If the node fails during processing, check the video options for invalid values (e.g., unsupported resolution or frame rate).
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow data.