Actions7
Overview
This node integrates with the ClipMagic API to perform various video and audio processing tasks. Specifically, the "Compress Video" operation reduces the file size of a given video by re-encoding it with specified quality and speed presets. This is useful for optimizing videos for web delivery, saving storage space, or preparing files for faster streaming.
Typical use cases include:
- Compressing large raw video files before uploading to a website or cloud storage.
- Reducing bandwidth usage when sharing videos over limited networks.
- Preparing videos for mobile devices where smaller file sizes are preferred.
For example, you can input a URL of a high-resolution video and specify compression parameters like encoding speed preset and quality factor to get a smaller output video in MP4 format.
Properties
| Name | Meaning |
|---|---|
| Video URL | URL of the input video to be compressed. |
| Preset | Encoding speed preset controlling compression speed vs. quality trade-off. Options: Ultra Fast, Super Fast, Very Fast, Faster, Fast, Medium, Slow, Slower, Very Slow, Placebo. Default is Medium. |
| CRF (Quality) | Constant Rate Factor controlling output quality (lower is better). Typical values: 18 (nearly lossless), 23 (default), 28 (low quality). Default is 23. |
| Output Format | Output container format for the compressed video. Options: MP4, MOV, AVI. Default is MP4. |
| Options | Extra settings for the request. Currently supports: Timeout (ms) - how long to wait before aborting the HTTP call; 0 means no limit. Default is 600000 ms (10 minutes). |
Output
The node outputs JSON data describing the result of the compression operation. The output includes:
success: Boolean indicating if the operation succeeded.operation: The operation performed ("compress").filename: The name of the output file returned by the API.contentType: MIME type of the output video (e.g., "video/mp4").
Additionally, the node outputs binary data under the binary.data field containing the compressed video file itself. This allows downstream nodes to access or save the compressed video directly.
Dependencies
- Requires an API key credential for authenticating with the ClipMagic API.
- The node makes HTTP requests to the ClipMagic service base URL configured in the credentials.
- No other external dependencies are required.
Troubleshooting
- Timeouts: If the video is large or the network slow, the default timeout may be insufficient. Increase the "Timeout (ms)" option to allow more time for the API response.
- Invalid URLs: Ensure the "Video URL" points to a direct accessible video file. URLs requiring authentication or non-direct links may cause failures.
- Unsupported formats: Input videos must be supported by the ClipMagic API. Unsupported formats or corrupted files will cause errors.
- API errors: Errors from the API are returned as JSON with error messages. Check the message for details such as invalid parameters or quota limits.
- Binary data missing: If the output does not contain binary data, verify that the content-type header indicates a video/audio stream. Otherwise, the response might be an error or metadata only.
Links and References
- ClipMagic API Documentation (general reference for API capabilities)
- FFmpeg CRF Guide (explains CRF quality parameter used in compression)