Repository navigation
v1.3.0
Experimental: two-time conditioning on pruned bases (curve refit)
Pruned/curve MiniMax-H3 bases have no time_embedder, so HyperFlow's two-time (t, r) conditioning physically couldn't apply — pruned users were stuck with backbone-only LoRA, single-time, off-recipe. This release adds an experimental curve refit that restores most of that signal:
- A tiny ~34 KB checkpoint-bound fit (bundled for the FL2VA and REF2VA pruned int8 checkpoints) replaces the missing time-conditioning pathway. No extra model weights, no download.
- Fits are hash-bound to the exact base + adapter + recipe (strength 1, default gate/sigmas). Any mismatch falls back to backbone-only with a console warning — it never silently does the wrong thing.
- Preserves the v1.2.5 first-step audio endpoint fix: separate fitted rows for video and audio even where both share
t = 0.
Measured against the full base (fixed prompt/seed/latents, 768x768, 124 frames, Euler):
| Stream | Backbone-only | + curve refit |
|---|---|---|
| FL2VA video (cosine) | 0.81 | 0.88 |
| FL2VA audio | 0.98 | 0.98 |
| REF2VA video | 0.87 | 0.89 |
| REF2VA audio | 0.93 | 0.997 |
How to enable: set experimental_curve_refit = True on the Apply node (show optional widgets), keep strength = 1.0, no gate/sigma overrides. Recommended: bypass mode + Euler + the node's SIGMAS output. Details and pruned-base settings: README → Pruned / curve bases.
Honest caveats: recovers most — not all — of the missing conditioning (pruning removed both learned time-embedder LoRAs; some residual is irreducible without training). Single prompt/seed validation so far; the full base remains the reference. New pruned checkpoints need their own fit (validation/curve_spike.py). Full analysis: validation/curve_findings.md.
Also in this release
- README troubleshooting: "Stuck at Model Initializing" after a ComfyUI update (
--disable-fast-diskdiagnostic). - 88 tests pass; the full-base path is bit-exact vs v1.2.5 (verified across all 8 steps incl. collision/mask rows).
Update: pull latest and restart ComfyUI. The toggle is off by default — full-base users are unaffected.