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 or audio file, or the name of the binary field containing the media. |
| 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 user (default is "data"). The json output contains metadata about the processed item, typically including information such as filename, mime type, and possibly duration or format details depending on the implementation.
If the input was binary data, the output binary field will contain the trimmed media file ready for further use or download.
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.
- No additional environment variables are explicitly required based on the static code analysis.
Troubleshooting
- Invalid Input: If the input URL or binary field name is incorrect or inaccessible, the node will fail to retrieve the media. Ensure the input source is valid and accessible.
- Start/End Time Errors: Providing a start time greater than or equal to the end time, or negative values, may cause errors. Always ensure start < end and both are non-negative.
- Unsupported Formats: If the input media format is not supported by the underlying ffmpeg service, the node may throw an error.
- API Credential Issues: Missing or invalid API authentication tokens will prevent the node from functioning. Verify that the API key credential is correctly set up in n8n.
- Output Field Conflicts: Using an output binary field name that conflicts with existing fields might overwrite data unintentionally. Use unique names for output fields.
Links and References
- FFmpeg Official Documentation
- n8n Documentation - Working with Binary Data
- n8n Community Forum for troubleshooting and examples