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 that support 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 will be stored. |
Add Method | Method to add subtitles: - Softcoded (subtitles as a separate selectable track) - Hardcoded (subtitles burned into video) |
Video Processing Options | Additional video processing parameters: - Video Bitrate (number, e.g., 480) - Frame Rate (fps, number, e.g., 480) - Resolution (string, e.g., "640x480") |
Output
The node outputs a binary video file with the subtitles added according to the selected method. The output is stored in the specified output binary field name.
- The
json
output typically contains metadata about the processed video or operation status. - The binary output contains the actual video file with subtitles embedded either softly or hardcoded.
Dependencies
- Requires access to an FFMPEG 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 backend.
- 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 and accessible. Invalid URLs or missing binary fields will cause processing failures.
- Unsupported Subtitle Formats: Only certain subtitle formats (commonly SRT) may be supported. Using unsupported formats might result in errors.
- API Authentication Errors: Missing or incorrect 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.
- Performance Issues: High-resolution videos or high bitrate/frame rate settings may increase processing time or resource usage.