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 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 video/audio file or the name of the input 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 ≥ 0. |
| Cut End Time (in Sec) | The ending point (in seconds) at which to stop cutting the media. Must be ≥ 0 and greater than start time. |
| 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 "Video or Audio Output Name" property (default is "data"). The output contains the media file data corresponding to the cut segment.
The json output field typically includes metadata about the processed item, but the main content is delivered as binary data representing the trimmed media file.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on ffmpeg functionality exposed via an external API or service configured within n8n.
- Proper configuration of the API authentication token or credentials is necessary for the node to function.
Troubleshooting
- Invalid Input URL or Binary Field: Ensure the input media URL is accessible or the binary field name is correct and contains valid media data.
- Start and End Times: Both must be numbers ≥ 0, and the end time should be greater than the start time. Otherwise, the node may throw errors or produce empty output.
- API Authentication Errors: If the API key or credentials are missing or invalid, the node will fail to connect to the ffmpeg service.
- Unsupported Media Format: The input media must be in a format supported by ffmpeg; otherwise, processing will fail.
- Output Binary Field Naming: Make sure the output field name does not conflict with existing fields to avoid overwriting data unintentionally.
Links and References
- FFmpeg Official Documentation
- n8n Documentation - Working with Binary Data
- n8n Community Forum for troubleshooting and examples