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 > ComfyUI-MAINodes > H3 Timeline Render (alpha)

ComfyUI Node: H3 Timeline Render (alpha)

Class Name

H3TimelineRender

Category
latent/minimax/timeline
Author
matlowai (Account age: 1004days)
Extension
ComfyUI-MAINodes
Latest Updated
2026-08-26
Github Stars
0.11K

How to Install ComfyUI-MAINodes

Install this extension via the ComfyUI Manager by searching for ComfyUI-MAINodes
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter ComfyUI-MAINodes 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

H3 Timeline Render (alpha) Description

Facilitates rendering timeline-based plans in ComfyUI, transforming pre-analyzed JSON plans into visual graphs for execution.

H3 Timeline Render (alpha):

H3TimelineRender is a node designed to facilitate the rendering phase of a timeline-based plan within the ComfyUI framework. This node is part of a two-phase execution process where it handles the second phase, which involves compiling and rendering the plan into a graph format. The primary purpose of H3TimelineRender is to take a pre-analyzed plan, typically in JSON format, and transform it into a visual representation that can be executed or further manipulated. This node is particularly beneficial for users who want to visualize and execute complex plans without manually re-entering frame numbers or other intricate details. By automating the rendering process, H3TimelineRender streamlines the workflow, allowing for efficient and accurate execution of plans. It acts as a thin client, meaning it relies heavily on external rules and models defined elsewhere in the system, ensuring that the node itself remains lightweight and focused on its core task of rendering.

H3 Timeline Render (alpha) Input Parameters:

plan_path

The plan_path parameter specifies the file path to the plan document that needs to be rendered. This document is typically in JSON format and contains all the necessary details about the timeline, such as the sequence of events, durations, and other relevant metadata. The function of this parameter is to provide the node with the source data it needs to perform the rendering process. There are no explicit minimum or maximum values for this parameter, but it must be a valid file path pointing to a correctly formatted plan document. The default value is not applicable as this parameter is required for the node to function.

graph_path

The graph_path parameter is an optional input that allows you to specify the destination path where the rendered graph will be saved. If not provided, the node will generate a default path based on the plan's base name. This parameter impacts the node's execution by determining where the output graph file will be stored, which can be useful for organizing and managing multiple outputs. There are no specific constraints on this parameter, but it should be a valid file path.

port

The port parameter defines the network port used for communication during the rendering process. It is an integer value, with a typical default of 8189. This parameter is crucial for ensuring that the node can communicate with other components of the system, especially if network-based operations are involved. The minimum value is 1, and the maximum is 65535, which are standard port range limits.

recorder_path

The recorder_path parameter specifies the file path for the recorder, which is used to log or track the rendering process. This parameter is important for debugging and auditing purposes, as it allows you to review the steps taken during the rendering. Like graph_path, this should be a valid file path, and if not provided, a default path is used.

H3 Timeline Render (alpha) Output Parameters:

graph_path

The graph_path output parameter provides the file path to the rendered graph. This output is crucial as it represents the final product of the rendering process, which can be used for further execution or analysis. The graph file contains the visual representation of the plan, ready for use in the ComfyUI environment.

cmd

The cmd output parameter is a command string that can be used to launch the rendered graph. This output is important for users who want to quickly execute or test the rendered plan without manually setting up the environment. It provides a convenient way to initiate the graph execution directly from the node's output.

report

The report output parameter contains a detailed report of the rendering process, including information about the plan's ID, revision, and whether it was recompiled. This output is valuable for users who need to verify the rendering process, check for any issues, or simply document the execution details for future reference.

H3 Timeline Render (alpha) Usage Tips:

  • Ensure that the plan_path points to a valid and correctly formatted JSON file to avoid errors during rendering.
  • Use the graph_path parameter to organize your output files, especially if you are working with multiple plans, to keep your workspace tidy.
  • If you encounter network issues, verify that the port parameter is set to an available and correct port number.

H3 Timeline Render (alpha) Common Errors and Solutions:

ValueError: H3 Drawn Plan: <error_message>

  • Explanation: This error occurs when there is an issue with the plan document, such as incorrect formatting or missing data.
  • Solution: Check the plan document for any syntax errors or missing fields. Ensure that the JSON is correctly formatted and contains all necessary information.

FileNotFoundError: [Errno 2] No such file or directory: <file_path>

  • Explanation: This error indicates that the specified file path for the plan or recorder does not exist.
  • Solution: Verify that the file paths provided for plan_path and recorder_path are correct and that the files exist at those locations.

OSError: [Errno 98] Address already in use

  • Explanation: This error occurs when the specified port is already in use by another process.
  • Solution: Change the port parameter to a different number that is not currently in use, or close the application using the port.

H3 Timeline Render (alpha) Related Nodes

Go back to the extension to check out more related nodes.
ComfyUI-MAINodes
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.

H3 Timeline Render (alpha)