Refresh daily workflow review notes

This commit is contained in:
Morpheus
2026-08-20 20:07:50 +00:00
parent a84c26a5f5
commit 69f3c0f9c3
7 changed files with 67 additions and 1 deletions
+8
View File
@@ -12,17 +12,23 @@
- `models/minimax/minimax-h3-turbo-lora-community/`
- `models/minimax/minimax-h3-int8-r2v-community/`
- `models/minimax/minimax-h3-extender-ref2va/`
- `models/minimax/minimax-h3-int8-r2v-javano2608-23/`
- `models/minimax/minimax-h3-turbo-gguf-i2va/`
- `models/minimax/minimax-h3-seamless-chain-v2/`
## Strong current heuristics
- Prefer Turbo LoRA for the first `text-to-video` attempt.
- Prefer INT8-based community workflows for `reference-to-video` exploration.
- Keep attention and memory-efficiency helpers if they are already integrated and well documented.
- Treat the same-day `javawock7618` `INT8 R2V` import as the strongest current donor for local continuity and identity retention, but not as proof that the graph is light enough for a `3070`.
- Keep the GGUF `I2VA` path as an audio-aware fallback, not the default lane.
## Current weak areas
- No proof yet that MiniMax is truly practical on Chris's box.
- Custom-node stack is more fragile than the current `flux2klein` path.
- The full `seamless-chain` graph is interesting, but it is not a clean baseline for the first maintained master.
## Best current optimization direction
@@ -30,6 +36,7 @@
- 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.
- 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
@@ -44,3 +51,4 @@
- whether the Turbo LoRA workflow is just technically possible or actually usable
- whether the source-recommended `8`-step path holds up in quality
- whether MiniMax feels like a real challenger to `LTX` locally
- whether the same-day `INT8 R2V` donor stays practical on the `3070` once the helper stack is trimmed to the minimum