Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node integrates ffmpeg functionality into n8n workflows, focusing here on adding filters and effects to media files. It supports both video and audio media types, allowing users to apply custom filter chains to transform the input media. Typical use cases include resizing videos, applying grayscale or other visual effects to video streams, or modifying audio streams with various audio filters.
For example, a user might input a video file URL or binary data, specify filters like scale=640:480,grayscale
for video, and receive the processed video as output. Similarly, audio files can be processed with audio-specific filters.
Properties
Name | Meaning |
---|---|
Media File Input | A valid media URL or the name of the input binary field containing the media file to process. |
Media File Output | The name of the output binary field where the processed media file will be stored. |
Media File | Selects the type of media to process: either "Video" or "Audio". |
Filter and Effects (videoF) | For video media only: a comma-separated list of ffmpeg video filters/effects to apply. Example: scale=640:480,grayscale . |
Filter and Effects (audioF) | For audio media only: a comma-separated list of ffmpeg audio filters/effects to apply. |
Output
The node outputs the processed media file in a binary field named as specified by the "Media File Output" property. The json
output contains metadata about the operation but primarily the binary data holds the transformed media content. This binary data represents the filtered video or audio stream after applying the specified ffmpeg filters.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on an external ffmpeg processing backend accessible via this API.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid media input: Ensure the input is a valid URL or a correctly named binary field containing media data.
- Filter syntax errors: Incorrectly formatted filter strings may cause ffmpeg to fail. Verify filter syntax according to ffmpeg documentation.
- Unsupported media type: Selecting a media type that does not match the input file format may lead to errors.
- API authentication failures: Confirm that the API key credential is correctly configured and has necessary permissions.
- Empty output: If no output is produced, check that filters are correctly applied and input media is valid.