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:
- Creating short promotional clips from longer videos.
- Extracting specific audio segments from podcasts or music tracks.
- Removing intros/outros from recorded videos.
Example: Given a 10-minute video, you can cut out a 30-second clip starting at 2 minutes and ending at 2 minutes 30 seconds, outputting just that segment as a new 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 be processed. |
| Cut Start Time (in Sec) | The start time in seconds from which to begin cutting the media. Must be zero or positive. |
| Cut End Time (in Sec) | The end time 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 cut media file will be stored. |
Output
The node outputs the trimmed video or audio segment in a binary data field named as specified by the user (default is "data"). The output contains the media file corresponding to the selected segment between the start and end times.
jsonoutput field: Typically contains metadata about the processed file or confirmation of successful processing.- Binary output: Contains the actual cut media file ready for further use or download.
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 this API credential in n8n 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: The start time must be less than the end time and both should be within the duration of the input media; otherwise, the node may throw errors or produce empty output.
- API Credential Issues: If authentication fails, verify that the API key or token is correctly set up in n8n credentials.
- Unsupported Media Format: The input media must be in a format supported by ffmpeg; unsupported formats will cause processing failures.
- Output Field Naming: The output binary field name must be unique and 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