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 where you need to prepare videos for specific platforms, reduce file size, or change video quality settings.
Practical examples include:
- Converting a raw video file into an MP4 format with H.264 codec for web streaming.
- Reducing the resolution and bitrate of a video to optimize it for mobile devices.
- Changing the frame rate of a video to match broadcast standards.
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 data field named according to the "Video Output Name" property. The json output contains metadata about the operation but primarily the binary field holds the actual transcoded video content.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on an external ffmpeg processing backend accessible via API.
- Proper configuration of this API credential within n8n is necessary for the node to function.
Troubleshooting
- Invalid video input: If the input video URL or binary field is incorrect or inaccessible, the node will fail. Ensure the input video exists and is reachable.
- Unsupported codec or options: Using an unsupported video codec or invalid transcoding options may cause errors. Verify that the codec and options are supported by the ffmpeg backend.
- API authentication errors: Missing or invalid API credentials will prevent the node from working. Confirm that the API key is correctly configured.
- Output binary field conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow to avoid overwriting data.