NCA Toolkit icon

NCA Toolkit

Process media files using the No Code Architects Toolkit API
Join our community

Actions15

Overview

This node integrates with the No Code Architects Toolkit API to process media files, specifically to detect silence intervals within audio or video media. It is useful for scenarios where identifying periods of silence in media is important, such as editing audio/video content, analyzing speech patterns, or automating media processing workflows. For example, it can detect silence longer than a specified duration in a podcast or video file to help with editing or content analysis.

Use Case Examples

  1. Detect silence intervals longer than 0.5 seconds in a media file hosted at a given URL.
  2. Specify a start and end time within the media to limit silence detection to a particular segment.
  3. Adjust noise threshold and mono audio processing options to fine-tune silence detection sensitivity.

Properties

Name Meaning
Media URL URL of the media file to process, required to specify the media source.
Duration Minimum duration in seconds for a silence interval to be considered valid, controls sensitivity to silence length.
Detection Options Additional parameters to customize silence detection, including start and end times, noise threshold in decibels, and whether to process audio as mono.
Webhook URL Optional URL to receive a webhook notification when processing is complete.
Custom Job ID Optional custom identifier for tracking the request.
Request Options Settings for batching, SSL certificate validation, proxy usage, and request timeout to control how the API request is made.

Output

JSON

  • silenceIntervals - Array of detected silence intervals with start and end times.
  • jobId - Identifier for the processing job, useful for tracking.
  • status - Status of the silence detection operation.

Dependencies

  • No Code Architects Toolkit API
  • API key credential for authentication

Troubleshooting

  • Ensure the Media URL is accessible and correctly formatted; inaccessible URLs will cause request failures.
  • Verify that the duration value is above the minimum threshold (0.1 seconds) to avoid invalid input errors.
  • If using a webhook URL, ensure it is reachable and correctly configured to receive notifications.
  • Check API key validity and permissions if authentication errors occur.
  • Adjust noise threshold and mono settings if silence detection results are inaccurate or inconsistent.

Links

Discussion