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 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. |
| 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 the filename and MIME type. The binary data represents the actual media file segment extracted between the specified start and end times.
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: If the input URL or binary field name is incorrect or inaccessible, the node will fail to retrieve the media file. Ensure the input source is valid and accessible.
- Start/End Times: Providing a start time greater than or equal to the end time will likely cause errors or produce empty output. Verify that the start time is less than the end time.
- Unsupported Formats: If the media format is not supported by the ffmpeg backend, the node may throw errors. Confirm that the input media format is compatible.
- Credential Issues: Missing or invalid API credentials will prevent the node from executing. Check that the required API key or authentication token 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.