Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides video and audio processing capabilities using ffmpeg. Specifically, the "Cut Video/Audio" operation allows users to trim a segment from a given video or audio file by specifying start and end times in seconds. This is useful for extracting highlights, removing unwanted sections, or creating clips from longer media files.
Common scenarios include:
- Extracting a specific scene from a recorded video.
- Trimming silence or noise from an audio recording.
- Creating short promotional clips from longer videos.
For example, if you have a 10-minute video but only want the segment from 2:00 to 3:30, this node can cut that portion and output it as a new media file.
Properties
| Name | Meaning |
|---|---|
| Video or Audio Input | A valid URL pointing to the input video/audio file or the name of the binary field containing the media to process. |
| Cut Start Time (in Sec) | The starting point (in seconds) from which to begin cutting the media. Must be zero or positive. |
| Cut End Time (in Sec) | The ending point (in seconds) at which to stop cutting the media. Must be zero or positive. |
| Video or Audio Output Name | The name of the output binary field where the resulting trimmed media file will be stored. |
Output
The node outputs the trimmed video or audio segment in a binary field named as specified by the user (default is "data"). The output contains the media file data corresponding to the cut segment between the specified start and end times.
If the input was binary data, the output will also be binary data representing the trimmed media. If the input was a URL, the node downloads and processes the media, then outputs the trimmed result similarly.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service or API.
- The node depends on ffmpeg functionality exposed via an external service or API configured in n8n credentials.
- Proper network access to fetch media files from URLs if input is provided as a URL.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Invalid Input URL or Binary Field: Ensure the input URL is accessible and points to a valid media file, or that the specified binary field exists and contains valid media data.
- Start or End Times Out of Range: The start and end times must be within the duration of the media. Setting them outside the media length may cause errors or empty output.
- API Authentication Errors: Verify that the API key credential is correctly configured and has permissions to use the ffmpeg service.
- Unsupported Media Format: The input media must be in a format supported by ffmpeg. Unsupported formats may cause processing failures.
- Network Issues: If input is a URL, ensure the node can reach the URL without firewall or proxy issues.