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 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 optimize videos for different devices, reduce file size, or change encoding formats for compatibility.
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 preview files.
- Changing frame rates to match specific playback requirements.
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). |
| 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 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 or API.
- The node depends on an external ffmpeg processing backend accessible via this credential.
- No additional environment variables are explicitly required based on the static code analysis.
Troubleshooting
- Invalid Video Input: If the input video URL or binary field name is incorrect or inaccessible, the node will fail to process. Ensure the input source is valid and reachable.
- Unsupported Codec: Specifying an unsupported or misspelled video codec may cause errors. Verify codec names against supported ffmpeg codecs.
- Incorrect Transcoding Options: Providing invalid values for bitrate, frame rate, or resolution can lead to failures. Use sensible numeric values and standard resolution formats.
- Credential Issues: Missing or invalid API credentials will prevent the node from connecting to the ffmpeg service. Confirm that the API key is correctly configured in n8n.
Common error messages might indicate connection failures, invalid input formats, or codec errors. Reviewing the node's configuration and ensuring all inputs meet expected formats usually resolves these issues.