By scragnog

The standard way to run a listening test in HOT-Step - a local HTML score sheet next to the renders where Rob plays each track, scores it 1-5 on named criteria, and the page charts the two score…

scragnog/HOT-Step-CPP

Explains where HOT-Step generation time goes (LM/DiT/VAE), how the TensorRT paths activate, how to benchmark from logs, and which knobs trade quality for speed.

scragnog/HOT-Step-CPP

Maps HOT-Step's native MiniMax-Music3 backend — engine port modules, endpoints, server/UI integration, parity/fixture infrastructure, and the hard-won trap list.

scragnog/HOT-Step-CPP

The validated recipe for training MiniMax-Music3 planner-LM style adapters (artist/album clones) with ace-train mm3-lm-train and the Training Studio.

scragnog/HOT-Step-CPP

Runbook for cutting and publishing a HOT-Step CPP release via a v git tag that triggers the multi-platform CI build and drafts a GitHub Release.

scragnog/HOT-Step-CPP

Safely pulls upstream acestep.cpp changes into the HOT-Step engine fork without destroying its integration hooks.

scragnog/HOT-Step-CPP

Diagnoses HOT-Step CPP generation failures, engine crashes, hangs, and startup problems from the logs/ session folders.

scragnog/HOT-Step-CPP

Safe edit-rebuild-test cycle for the HOT-Step C++ engine (dev-rebuild.bat, build script selection, stale-.obj recovery, smoke tests).

scragnog/HOT-Step-CPP

Traces the full life of a music generation request (UI form → Node job queue → engine LM → synth → SQLite song row) and every place params can silently drop, especially the LM echo sideband gotcha.

scragnog/HOT-Step-CPP

Explains how to write, test, and debug HOT-Step Lua plugins (solvers, schedulers, guidance modes, postprocess) including the apg()/poststep() API and UI param flow.

scragnog/HOT-Step-CPP

Explains MiniMax-Music3's Structured Caption format (Global Metadata / Vocal Details / Arrangement) and the vendored upstream music-caption-rewriter reference library.

scragnog/HOT-Step-CPP

Explains how model files, checkpoints, GGUF quantization, and the Model Manager work in HOT-Step CPP.

scragnog/HOT-Step-CPP

Maps every HOT-Step CPP feature to its route file, service, UI folder, and engine subsystem, including port topology and the browser-to-engine request path.

scragnog/HOT-Step-CPP

Guides adding or modifying a feature in the HOT-Step CPP Node/TypeScript server (Express route + service pattern, better-sqlite3 schema changes, engine calls via aceClient, logging, tsx watch dev…

scragnog/HOT-Step-CPP

Guides adding or modifying UI features (React "studios") in HOT-Step CPP — studio-folder convention, store patterns, API wiring, routing registration, Tailwind/i18n rules, and the Vite HMR dev loop.

scragnog/HOT-Step-CPP

Defines the verification bar every HOT-Step CPP change must clear before being called done — per-tier checks (TypeScript, C++ engine, UI, audio, end-to-end smoke generation) and honest result…

scragnog/HOT-Step-CPP

Explains how HOT-Step's LoRA/LoKr adapter system loads, merges, caches, stacks, and regionally masks adapters at runtime, including hard-won failure modes.

scragnog/HOT-Step-CPP

How HOT-Step's custom flash-attention training ops (GGMLOPFLASHATTNTRAIN/BACK) work, what the AS1.5 DiT trainer campaign proved and disproved, and the exact contract for porting flash mode to the…

scragnog/HOT-Step-CPP