Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > OpenKatana > OpenKatana · Inspect media

ComfyUI Node: OpenKatana · Inspect media

Class Name

OpenKatana_inspect_media

Category
OpenKatana/Tools
Author
rk0neki (Account age: 235days)
Extension
OpenKatana
Latest Updated
2026-11-05
Github Stars
0.05K

How to Install OpenKatana

Install this extension via the ComfyUI Manager by searching for OpenKatana
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter OpenKatana in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

OpenKatana · Inspect media Description

Inspects local media metadata, dimensions, duration, file size, and SHA-256 fingerprint.

OpenKatana · Inspect media:

OpenKatana_inspect_media checks the technical properties of a local media file without changing its contents. It helps you understand whether an asset is suitable for your planned edit, animation, or image workflow before you import or process it. For PNG, JPG, JPEG, and WebP images, it reads the image dimensions and color mode using Pillow; for other files, it uses a media-probing function to inspect available information such as duration, dimensions, rates, and media streams. It also calculates a SHA-256 fingerprint and checks the file size, helping you identify the exact asset you inspected. This is a technical inspection rather than a visual or creative analysis: it does not identify subjects, evaluate composition, detect scene changes, generate previews, or modify the media.

OpenKatana · Inspect media Input Parameters:

project_id

A required STRING passed through the shared OpenKatana tool interface. The underlying media-inspection method accepts only a source location and does not directly use a project identifier, so this field should not be interpreted as selecting a project asset or importing the inspected file into a project. Supply the project identifier appropriate to your OpenKatana workflow so the shared tool interface has the context it expects; the supplied code does not show how that interface validates or otherwise handles this identifier for inspection. No default value, minimum or maximum length, or list of permitted values is provided in the displayed node interface.

arguments

A required STRING containing the arguments for the inspection request. The underlying method requires a source string, so a practical JSON value is {"source":"/path/to/reference.mp4"}, with the example path replaced by the local file you want to inspect. Although source is not a separate node input, it is the essential setting inside this JSON text: it determines which file is opened, inspected, and fingerprinted. The file must be accessible to the environment running OpenKatana, which may differ from your own computer if ComfyUI runs remotely or inside a container. The shown inspection method does not accept trimming, resizing, or analysis settings. No default string, length limits, or selectable options are specified in the displayed node interface.

after

An optional STRING with a default of None in the execution method. It is accepted by the shared tool interface, but the displayed execution code does not read it, include it in the inspection arguments, or pass it to the underlying inspection call. Consequently, no change to the inspection results can be attributed to its text value from the supplied code. It may be available for workflow connections, but any additional scheduling behavior is not established by the provided implementation. Leave it unconnected unless your surrounding workflow requires it; no permitted values or minimum or maximum length are specified.

OpenKatana · Inspect media Output Parameters:

result_json

A STRING containing the tool response serialized through the shared response handler. The underlying inspection method returns four fields: source, the resolved source path; sha256, a SHA-256 fingerprint calculated from the file contents; bytes, the file size in bytes; and media, the technical inspection information. For files ending in .png, .jpg, .jpeg, or .webp, with case ignored, media contains width and height in pixels and mode, Pillow’s image-mode label, such as RGB or RGBA. Other file types receive the information returned by the media-probing function; the exact field layout of that information is not shown, so do not assume every file includes the same duration, frame-rate, or stream fields. The shared response handler’s outer JSON structure is also not provided. This output is useful for checking asset properties and identifying files, but it is not an image preview, an audio signal, or a playable video.

