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 compatible format for specific devices.
Practical examples:
- 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 a video 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 (number). - Fram Rate: frames per second (number). - Resolution: output resolution as width x height string (e.g., "640x480"). |
Output
The node outputs the transcoded video file in a binary field named according to the "Video Output Name" property. The json output contains metadata about the operation result, typically including success status and possibly details about the transcoded file. The binary data represents the actual transcoded video file 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 configured within n8n.
- No direct local ffmpeg installation is implied; all processing is done via the connected API.
Troubleshooting
- Invalid video input: Ensure the input video URL is accessible or the binary input field name is correct and contains valid video data.
- Unsupported codec or options: Verify that the specified video codec and transcoding options are supported by the backend ffmpeg service.
- API authentication errors: Confirm that the API key credential is correctly set up and has necessary permissions.
- Output binary field missing: Make sure the output field name is unique and does not conflict with existing fields in the workflow.
Common error messages might include:
- "Invalid input video": caused by incorrect input reference or inaccessible URL.
- "Codec not supported": due to unsupported codec value.
- "Authentication failed": related to invalid or missing API credentials.
Resolving these usually involves checking property values, ensuring proper credentials, and validating input data.