Actions7
Overview
The "Remove Silence" operation in the ClipMagic node allows users to detect and remove silent sections from video or audio files. This is particularly useful for cleaning up recordings by automatically trimming out pauses, dead air, or background noise below a certain threshold. Common scenarios include preparing podcasts, interviews, lectures, or any media where silence removal improves flow and listener/viewer engagement.
For example, a user might provide a URL to a recorded webinar and configure the node to remove all silent parts longer than 0.35 seconds with a noise threshold of -45dB, resulting in a more concise and polished final video.
Properties
| Name | Meaning |
|---|---|
| Video URL | Direct file URL or Google Drive link to the video file to process. |
| Noise Threshold | The noise level threshold (e.g., "-45dB") used by FFmpeg's silencedetect filter to identify silence. |
| Silence Duration (s) | Minimum duration in seconds that audio must stay below the noise threshold to be considered silence. |
| Encoding Preset | Encoding speed/quality trade-off preset. Options: Ultra Fast, Super Fast, Very Fast, Faster, Fast, Medium, Slow, Slower, Very Slow. |
| CRF (Quality) | Quality setting for the libx264 encoder (range 0-51, lower means better quality). |
| Output Format | Container format for the output media. Options: MP4, MOV, MP3, WAV. |
| Output Filename | Desired filename for the output file without extension (optional). |
| Options > Timeout (ms) | How long to wait before aborting the HTTP call. Set to 0 for no limit. |
Output
The node outputs JSON data indicating success and details about the operation, including:
success: Boolean indicating if the operation succeeded.operation: The string"remove_silence".filename: The name of the output file.contentType: MIME type of the returned media (e.g., video/mp4, audio/wav).
If the output includes binary data (the processed media file), it is provided under the binary.data field, containing the actual media content encoded appropriately for n8n to handle.
Dependencies
- Requires an API key credential for authenticating with the ClipMagic API.
- The node makes HTTP requests to the ClipMagic service endpoint.
- No additional local dependencies; all processing is done remotely via the API.
Troubleshooting
- Timeouts: If the operation takes too long, consider increasing the timeout option or setting it to 0 for no limit.
- Invalid URLs: Ensure the provided video URL is accessible and direct (Google Drive links must be shareable).
- Unsupported Formats: The input video/audio must be in a format supported by ClipMagic.
- API Errors: Errors returned from the API will be surfaced as error messages. Check your API key validity and quota.
- Output Filename Issues: Avoid special characters in the output filename to prevent issues with file saving.
Links and References
- FFmpeg silencedetect filter documentation
- ClipMagic official website and API docs (refer to your ClipMagic account resources)