OpenKatana · Inspect media Usage Tips:

  • Enter a minimal inspection request in arguments, such as {"source":"/path/to/photo.png"}. Use double quotes around both the property name and the path to keep the JSON valid.
  • Prefer an absolute path that is accessible from the machine running ComfyUI. For a remote server or container, use the file’s location in that environment rather than its location on your personal computer.
  • Inspect your reference before choosing import or render settings. Image dimensions can help you select an appropriate canvas size, while video duration and rate information, when returned by the probe, can help you plan timing and frame-rate choices.
  • Use sha256 to compare file contents across inspections. Matching fingerprints are useful for confirming that two paths refer to identical file contents; matching filenames alone do not provide that assurance.
  • Remember that inspection also calculates a fingerprint of the file, which requires reading its contents. Very large files can therefore take longer to inspect even when their technical metadata is quick to read; avoid repeatedly inspecting the same unchanged asset when one result is sufficient.
  • For image files, use mode as a basic indicator of how pixels are stored. For example, RGBA indicates an alpha channel is present, but it does not establish that the image actually contains transparent pixels or that its color profile matches your project.
  • Use a separate preview or reference-analysis operation when you need to see frames, assess the visual content, or investigate cuts. This node provides technical information rather than visual verification.

OpenKatana · Inspect media Common Errors and Solutions:

Invalid JSON in arguments — exact message depends on the argument parser

  • Explanation: The shared interface processes the arguments before calling the inspection method. Missing quotation marks, trailing commas, or incorrectly escaped path characters can prevent a JSON request from being read; the supplied code does not show the parser’s exact error text.
  • Solution: Start with {"source":"/path/to/reference.mp4"} and replace only the path. For Windows paths written with backslashes inside JSON, escape each backslash, for example {"source":"C:\\media\\reference.mp4"}.

Missing required source argument — exact message depends on the invocation layer

  • Explanation: The inspection method requires source. Providing an empty object or using a different property name does not supply the file location, even if project_id is filled in.
  • Solution: Include a nonempty source string in arguments. A project identifier does not replace the media path.

unexpected inputs: ...

  • Explanation: This is the explicit error prefix in the displayed node implementation when additional named execution inputs are supplied outside the generated tool’s declared fields. It concerns extra node execution fields, not necessarily extra properties inside the JSON text.
  • Solution: Use only the listed node inputs: project_id, arguments, and optionally after. Put the source location inside arguments rather than adding a separate execution input.

Unexpected argument in the inspection request — exact message depends on the invocation layer

  • Explanation: The underlying inspection method accepts only source. Properties such as duration, start, or max_width belong to other operations and are not supported inspection settings.
  • Solution: Reduce the request to the source property. Perform trimming, resizing, or importing with an appropriate separate operation.

Source file not found or rejected — exact message depends on source-path validation

  • Explanation: The source resolver or a later file operation can fail if the path does not exist, is inaccessible in the runtime environment, or does not satisfy OpenKatana’s source-path rules. Those validation rules and their error messages are not included in the supplied code.
  • Solution: Confirm the file exists where OpenKatana is running, check its spelling and extension, and use an accessible local file path. If ComfyUI runs in a container, verify that the folder containing the file is mounted into that container.

Permission denied — possible file-access error

  • Explanation: Inspecting the file and calculating its fingerprint require read access. An existing file can still fail if the account running ComfyUI cannot read it.
  • Solution: Grant that account read access or copy the file into an accessible media folder. Make sure the containing folders also permit access.

Image cannot be identified or decoded — possible Pillow error

  • Explanation: Files with PNG, JPG, JPEG, or WebP extensions are opened as images. Opening can fail if the file is damaged, incomplete, or contains a different format than its filename suggests; the exact message depends on Pillow and the file.
  • Solution: Open the asset in an image application to verify it, then export a fresh copy in a supported image format. Changing the extension alone does not convert the file.

Media probing failed — exact message depends on the probe implementation

  • Explanation: Files outside the four explicitly handled image extensions are sent to the media-probing function. Inspection may fail if the file is unreadable, damaged, unsupported by the installed probing setup, or if a required probing dependency is unavailable. The supplied code does not expose the probe implementation or its exact errors.
  • Solution: Verify that the media plays or opens correctly, review the runtime logs for the specific probing failure, and check the media dependencies required by your OpenKatana installation. If necessary, create a valid copy in a supported format and inspect that copy.

OpenKatana · Inspect media Related Nodes

Go back to the extension to check out more related nodes.
OpenKatana
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

OpenKatana · Inspect media