chris.dumas/comfyui-workflows
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tighten optimized workflow masters

Browse Source
This commit is contained in:
Morpheus
2026-08-22 15:24:04 +00:00
parent 2e940d7e71
commit 6bcfd3904f
23 changed files with 89 additions and 13712 deletions
Download Patch File Download Diff File Expand all files Collapse all files
optimized/notes/ltx.md
+1 -1
View File
@@ -28,7 +28,7 @@
## Best current optimization direction
- Keep `optimized/image-to-video/ltx23-3070-simple-master/` as the first `LTX` default.
- Keep `LTX` in `models/ltx/` and notes until it earns a real maintained optimized slot again.
- Only promote first-last-frame or character-sheet variants after the simple master proves viable.
- Use the `LTX-2.5` multi-subject reference workflow as a future donor for reference-heavy jobs, not as the baseline.
optimized/notes/minimax.md
+10 -2
View File
@@ -34,19 +34,27 @@
- Keep `optimized/text-to-video/minimax-h3-3070-turbo-master/` as the first MiniMax default.
- Keep the INT8 reference-video workflow as the next donor for future low-VRAM optimization.
- Keep `optimized/image-to-video/minimax-h3-extender-3070-r2v-480p-clip-by-clip/` as the first `MiniMax H3 Extender` path to compare against the compact `Contex Loop` masters.
- Use `optimized/image-to-video/minimax-h3-best-current-r2v-master-480p-3x10s/` as the best-current default whenever Chris wants a `MiniMax H3` `reference-to-video` continuation workflow.
- Keep only two maintained `optimized/image-to-video/` MiniMax lanes:
- `optimized/image-to-video/minimax-h3-best-current-r2v-master-480p-3x10s/` as the reference-first generation master
- `optimized/image-to-video/minimax-h3-contex-loop-3070-safe-60s-awq-int8/` as the imported-video extension master
- Use the new same-day `javawock7618` `INT8 R2V` import as the main donor for future `best-current-r2v` revisions if the current master needs another pass.
## Ref2VA prompt guidance
- For `MiniMax H3 Ref2VA`, treat `480p` and `10s` as the safe planning baseline on `8GB VRAM` unless direct tests prove otherwise.
- Chris's later manual testing suggests `20s @ 480p` is a real context-loop candidate ceiling, so maintained loop masters should compare `3 x 20s` against `6 x 10s` rather than assuming only `10s` clips are viable.
- In the maintained `best-current-r2v-master`, keep `Picture 1` as the master scene / environment reference and `Picture 2` as the primary full-body identity reference.
- Use one master-scene reference to control environment/composition, one primary full-body reference per subject to control overall appearance, and headshots only to reinforce facial identity.
- Explicitly state when multiple images represent the same subject, and explicitly tell the model to ignore character-reference backgrounds so they do not fight the master environment.
- Use the prompt mainly for action, performance, camera movement, dialogue, and audio rather than re-describing scene details already visible in the references.
- Full guidance now lives in `optimized/notes/minimax-h3-ref2va-prompt-guidelines.md`.
## Loop enhancement direction
- For the target maintained `Contex Loop` quality workflow, treat the second-pass enhancement lane as mandatory, not optional.
- That second pass should reuse the conditioning from the original `MiniMaxH3ReferenceToVideo` node that gathers the reference images, and feed that original reference conditioning back into the guider for the enhancement pass instead of relying only on first-pass latent continuity.
- Current preferred sampler/scheduler direction for that enhancement pass is `Euler` plus `beta`.
## What needs Monday proof
- whether the Turbo LoRA workflow is just technically possible or actually usable