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 videos need to be optimized for different devices, platforms, or bandwidth constraints.
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 viewing.
- 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). |
| Transcoding Options | Collection of optional parameters: - Video Bitrate (number): target bitrate in kbps. - Fram Rate (number): frames per second. - Resolution (string): output resolution, e.g., "640x480". |
Output
The node outputs the transcoded video file in a binary data field named as specified by 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 or API.
- The node depends on an external ffmpeg-based service or library to perform the actual transcoding.
- No additional environment variables are explicitly required based on the static code analysis.
Troubleshooting
- Common issues:
- Invalid or inaccessible video input URL or missing binary input field.
- Unsupported or misspelled video codec names.
- Incorrect formatting of transcoding options like resolution or frame rate.
- Error messages:
- Errors related to missing input video or output field indicate misconfiguration of properties.
- Codec not supported errors suggest choosing a valid codec supported by the backend.
- Transcoding failures may occur if the input video format is unsupported or corrupted.
To resolve these, verify that the input video source is correct and accessible, ensure the codec and options are valid, and check the API credentials are properly configured.