Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides video transcoding functionality using ffmpeg. It allows users to convert input videos into different formats or codecs with customizable parameters such as video codec, bitrate, frame rate, and resolution. This is useful for scenarios like preparing videos for web streaming, reducing file size, or converting videos to a format compatible with specific devices.
Practical examples include:
- Transcoding an uploaded video to H.264 codec with a specific bitrate and resolution for optimized playback on mobile devices.
- Changing the frame rate of a video to match broadcast standards.
- Converting videos from one container format to another while adjusting quality settings.
Properties
| Name | Meaning |
|---|---|
| Video Input | A valid video URL or the name of the input binary field containing the video to transcode. |
| Video Output Name | The name of the output binary field where the transcoded video file will be stored. |
| Video Codec | The codec to use for transcoding the video (e.g., h264, vp9). |
| Transcoding Options | Collection of optional parameters: - Video Bitrate: target bitrate in kbps (default 480) - Fram Rate: frames per second (default 480) - Resolution: output resolution string (e.g., "640x480") |
Output
The node outputs the transcoded video file in a binary data field named according to the "Video Output Name" property. The json output contains metadata about the operation result, but the main content is the binary video data ready for further processing or saving.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on an external ffmpeg-based service or API that performs the actual transcoding.
- No direct local ffmpeg installation is implied; all processing is done via the configured API.
Troubleshooting
- Invalid Video Input: If the input video URL or binary field is incorrect or inaccessible, the node will fail to fetch the video. Ensure the input source is valid and accessible.
- Unsupported Codec or Parameters: Using an unsupported video codec or invalid transcoding options may cause errors. Verify supported codecs and parameter ranges with the ffmpeg service documentation.
- API Authentication Errors: Missing or invalid API credentials will prevent the node from connecting to the transcoding service. Confirm that the API key is correctly configured in n8n credentials.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow to avoid overwriting data unintentionally.