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 > MiniMax H3 Context Loop > MiniMax H3 Project Asset Carousel (Tree)

ComfyUI Node: MiniMax H3 Project Asset Carousel (Tree)

Class Name

MiniMaxH3ProjectAssetTree

Category
conditioning/minimax/context_loop/project
Author
ethanfel (Account age: 3434days)
Extension
MiniMax H3 Context Loop
Latest Updated
2026-10-06
Github Stars
0.51K

How to Install MiniMax H3 Context Loop

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

MiniMax H3 Project Asset Carousel (Tree) Description

Specialized node for managing project assets in MiniMax H3 framework, optimizing performance and resource usage.

The MiniMaxH3ProjectAssetTree is a specialized node designed to manage and organize project assets within the MiniMax H3 framework. It serves as an opt-in source-tree layout that shares the Carousel's storage and sockets, providing a structured approach to handling various media types such as images, videos, audio, and semantic anchors. This node is particularly beneficial for AI artists who need to synchronize large project assets across different stages of their creative workflow. By leveraging the capabilities of the MiniMaxH3ProjectAssetTree, you can efficiently manage and access your project assets, ensuring that only the necessary references are decoded during sampling, which optimizes performance and resource usage.

run_name

The run_name parameter is a required input that specifies the name of the current run or session. It plays a crucial role in identifying and managing the assets associated with a particular project iteration. The default value is an empty string, and it is essential to provide a meaningful name to ensure proper tracking and organization of project assets.

semantic_anchor_size

This parameter defines the size of the semantic anchors used within the project. It inherits its value from the parent configuration, ensuring consistency across different nodes. The default size is set to "512", which provides a balanced resolution for most use cases. Adjusting this parameter can impact the precision and detail of semantic anchors in your project.

semantic_anchor_mode

The semantic_anchor_mode parameter determines the mode of operation for semantic anchors. It also inherits its value from the parent configuration, with a default setting of "timestamped_video". This mode is suitable for projects that require precise temporal alignment of semantic data with video content. Modifying this parameter can affect how semantic information is processed and integrated into your project.

operation_json

This required parameter contains the JSON configuration for the operations to be performed on the project assets. It is crucial for defining the specific actions and transformations that need to be applied to the assets during the workflow. Proper configuration of this parameter ensures that the node executes the desired operations accurately.

tagged_references

An optional parameter that allows you to include additional tagged references in your project. These references can provide supplementary information or metadata that enhances the context and understanding of the project assets. Including tagged references can improve the richness and depth of your project's semantic data.

ownership_json

This optional parameter holds the JSON data related to the ownership and rights management of the project assets. It is particularly useful for projects that require strict control over asset usage and distribution. Properly configuring this parameter ensures compliance with ownership and licensing requirements.

upscale_model

The upscale_model parameter is an optional input that specifies the model to be used for upscaling project assets. It is marked as "lazy", meaning it is only loaded and utilized when necessary, optimizing resource usage. Selecting an appropriate upscale model can enhance the quality and resolution of your project assets.

project_assets

This output provides a compact catalog of the project assets, facilitating synchronization with Plan or Plan Studio. It is essential for maintaining a coherent and organized collection of assets throughout the project lifecycle.

references

The references output includes native tagged references along with separate semantic-anchor metadata. This information is crucial for understanding the relationships and context of the project assets, enabling more informed decision-making during the creative process.

reference_fingerprint

This output generates an order-neutral incremental reference lineage, ensuring compatibility with Plan. It serves as a unique identifier for the project's references, allowing for efficient tracking and management of asset versions and changes.

source_timeline

The source_timeline output provides an optional path-backed Source Timeline for specialized direct uses. While Plan automatically absorbs this through project_assets, having a separate timeline can be beneficial for projects that require detailed temporal analysis and manipulation of media content.

status

This output conveys the run name, enabled reference count, source-track state, and revision information. It provides a comprehensive overview of the current state of the project, aiding in monitoring progress and identifying potential issues.

  • Ensure that the run_name is descriptive and unique to avoid confusion when managing multiple project iterations.
  • Utilize the semantic_anchor_mode to align semantic data with your project's specific requirements, especially when working with video content.
  • Regularly update the operation_json to reflect any changes in the project's workflow or asset processing needs.

Invalid H3 project asset descriptor.

  • Explanation: This error occurs when the asset descriptor provided does not match the expected format or type for the specified media kind.
  • Solution: Verify that the asset descriptor is correctly formatted and corresponds to the correct media type (e.g., image, audio). Ensure that all required fields are present and correctly specified.

H3 project picture references require Pillow, NumPy, and torch.

  • Explanation: This error indicates that the necessary libraries for processing image references are not installed or accessible.
  • Solution: Install the required libraries by running pip install Pillow numpy torch in your environment. Ensure that these libraries are correctly imported and available for use in your project.

MiniMax H3 Project Asset Carousel (Tree) Related Nodes

Go back to the extension to check out more related nodes.
MiniMax H3 Context Loop
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.

MiniMax H3 Project Asset Carousel (Tree)