Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides functionality related to media files using ffmpeg capabilities. 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 processing or transcoding.
- Extracting technical details for cataloging or reporting purposes.
- Validating media files by checking their metadata before further workflow steps.
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 downstream in your workflow.
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 JSON data 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 describing the media content.
If the input was binary, the output will still be JSON metadata describing that binary media file.
Dependencies
- Requires an API key credential for accessing the ffmpeg service integrated within the node.
- The node depends on ffmpeg-related libraries bundled internally to perform media analysis.
- No additional external services are explicitly required beyond the configured API authentication.
Troubleshooting
- Invalid Media Input: If the media URL is invalid or the binary field does not contain a proper media file, the node may fail to extract metadata. Ensure the input points to a valid media source.
- Authentication Errors: Missing or incorrect API credentials will prevent the node from functioning. Verify that the required API key or token is correctly set up in n8n credentials.
- Unsupported Formats: Some rare or proprietary media formats might not be supported by ffmpeg, leading to incomplete or failed metadata extraction.
- Timeouts or Large Files: Very large media files might cause timeouts or performance issues. Consider preprocessing or limiting file size.