Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides functionality to add filters and effects to media files using ffmpeg capabilities. It supports both video and audio media types, allowing users to specify custom filter chains to transform the input media. Common scenarios include resizing videos, applying grayscale or other visual effects to video streams, or adding audio filters such as volume adjustments or equalization.
Practical examples:
- Scaling a video to 640x480 resolution and converting it to grayscale.
- Applying an audio filter chain to normalize sound levels or add echo effects.
Properties
| Name | Meaning |
|---|---|
| Media File Input | A valid media URL or the name of the input binary field containing the media file. |
| Media File Output | The name of the output binary field that will contain the processed media file. |
| Media File | The type of media being processed; options are "Video" or "Audio". |
| Filter and Effects (video) | A comma-separated list of video filters and effects to apply (e.g., scale=640:480, grayscale). Only shown if Media File is Video. |
| Filter and Effects (audio) | A comma-separated list of audio filters and effects to apply. Only shown if Media File is Audio. |
Output
The node outputs the processed media file in a binary field named according to the "Media File Output" property. The json output field typically contains metadata about the operation or the processed media but primarily the transformed media content is available in the specified binary output field.
If the media is video, the output binary data represents the filtered/transformed video stream. If audio, it represents the filtered/transformed audio stream.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on an external ffmpeg processing backend accessible via API.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid media input: Ensure the input media URL or binary field name is correct and accessible.
- Filter syntax errors: Filters must be specified correctly as per ffmpeg filter syntax; invalid filters will cause processing failures.
- Unsupported media type: Selecting a media type inconsistent with the actual input may cause errors.
- API authentication issues: Verify that the API key credential is valid and has necessary permissions.
- Output binary field conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow.
Common error messages might relate to:
- "Failed to load input media" — check input source.
- "Filter parsing error" — verify filter string correctness.
- "Authentication failed" — check API credentials.