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) and produce a new video with hardcoded subtitles for social media sharing or softcoded subtitles for streaming platforms.
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 will be stored. |
| Add Method | Method to add subtitles: Softcoded (subtitles as a separate selectable track) or Hardcoded (burned in). |
| Video Processing Options | Optional settings including: - 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 according to the "Video Output Name" property. The output contains the video with subtitles added either as a softcoded track or hardcoded into the video frames depending on the selected method.
No additional JSON structure is specified beyond the binary video data output.
Dependencies
- Requires access to an FFMPEG-based service or API capable of processing video and subtitle files.
- Needs an API authentication token or key configured in n8n credentials to interact with the FFMPEG service.
- Input video and subtitle files must be accessible either via URLs or provided as binary data within the workflow.
Troubleshooting
- Invalid Input URLs or Binary Fields: Ensure that the video and subtitle inputs are correctly specified as valid URLs or existing binary fields; otherwise, the node will fail to retrieve the necessary files.
- Unsupported Subtitle Formats: The subtitle file should be in a supported format (commonly SRT). Unsupported formats may cause errors during processing.
- API Authentication Errors: Missing or invalid API credentials will prevent the node from communicating with the FFMPEG service.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow to avoid overwriting data unintentionally.
- Performance Issues: High-resolution videos or complex subtitle files may increase processing time; consider adjusting bitrate, frame rate, or resolution options accordingly.