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 > MiniMaxH3-Studio > H3 Feasible AV Timeline

ComfyUI Node: H3 Feasible AV Timeline

Class Name

comfyui_h3_context.H3Context.FeasibleAVTimeline

Category
h3_context/planning
Author
rookiestar28 (Account age: 1077days)
Extension
MiniMaxH3-Studio
Latest Updated
2026-11-05
Github Stars
0.16K

How to Install MiniMaxH3-Studio

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

Builds a deterministic audiovisual timeline, validating timing and constraints before execution.

H3 Feasible AV Timeline:

The H3 Feasible AV Timeline node builds a deterministic audiovisual timing plan: a structured schedule for how audio and visual material should fit together before later processing or reconstruction. Its purpose is to establish a contiguous timeline that accounts for the selected operating mode, rather than simply arranging material without checking whether the arrangement is feasible. The underlying planning system considers timing information such as effective duration and frame alignment alongside registered references and planning constraints. For you, this provides a consistency checkpoint between creative planning and downstream execution, helping identify incompatible requirements before they propagate further through the workflow. The node performs planning rather than rendering finished audio or video, and it fails closed when the validation or value errors handled by its implementation occur, stopping instead of presenting an invalid timeline as usable.

H3 Feasible AV Timeline Input Parameters:

request

Required connection of type H3_CONTEXT_REQUEST, represented internally as a RawContextRequest. This supplies the current context request to the timeline-building stage, establishing the request context under which planning takes place. It is passed together with the references, intent information, and directive information, so you should use the request associated with those other connected values rather than one from an unrelated workflow branch. The supplied node code does not expose the request’s individual fields or show exactly how each field affects timing, so this socket should be treated as a structured upstream connection rather than a text entry or duration control. Minimum, maximum, default, and selectable options are not specified; the connection is required.

reference_registry

Required connection of type H3_REFERENCE_REGISTRY, represented internally as a ReferenceRegistry. This supplies the collection of reference assets available to the planning process. The provided planner code reads asset identifiers and asset roles from a reference registry, allowing planning to distinguish registered assets and their assigned roles instead of relying only on informal descriptions. Its effect depends on the references used by the rest of your planning data: the registry should correspond to the assets associated with the current request and intent. This socket does not upload media or expose individual asset settings in this node. Minimum, maximum, default, and selectable options are not specified; you must connect an appropriate registry from upstream.

intent_graph

Required connection of type H3_INTENT_GRAPH, represented internally as an IntentGraph. This carries the structured intent that the timeline-building stage receives alongside the request and reference registry. In the supplied context, an intent graph’s effective duration is used when constructing a feasible timeline request, illustrating how creative intent can supply timing requirements for planning. The node itself does not expose controls for editing the graph, changing its duration, or adjusting individual segments; those changes belong upstream. Use the graph for the same request and references you are planning so that the stage can evaluate a coherent set of values. Minimum, maximum, default, and selectable options are not specified; the connection is required.

intent_report

Required connection of type H3_DOWNSTREAM_PRODUCER_REPORT, represented internally as a DownstreamProducerReport. This supplies the report associated with the intent-producing stage and is passed to timeline construction together with the intent graph. Its role is to provide the accompanying producer report, not to replace the graph itself. Because the provided code does not show which report fields are inspected, it does not establish specific required status values or report options. Connect the report belonging to the current intent graph rather than assuming that any report with the same socket type is interchangeable. Minimum, maximum, default, and selectable options are not specified; the connection is required.

directive_authority

Required connection of type H3_DIRECTIVE_AUTHORITY, represented internally as a DirectiveAuthorityBundle. This supplies the directive-authority information used by the reconstruction timeline-building stage alongside the creative intent and request context. It provides the planning stage with the structured authority bundle produced upstream; the supplied class does not expose its contents or define a local priority selector, override switch, or editable instruction field. To keep the planning context consistent, connect the bundle associated with the directives for your current request. Its precise effect on individual timeline decisions depends on implementation details not included in the supplied excerpts. Minimum, maximum, default, and selectable options are not specified; the connection is required.

directive_report

