Overview
This node uses the FFprobe command-line tool to extract detailed metadata from media files such as videos or audio. It is useful for scenarios where you need to analyze media file properties like format, streams (video/audio/subtitle tracks), chapters, and program information without manually running FFprobe commands.
Practical examples include:
- Automatically gathering video codec, resolution, and duration information for media management workflows.
- Extracting audio stream details for transcoding or quality checks.
- Collecting chapter markers or program data for complex multimedia files.
The node runs FFprobe with user-configured options and returns the parsed output in JSON, XML, or CSV formats.
Properties
| Name | Meaning |
|---|---|
| 输入文件路径 | Path to the media file to analyze. Must be a valid existing file path. |
| 输出格式 | Output format of FFprobe results. Options: JSON, XML, CSV. |
| 显示信息类型 | Types of information to show. Multiple selections allowed: Format info, Streams, Chapters, Programs. Default is Format and Streams. |
| 隐藏横幅 | Whether to hide the FFprobe version banner in the output. Boolean true/false. |
| 自定义参数 | Additional custom FFprobe command-line arguments (optional). Example: -select_streams v:0 |
Output
The node outputs an array with one item per input. Each item contains:
json:inputPath: The analyzed media file path.command: The full FFprobe command line executed.data: The parsed FFprobe output. If output format is JSON, this is a parsed object; otherwise, it is a raw string of XML or CSV.
binary: Empty object (no binary data output).
If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message instead of data.
Dependencies
- Requires FFprobe installed and accessible in the system's PATH.
- No external API keys or credentials needed.
- Runs FFprobe as a child process on the host machine.
Troubleshooting
- File Not Found: If the input file path does not exist, the node throws an error. Ensure the path is correct and accessible by n8n.
- Empty Input Path: The node requires a non-empty input file path.
- FFprobe Execution Failure: Errors during FFprobe execution (e.g., invalid parameters) will cause the node to fail with the FFprobe error message.
- JSON Parsing Error: When output format is JSON but FFprobe returns invalid JSON, the node throws a parsing error.
- Custom Arguments: Incorrect custom FFprobe arguments may cause execution failure. Validate arguments carefully.
- Hide Banner Option: If set to false, FFprobe version info appears in stderr but does not affect JSON parsing.
To resolve errors:
- Verify file paths and permissions.
- Check custom FFprobe arguments syntax.
- Confirm FFprobe installation and version compatibility.