A visualizer catalogue only works if engines still look like themselves when the track is silent. Here is how distinct draw identities survive muted preview, reduced motion, and still capture.
A short walkthrough of why muted and reduced-motion frames are part of the engine ship gate.
Audio reactivity is the promise. Identity is the product. If every engine collapses into the same soft glow the moment the track is muted, the gallery becomes a wallpaper picker instead of a catalogue. The September expansion work treated muted and reduced-motion frames as first-class proofs that each engine still reads as itself.
Muted preview is how authors, reviewers, and accessibility users inspect structure without a beat driving every pixel. It is also how still captures and poster frames are judged. An engine that only looks correct while audio is pumping is not finished. The draw path must keep silhouette, palette family, and motion grammar readable at rest.
That does not mean the scene should ignore audio when audio exists. It means the resting pose is designed, not an accident of zero amplitude. Bars still imply a spectrum layout. Stage lights still imply fixtures. Particle fields still imply depth. The energy scale can drop without erasing the machine.
The track is playing
Each band has its own level, so bass, mids and highs can drive different elements.
Distinct is not a marketing adjective. It is whether a reviewer can name the engine from a muted still with the label covered. Failures look like shared default gradients, identical centre orbs, or motion kits that all settle into the same breathing circle. When two engines share a kit, their modes still need different geometry, density, and framing so the catalogue row is not a lie.
Shared shaders are fine. Shared resting poses are not. If two modes only differ by a hue rotate while muted, they are one product with two nameplates. Rename them, merge them, or give each mode its own geometry budget before the gallery ships the row.
Open the editor, mute audio, and capture a still. Compare it against the neighbouring catalogue row. If you need the label to tell them apart, rewrite the draw defaults before you write the blog post. Then enable reduced motion and confirm the scene settles on a readable frame rather than a half-rotated prop.
Repeat with a quiet track and a loud track. Quiet should scale energy down without changing identity. Loud should intensify the same grammar rather than switching to a different product. If loud mode invents a new silhouette, you shipped two engines under one name.
Blind still test
Cover the titles on three neighbouring cards. Name each engine from the muted still alone. Wrong answers are engine bugs wearing marketing clothes.
Gallery cards, OG stills, and export posters often show muted or low-energy frames. Those frames are public claims about the engine. Treat them as part of the ship gate. A beautiful reactive clip with a muddy poster is a failed package.
Export settings should not silently restyle the identity to chase encoder friendliness. Adaptive quality may reduce particles or effect cost, which is the subject of the companion article, but it should not replace one engine with another look.
When you document a mode, include one muted still and one reactive clip. The still proves identity. The clip proves reactivity. Publishing only the clip hides the harder requirement.
Some modes are intentionally sparse at rest. Sparse is allowed when sparse is the identity. Blank is not. If a mode needs audio to draw anything at all, say so on the mode card rather than showing an empty stage as if it were intentional design.
This post does not claim every historical mode already passes a blind still test. It claims the expansion standard: new and revised engines must remain distinct when muted, and reviewers should reject rows that fail.
Beat smoothing and mode-specific editor controls exist to protect composition, not to paper over a missing idle pose. If smoothing is the only thing keeping two modes apart, the modes are unfinished.
Pick three engines you use most. Mute them. Save stills. If any pair could swap labels unnoticed, file that as a product defect against identity, not as a content preference. Then read Adaptive quality when the device gets hot for how performance governance should lower cost without erasing those silhouettes.
Field check for maintainers: open the gallery, cover the titles with your hand, and name each card. Schedule the same check after any shared kit change. Kit refactors are the most common way distinct engines quietly become twins.
Reviewed by the editorial team. Report a correction.
Anonymous. Only this page’s address and your yes/no are recorded, and only if you allowed analytics cookies.
Ready to make your own?
Open the editor, drop in a track, and export a watermark-free video: free, no account.
Open the Editor