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, preparing content for platforms that require embedded subtitles, or providing multiple subtitle options without altering the original video stream.
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 with subtitles embedded accordingly.
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 as selectable track) - Hardcoded (burned in) |
| Video Processing Options | Optional settings for video processing: - 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 is stored in the specified binary field name (Video Output Name).
- The
jsonoutput contains metadata about the processed video. - The binary output contains the actual video file with subtitles embedded either softly or hardcoded.
Dependencies
- Requires access to an Ffmpeg API service capable of video processing and subtitle embedding.
- Needs an API key or authentication token configured in n8n credentials to connect to the Ffmpeg service.
- The node depends on the external Ffmpeg processing backend exposed via the bundled router and action modules.
Troubleshooting
- Invalid video or subtitle input: Ensure the provided URLs or binary fields contain valid video and subtitle files respectively.
- Unsupported subtitle format: Confirm the subtitle file format is supported by the Ffmpeg backend (commonly SRT, ASS).
- API authentication errors: Verify that the API key or authentication token is correctly set up in n8n credentials.
- Processing failures: Check video processing options like bitrate, fps, and resolution for valid values; invalid parameters may cause errors.
- Output binary field missing: Make sure the output binary field name is unique and does not conflict with existing fields.