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 can input a video file and an SRT subtitle file, choose to hardcode the subtitles, 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) or "Hardcoded" (subtitles burned in). |
| Video Processing Options | Collection of optional video settings: - Video Bitrate (number) - Frame Rate (fps, number) - Resolution (string, e.g., "640x480") |
Output
The node outputs a binary video file with the subtitles added according to the selected method. The output binary data is stored under the specified output field name. The JSON output typically contains metadata about the processed video, but the main result is the binary video data with subtitles embedded or attached.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg-based service.
- The node depends on ffmpeg functionality exposed via an API endpoint configured in n8n credentials.
- No other external dependencies are explicitly required.
Troubleshooting
- Invalid Input URLs or Binary Fields: Ensure that the video and subtitle inputs are either valid URLs accessible by the service or correctly named binary fields in the workflow.
- Unsupported Subtitle Formats: The subtitle file must be in a supported format (commonly SRT). Unsupported formats may cause errors.
- Incorrect Output Field Name: The output 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 necessary permissions.
- Video Processing Failures: If the video options (bitrate, fps, resolution) are set to unsupported values, the processing might fail. Use standard values.
Common error messages might include:
- "Failed to fetch input video/subtitle": Check URLs or binary field names.
- "Subtitle format not supported": Use a compatible subtitle file.
- "Authentication failed": Recheck API key configuration.