Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides functionality related to media file processing using ffmpeg. Specifically, for the "Metadata" resource and the "Extract Metadata" operation, it extracts metadata information from a given media file. This is useful when you want to analyze or retrieve details such as codec, duration, format, resolution, or other embedded metadata from audio or video files.
Common scenarios include:
- Automatically gathering media file properties before further processing.
- Validating media files by checking their metadata.
- Extracting technical details for reporting or cataloging media assets.
Example: You provide a URL or binary input of a video file, and the node outputs detailed metadata about that video, which can then be used in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Media File Input | A valid media URL or the name of the input binary field containing the media file to analyze. |
Output
The node outputs a JSON object containing the extracted metadata of the provided media file. This typically includes fields such as format, streams (video/audio), codec information, duration, bit rate, and other relevant technical details.
If the input was binary data, the output will still be JSON metadata describing that media content. The node does not output binary data itself for this operation.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on an external ffmpeg-based service or library to perform the metadata extraction.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Media Input: If the media URL or binary field name is incorrect or points to unsupported media, the node may fail to extract metadata. Ensure the input is a valid media file accessible by the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly configured.
- Timeouts or Service Unavailability: Since the node relies on an external ffmpeg service, network issues or service downtime can cause errors. Retry or check service status if extraction fails unexpectedly.
- Unsupported Formats: Some rare or proprietary media formats might not be supported by the ffmpeg backend, resulting in incomplete or failed metadata extraction.