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.
For example, a user can input a full-length video URL or binary data, specify start time as 30 seconds and end time as 90 seconds, and get a trimmed video clip of 1 minute duration as output.
Properties
Name | Meaning |
---|---|
Video or Audio Input | A valid video or audio URL, or the name of the input binary field containing the media file. |
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. |
Video or Audio Output Name | The name of the output binary field where the 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 cut media file corresponding to the specified start and end times.
json
output: Typically includes metadata about the processed item(s).binary
output: Contains the actual trimmed media file under the specified output field name.
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.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Invalid Input: If the input URL or binary field does not contain a valid video/audio file, the node may fail. Ensure the input is correctly specified and accessible.
- Start/End Times: Providing a start time greater than or equal to the end time will likely cause errors. Make sure the start time is less than the end time and both are within the media duration.
- Output Field Name Conflicts: Using an output binary field name that conflicts with existing fields might overwrite data unintentionally. Use unique names.
- API Authentication Errors: If the API key or credentials are missing or invalid, the node will not execute successfully. Verify credential configuration.
- Unsupported Formats: Some media formats might not be supported by the underlying ffmpeg service, leading to processing failures.