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 · Import hdr media

ComfyUI Node: OpenKatana · Import hdr media

Class Name

OpenKatana_import_hdr_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 · Import hdr media Description

Imports HDR media into OpenKatana, preserving source data for HDR editing and rendering.

OpenKatana · Import hdr media:

OpenKatana_import_hdr_media brings source media into an OpenKatana project for HDR-aware editing and rendering. HDR, or high dynamic range, allows a picture to represent a wider range of brightness than a conventional image, helping retain bright highlights and subtle lighting differences. This tool provides a dedicated import route for HDR workflows rather than treating the material as an ordinary image batch. The supplied tests confirm that an imported HDR source is preserved byte-for-byte and that the import prepares a document that can be passed to OpenKatana’s HDR renderer. This makes the node useful when you want to prepare footage for HDR processing while retaining the original material for reference and subsequent production work. Importing is a preparation step, not a final render or a guarantee that every display will show HDR correctly.

OpenKatana · Import hdr media Input Parameters:

project_id

A required STRING identifying the OpenKatana project that receives the imported media. Use the identifier of the project you intend to work in so that the imported source and its associated project data are stored together. The supplied examples create a project before importing into it, so creating or confirming your project first is the demonstrated workflow. This input is separate from the JSON settings supplied through arguments. The provided node interface does not specify a default value, permitted identifier format, or minimum or maximum length.

arguments

A required STRING containing the HDR import settings as a JSON object. The underlying tool signature exposes source as the required media-source string, along with optional settings: source_color accepts "pq", "hlg", "bt709", "srgb", or JSON null and defaults to null; fps is an integer defaulting to 30; start defaults to 0; duration defaults to 3; peak_nits defaults to 1000; and rights defaults to "review_pending". These are settings inside this text input, not additional node sockets. source identifies the material to import; a filesystem path is demonstrated in the tests. source_color provides an explicit source color interpretation: PQ and HLG are HDR transfer characteristics, while BT.709 and sRGB are commonly associated with standard-range material. fps controls the imported clip’s frame rate, and start and duration select the excerpt timing in seconds; the supplied test imports four frames with fps set to 4 and duration set to 1. peak_nits supplies a peak-brightness setting in nits, although the implementation excerpt does not establish its precise processing effect. rights records the supplied rights status; it does not establish legal permission to use the media. For example, enter {"source":"/media/pq.mkv","fps":4,"start":0,"duration":1} for a short test import. No default text, numeric limits, or text-length limits are specified for the node’s arguments input, and the tool signature does not establish numeric minimums or maximums for its settings.

after

An optional STRING accepted by the shared OpenKatana tool interface. The displayed execution method accepts this value but does not directly read it or pass it into the HDR import arguments. Consequently, the supplied source does not establish any effect on color interpretation, frame selection, import results, or execution ordering. Leave it unconnected unless your broader OpenKatana workflow provides documented guidance for using it; do not assume that it adds media-processing settings. No default value, permitted options, or minimum or maximum length is shown.

OpenKatana · Import hdr media Output Parameters:

result_json

A STRING carrying the tool response in JSON form. This is a textual result, not a ComfyUI IMAGE, VIDEO, or AUDIO output, so subsequent processing must use the information inside the response rather than treating the socket as image pixels or a playable clip. The underlying import API returns a dictionary, and the supplied tests demonstrate that a successful import contains original, asset, and hdr_document information: original identifies the retained source relative to the project, asset contains clip information including the frame count at asset.clip.n, and hdr_document is the document passed to render_hdr in the tested workflow. These details let you check what was imported and prepare the next HDR-processing step. The shared response-formatting function is not included, so the exact JSON envelope around those import details is not established by the supplied source; inspect the returned structure before selecting nested fields.

OpenKatana · Import hdr media Usage Tips:

  • Create or confirm your project before importing, and use its exact identifier in project_id. The demonstrated HDR workflow explicitly creates the project first.
  • Start with a short excerpt to check source compatibility and color interpretation before processing more footage. The tested configuration uses {"source":"/media/pq.mkv","fps":4,"duration":1} and produces a four-frame clip.
  • Keep tool settings inside arguments as valid JSON. Use double-quoted property names and strings, unquoted numbers, and null rather than Python’s None when explicitly leaving source_color unspecified.
  • Set source_color explicitly when you have reliable information about the footage’s transfer characteristics. For example, use "pq" for known PQ footage or "hlg" for known HLG footage; do not choose either simply because you want an HDR-looking result.
  • Treat peak_nits as a brightness-related import setting, not as a promise that the result will reach that brightness or look correct on every screen. Its default is 1000, but the supplied excerpt does not document the exact mapping behavior, so verify your rendered result before production use.
  • Inspect result_json after a successful import, especially the clip frame count and the returned HDR document. The tests demonstrate passing the returned hdr_document to render_hdr rather than rendering the entire import response.
  • Plan audio handling separately when necessary. The supplied test demonstrates adding an audio path to the HDR document before rendering, but it does not establish that this import automatically preserves or attaches source audio.
  • Keep rights records accurate and obtain the permissions your project requires. A value such as "review_pending" is provenance information, not legal clearance.