Required connection of type H3_DOWNSTREAM_PRODUCER_REPORT, represented internally as a DownstreamProducerReport. This supplies the producer report associated with the directive information and is passed alongside the directive-authority bundle to timeline construction. Although it uses the same socket type as intent_report, it occupies a different argument position and should carry the report from the corresponding directive-producing stage. Keeping these reports correctly paired helps avoid passing unrelated planning context into the stage. The supplied source does not reveal report-specific acceptance rules or editable report settings. Minimum, maximum, default, and selectable options are not specified; the connection is required.

H3 Feasible AV Timeline Output Parameters:

feasible_timeline

Output of type H3_FEASIBLE_AV_TIMELINE, represented internally as a ReconstructionTimelineStage. This is the structured result returned by the reconstruction timeline-building stage for use by compatible downstream nodes. Interpret it as planning data for audiovisual timing, not as rendered video, audio samples, or a plain-text timeline. The underlying feasible-timeline planner is designed to construct a contiguous, mode-aware plan and can produce status information, diagnostics, and limitations, but the supplied node implementation does not show how those details are stored or exposed within this output object. Consequently, do not assume that this socket directly returns the lower-level planner result or a separate diagnostic list. When a handled validation, type, or value error occurs, the node raises a pipeline error instead of returning this output normally.

H3 Feasible AV Timeline Usage Tips:

  • Connect all six required inputs before execution. This node has no optional inputs or local widgets, so you cannot substitute a manually entered value for a missing structured planning connection.
  • Keep the request, references, intent graph, and directive information from the same planning context. If you change the request or reference assets, regenerate the affected upstream planning values and their reports before rebuilding the timeline.
  • Pair intent_report with the intent-producing stage and directive_report with the directive-producing stage. Their identical socket types do not identify which report belongs in which position.
  • Adjust timing requirements upstream rather than looking for duration or frame-rate controls here. The underlying planner uses effective duration and a frame grid, but neither is exposed as an independent parameter on this node.
  • Use the node as a planning checkpoint before downstream reconstruction or rendering. A timeline plan organizes feasible timing; it does not itself generate finished media or establish the artistic quality of a final result.
  • When troubleshooting, inspect the chained exception or execution log as well as the visible error. The node deliberately presents a general failure message for several underlying error categories, so the original cause is often more useful than the summary alone.

H3 Feasible AV Timeline Common Errors and Solutions:

feasible_timeline_failed: feasible timeline planning failed closed

  • Explanation: The source defines the error code feasible_timeline_failed and message feasible timeline planning failed closed. This is raised when timeline construction encounters a ContractValidationError, TypeError, or ValueError. “Failed closed” means the stage stops rather than returning a potentially invalid timeline; the exact display formatting depends on the pipeline’s error formatter.
  • Solution: Inspect the original exception in the execution log, then check all six upstream connections. Confirm that the request, registry, intent graph, authority bundle, and reports belong together, and regenerate any upstream values affected by recent changes.

ContractValidationError — underlying validation failure

  • Explanation: This is an exception category explicitly handled by the node, not a separate guaranteed on-screen message. It indicates that timeline construction rejected a contract requirement. The supplied excerpts do not enumerate the individual validation rules or their diagnostic messages.
  • Solution: Follow the detailed validation message in the original exception. Check the relevant upstream producer and its report, correct the reported inconsistency, and rerun the dependent stages before attempting timeline planning again.

TypeError — underlying data-type failure

  • Explanation: The node catches this exception when timeline construction encounters an incompatible kind of value. The expected inputs are structured H3 objects, not ordinary text, numbers, images, or manually assembled substitutes. The exact type-error message is not provided in the source excerpt.
  • Solution: Connect each socket to a producer with the matching declared H3 type. If the workflow uses custom integrations or modified nodes, verify that they return the expected object classes rather than merely declaring a compatible socket label.

ValueError — underlying invalid-value failure

  • Explanation: The node also catches invalid-value errors raised during timeline construction. A value can have the expected general type yet still be unsuitable for the operation being performed. The supplied code does not identify the specific values or timing combinations that trigger this exception.
  • Solution: Read the chained error for the rejected value or condition, then correct it in the upstream stage that produced it. If the detail concerns timing or references, review the relevant duration, frame-alignment configuration, or registered assets there; this node has no local controls for repairing those values.

H3 Feasible AV Timeline Related Nodes

Go back to the extension to check out more related nodes.
MiniMaxH3-Studio
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 Feasible AV Timeline