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.
Practical examples:
- Extracting a 30-second highlight from a recorded webinar.
- Trimming silence or ads from a podcast episode.
- Creating short teaser videos from full-length content.
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 cut. |
| Cut Start Time (in Sec) | The starting point (in seconds) from which the media will be trimmed. Must be ≥ 0. |
| Cut End Time (in Sec) | The ending point (in seconds) up to which the media will be trimmed. 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 as binary data under the specified output field name. The json output typically contains metadata about the processed file, 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 network access to the input media URLs or availability of the input binary data is necessary.
Troubleshooting
- Invalid Input URL or Binary Field: Ensure the input URL is accessible or the binary field name matches an existing input binary property.
- Start or End Time Errors: The start time must be less than the end time and both should be non-negative. Setting invalid values may cause errors or unexpected results.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields to avoid overwriting data unintentionally.
- API Authentication Failures: Verify that the API key credential is correctly configured and has sufficient permissions.
- Unsupported Media Format: If the input media format is unsupported by ffmpeg, the operation may fail.