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.
- Creating audio snippets from podcasts or music tracks.
- Trimming recordings to remove intros or outros.
For example, a user can input a URL or binary field containing a video, specify start time as 30 seconds and end time as 90 seconds, and get a new trimmed video clip of 1 minute duration.
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 "Video or Audio Output Name" property. The json output typically contains metadata about the processed file, such as filename or mime type, but the main content is in the binary data representing the cut media segment.
If the input was a video, the output binary data will be a video file trimmed to the specified time range. Similarly, if the input was audio, the output will be an audio file segment.
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 in n8n credentials.
- No additional environment variables are explicitly required beyond the API authentication.
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 accessible and correctly specified.
- 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.
- API Authentication Errors: Missing or invalid API credentials will prevent the node from functioning. Verify that the API key credential is properly set up.
- Unsupported Formats: Some media formats might not be supported by the underlying ffmpeg service, leading to processing failures.
- Output Field Naming: Using an output binary field name that conflicts with existing fields may cause unexpected behavior. Use unique names.