Clipmagic Api icon

Clipmagic Api

Interact with ClipMagic API for video and audio processing
Join our community

Actions8

Overview

This node integrates with the ClipMagic API to perform various video and audio processing operations such as compressing videos, converting media formats, trimming media, burning captions, removing silence, stitching videos, generating AI clips with subtitles, and creating split-screen videos. It is useful for automating media processing workflows, for example, compressing a video to reduce file size, trimming segments from a video, or generating karaoke-style subtitles for clips.

Use Case Examples

  1. Compress a video by providing its URL, selecting an encoding speed preset, setting the quality (CRF), and choosing the output format.
  2. Trim a video by specifying start and end times or multiple segments, and output the trimmed clip in a desired format.
  3. Burn subtitles into a video by providing the video URL and subtitle file URL, along with font and styling options.

Properties

Name Meaning
Video URL URL of the input video to be processed (required for compress operation).
Preset Encoding speed preset to balance speed and quality during compression.
CRF (Quality) Constant Rate Factor controlling video quality (lower is better quality).
Output Format Output container format for the compressed video.
Options Extra settings for the HTTP request, such as timeout in milliseconds.

Output

Binary

Binary data contains the processed media file (video/audio) returned from the ClipMagic API.

JSON

  • success - Indicates if the operation was successful.
  • operation - The operation performed, e.g., compress.
  • filename - Name of the output file.
  • contentType - MIME type of the output file.

Dependencies

  • ClipMagic API

Troubleshooting

  • Ensure the provided video URL is accessible and valid; inaccessible URLs will cause errors.
  • Timeout errors may occur if the processing takes longer than the specified timeout; increase the timeout value if needed.
  • Invalid parameter values (e.g., unsupported output format or invalid CRF) will cause API errors; verify input parameters.
  • If the API returns an error, check the error message in the node output for details and adjust parameters accordingly.

Links

Discussion