OpenKatana · Import hdr media Common Errors and Solutions:

unexpected inputs: …

  • Explanation: This is an explicit error pattern in the node source. It occurs when additional fields are passed to the execution method that are not recognized by the generated tool interface. The authoritative interface exposes only project_id, arguments, and optional after.
  • Solution: Remove extra node-level fields. Put HDR import settings such as source, fps, and duration inside the JSON object in arguments instead of adding them as separate sockets.

Invalid JSON in arguments — possible validation failure

  • Explanation: The exact parser error is not shown in the supplied source, but malformed JSON can prevent the arguments text from being interpreted. Common mistakes include single quotes, missing commas, trailing commas, and using None instead of null.
  • Solution: Begin with a small valid object such as {"source":"/media/pq.mkv","fps":4,"duration":1}. Add other settings one at a time, retaining double quotes around property names and string values.

Missing source — possible argument-validation failure

  • Explanation: The underlying import_hdr_media signature requires source and supplies no default for it. Providing a project identifier alone does not identify the media to import. The exact missing-argument message depends on the shared argument-handling code, which is not included.
  • Solution: Add a source entry to arguments, for example {"source":"/media/pq.mkv"}, and make sure it identifies the intended media file.

Source file not found or inaccessible — possible import failure

  • Explanation: The demonstrated workflow reads a source file from disk. Importing can fail if the path is incorrect, the file has moved, or the process running OpenKatana cannot read it. The supplied excerpts do not show the exact error text.
  • Solution: Confirm that the file exists and is readable from the environment running OpenKatana. If it runs on a remote machine or inside a container, use a path available there rather than a path that exists only on your own computer.

Project unavailable — possible project lookup failure

  • Explanation: The import targets a project, and the supplied tests create that project before calling the tool. An incorrect identifier or unavailable project can prevent the import from reaching its intended destination; the exact failure message is not provided.
  • Solution: Create or confirm the project first, check the spelling of project_id, and ensure you are using the same OpenKatana project storage as the rest of your workflow.

Unsupported source_color value — possible validation failure

  • Explanation: The tool signature restricts source_color to "pq", "hlg", "bt709", "srgb", or null. Labels such as "HDR" or "Rec.2020" are not listed choices, and a color-gamut label is not interchangeable with a transfer-characteristic setting. The exact validation message is not shown.
  • Solution: Use one of the documented values that matches your footage. If the correct interpretation is unknown, omit the setting or use null rather than supplying an unsupported label, then verify the result.

Invalid numeric settings — possible validation or processing failure

  • Explanation: fps is declared as an integer, while start, duration, and peak_nits are numeric settings. Incorrect types or values unsuitable for the selected footage may cause validation or processing problems. The supplied source does not document exact numeric bounds or associated error messages.
  • Solution: Use JSON numbers rather than quoted text, use an integer for fps, and begin with a short excerpt known to exist in the source. If needed, return to the documented defaults of 30 fps, a start of 0 seconds, a duration of 3 seconds, and a peak setting of 1000 nits.

HDR appears washed out, too dark, or incorrectly contrasted

  • Explanation: This is a visual troubleshooting symptom rather than a confirmed exception message. Incorrect source interpretation or an unsuitable viewing workflow can make HDR material appear wrong even when importing succeeds. The supplied tests verify HDR processing behavior, not correct appearance on every display or viewer.
  • Solution: Check the footage’s actual color characteristics, correct source_color if necessary, and assess a rendered test using an HDR-capable viewing setup. Do not change color labels randomly or assume that successful import alone verifies the final appearance.

result_json cannot be connected as an image or video

  • Explanation: The node returns only a STRING containing the tool response. It does not expose an IMAGE, VIDEO, or AUDIO socket, so a media-processing node expecting those types cannot directly use it as media.
  • Solution: Inspect or parse the JSON response and use its returned project references or HDR document with the appropriate OpenKatana processing step. Follow the demonstrated HDR rendering workflow rather than connecting this output directly to an image or video input.

OpenKatana · Import hdr 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 · Import hdr media