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 clips.
- 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 (default 480) - Fram Rate: frames per second (default 480) - Resolution: output video resolution (default "640x480") |
Output
The node outputs the transcoded video file in a binary 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 processing or saving.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on ffmpeg being available via the configured API endpoint.
- 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 video. Ensure the input is valid and accessible.
- Unsupported Codec: Specifying an unsupported or misspelled video codec may cause transcoding errors. Verify codec names against supported ffmpeg codecs.
- Resource Limits: Large videos or high-resolution settings might exceed memory or processing limits, causing timeouts or failures.
- Missing Credentials: The node requires a valid API authentication token; missing or invalid credentials will prevent execution.