ClipMagic icon

ClipMagic

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

Actions7

Overview

This node integrates with the ClipMagic API to perform various video and audio processing tasks. Specifically, the "Convert Media" operation allows users to convert media files from one format to another, optionally adjusting video resolution and bitrate. This is useful for workflows that require media format standardization, preparing files for different platforms, or optimizing media for size and quality.

Practical examples include:

  • Converting a WAV audio file to MP3 for web streaming.
  • Changing a video from MOV to MP4 format while scaling it down to 720p for mobile compatibility.
  • Adjusting the bitrate of a video to reduce file size without changing its format.

Properties

Name Meaning
Options Extra settings for the request. Currently supports: Timeout (ms) - how long to wait before aborting the HTTP call (0 means no limit).
Media URL Direct URL to the media file or a Google Drive share link to be converted.
Output Format Target container format for the output media. Options: MP3, WAV, AAC, MP4, MOV
Resolution Video height to scale to (ignored for audio). Options: Original (no scaling), 360p, 480p, 720p, 1080p
Bitrate (kbps) Target video bitrate in kilobits per second (max 3000). Set to 0 for automatic bitrate selection

Output

The node outputs an array with one item per input. Each output item contains:

  • json:

    • success: Boolean indicating if the operation succeeded.
    • operation: The operation performed ("convert").
    • If the response is JSON (e.g., metadata or status), it includes the parsed response fields.
    • If the response is binary media data, it includes:
      • filename: The name of the output file (extracted from response headers or defaulted).
      • contentType: The MIME type of the returned media.

  • binary (only for media data responses):

    • data: The binary content of the converted media file, ready for further use or saving.

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 additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Timeouts: If conversions take too long, increase the timeout option or set it to 0 for no limit.
  • Invalid URLs: Ensure the Media URL is accessible and points directly to a supported media file or a valid Google Drive share link.
  • Unsupported formats: Verify that the input media format is supported by ClipMagic and that the requested output format is valid.
  • API errors: Errors from the API will be returned as JSON with an error message. Check your API key validity and quota.
  • Binary data handling: If the output is not recognized as media, check the content-type header and ensure the API response is correct.

Links and References

Discussion