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 mobile-friendly versions.
- Changing frame rates 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). |
| Transcoding Options | Collection of optional parameters: - 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 field named as specified by the "Video Output Name" property. The json output contains metadata about the operation but primarily the binary data holds the actual transcoded video content.
If the input was binary video data, the output binary field will contain the transcoded video file ready for further processing or saving.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on an external ffmpeg-based service or API configured via credentials.
- No additional environment variables are explicitly required based on static analysis.
Troubleshooting
- Invalid Video Input: If the input video URL is invalid or the binary field does not contain proper video data, the node may fail. Ensure the input is accessible and correctly referenced.
- Unsupported Codec: Specifying an unsupported or misspelled video codec can cause errors. Verify codec names against supported codecs by the underlying ffmpeg service.
- Resource Limits: Large video files or high-resolution settings might exceed memory or processing limits, causing timeouts or failures.
- Missing Credentials: The node requires a valid API key credential; missing or incorrect credentials will prevent execution.
Common error messages likely relate to input validation, codec support, or authentication failures. Checking logs and ensuring correct property values usually resolves these issues.