Skip to content

H3 Editor 0.9.0

Choose a tag to compare

@igorls igorls released this 15 Nov 10:53
· 47 commits to main since this release

H3 Editor 0.9.0 lets a project render with speed-up nodes from your other packs: sparse attention, low-memory attention, a step cache, a compile node. It also closes two gaps in how project zips are opened.

H3 Editor 0.9.0

Highlights

  • Model patches. Any installed node that takes the model and returns it can go on every render of a project.
  • The settings are the node's own. The editor reads them from the node's definition, so a pack released tomorrow works without a change to the editor.
  • Project zips open more carefully. A zip made by hand can no longer bring a revision history, and its patches open switched off.

Model patches

Other packs ship nodes that change how the model runs without being a model: sparse or low-memory attention, a cache that skips steps, a compile node. In a workflow you put one between the loader and the sampler. The Model patches section of the Project tab does the same for every render of a project.

In the section What it does
Add a patch Lists the installed nodes that take one model and plain values and return one model. The ones for H3, MiniMax or attention come first; type to search by name, pack or category.
The settings in a patch's row The node's own: numbers with their range, switches, menus and text. The button under the name shows what you changed from the defaults, and Reset goes back to them.
The tick box Renders without the patch and keeps it in the list.
The arrows Move a patch up or down. Patches go on the model in the order listed.
The bin Removes the patch.

How they are applied:

  • Patches sit after the LoRAs, on drafts and on both passes of a final.
  • They are set for the project, up to 8. A clip cannot have its own.
  • A take records the patches it was made with.
  • A patch whose pack is not installed shows Not installed and is left out of renders, so the project still opens and renders on a machine without that pack.
  • A project opened from a zip has its patches unticked until you tick them: whoever made the zip chose the nodes and their settings.

Does a patch help?

The editor cannot know. Some patches speed a render up at a cost to the picture, some only save memory, and some do not work with every checkpoint. Render the same clip with the same seed with the patch and without, compare the times, and look at both. For clips that join, h3.py cuts scores the cuts of each version.

One was measured for this release, Veda Sparse Attention at 90% sparsity, on MiniMax H3 Turbo at 6 steps with the same seeds:

Render Without With
Draft, 640×352, 3.8 seconds 22 to 24 s 51 to 58 s 2.3 times slower
Final, 3.8 seconds 226 and 235 s 186 and 173 s 1.3 times faster
Final of a bridge, 8 seconds 661 s 288 s 2.3 times faster

The bridge is one run each way. Its two cuts scored the same with the patch and without: 98 of 100 for the picture at both, and 94 against 95 for the sound into the next clip.

The time is not the whole answer. All three 3.8 second finals made with the patch have a small jump 5 frames before their end, at the last step of the picture latent. The finals made without it and the drafts do not. The editor's Checks list it as a change of picture inside the take, and h3.py cuts reports it under inside.

What that says about patches in general:

  • Compare at the size you mean to use. A patch with a fixed cost at every step loses on a short draft and wins on a long final. Untick it for drafts.
  • Read the checks of a take made with a patch, and look at its end. A faster render can differ in a few frames only.
  • A patch may want a certain checkpoint. That node accepts plain MiniMax H3 checkpoints and refuses HyperFlow H3 Flash, the editor's default model. When a render is refused, the message names the patch.

Project zips

Fixed What happened
A zip can no longer bring a revision history A zip made by hand could carry files that landed in the new project's history, its previews or its project file, and restoring such a revision brought back whatever it held. Opening a zip now passes over everything that Download as zip never packs, and the project starts with one revision.
Paths that Windows reads as another file are refused A name with a colon, a control character, one of < > " | ? *, or a device name such as NUL. The editor writes no such names.

Zips made by the editor open as before.

For agents

What Where
patches in set_project [{"node": id, "inputs": {name: value}, "on": true}]. Replaces the whole list; inputs names only what differs from the node's defaults; [] clears it.
patches in GET /projects Every installed node a project can use, with its title, pack, category and controls: each input's name, kind, default, range or options, and the node's own tooltip.
patches_off in the reply to POST /projects/open The patches a zip had on, opened switched off. Tell the user which they are, and switch one on only when asked.
Limits A patch takes up to 64 inputs and text of up to 4000 characters. A render is refused, with the input's name, when a value is outside what the node accepts.

Updating

Update the pack and restart ComfyUI. Projects made with 0.8 need no change, and nothing renders differently until you add a patch.