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 to keep the segment from 2 minutes to 3 minutes 30 seconds, you can use this operation to cut that exact portion.
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 starting point (in seconds) from which to begin cutting the media. Must be zero or positive. |
| Cut End Time (in Sec) | The ending point (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 trimmed media file will be stored. |
Output
The node outputs the trimmed video or audio segment as binary data under the specified output field name. The json output typically contains metadata about the processed file, such as its name or size, while the actual media content is available in the binary property named as per the "Video or Audio Output Name" input.
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 successful execution.
Troubleshooting
- Invalid Input URL or Binary Field: Ensure the input media URL is accessible or the binary field name correctly references existing binary data.
- Start or End Times Out of Range: The start and end times must be within the duration of the input media and start must be less than end.
- Missing or Invalid Credentials: Verify that the API key or authentication token is correctly set up in n8n credentials.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields to avoid overwriting data unintentionally.
If errors occur related to media processing, check the input media format compatibility and network accessibility of URLs.
Links and References
- FFmpeg Official Documentation
- n8n Documentation - Working with Binary Data
- n8n Community Forum for troubleshooting and examples