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 or codecs with customizable parameters such as video codec, bitrate, frame rate, and resolution. This is useful for scenarios like preparing videos for web streaming, reducing file size, or converting videos to a format compatible with specific devices.
For example, you can input a video URL or binary video data, specify the desired output codec (e.g., H.264), set the target resolution (e.g., 640x480), and get a transcoded video file ready for use in your workflow.
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, vp9). |
| Transcoding Options | Collection of optional settings: - Video Bitrate: Target bitrate for the video (number). - Fram Rate: Frames per second (number). - Resolution: Target resolution in width x height format (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.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node 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: Ensure the input video URL is accessible or the binary input field contains valid video data.
- Unsupported codec or options: Verify that the specified video codec and transcoding options are supported by the backend.
- API authentication errors: Confirm that the API key credential is correctly configured and has necessary permissions.
- Output binary field missing: Make sure the output field name is unique and does not conflict with other fields in the workflow.