Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Transcoding → Video Transcode
AI-generatedOverview
This node provides video transcoding functionality using ffmpeg. It allows users to convert input videos into different formats by specifying the desired video codec and various transcoding options such as bitrate, frame rate, and resolution. This is useful for scenarios where you need to prepare videos for different platforms or devices, optimize file size, or change encoding parameters.
Practical examples include:
- Converting a raw video file into an MP4 format with H.264 codec for web streaming.
- Reducing video resolution and bitrate to create smaller files suitable 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, hevc, vp9). |
| Transcoding Options | Collection of optional settings: - 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 typically contains metadata about the operation or the processed item, but the main content is the binary video data ready for further workflow steps or download.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on an external ffmpeg processing backend accessible via API.
- No additional environment variables are explicitly required based on the static code.
Troubleshooting
- Invalid Video Input: If the input video URL or binary field name is incorrect or inaccessible, the node will fail to retrieve the source video. Ensure the input is valid and accessible.
- Unsupported Codec: Specifying a video codec not supported by the backend may cause errors. Use standard codecs like h264 or hevc.
- Incorrect Transcoding Options: Providing invalid values for bitrate, frame rate, or resolution can lead to processing failures. Verify these values conform to expected formats and ranges.
- API Authentication Errors: Missing or invalid API credentials will prevent the node from communicating with the ffmpeg service. Confirm that the API key is correctly configured in n8n credentials.