Sonic Weaver

About the Sonic Weaver thread

Turning a track into video is a rendering problem wearing a music-theory costume. This cluster covers both halves: how audio is analysed in the browser with the Web Audio API and FFT, and how that analysis is turned into motion across the 29 engines in Sonic Weaver (Particles, Trails, Bloom, Character Motion, Radial, Spectrum, Bars, Tunnel, Waveform, Logo, Lattice, Terrain, Stage Lights, Harmonic Constellation, Chladni Resonance Plate, Voronoi Stained Glass, Procedural Night City, Spectral Topography, Fluid Ink Feedback, Arrangement Tunnel, Cover-Art Relief, Kinetic Lyric Typescape, Stereo Phase Garden, Horizon Scenes, Disco, Liquid, Portal, Now Playing, and Sketchbook), each carrying 6 or 7 modes, for 180 in total.

The recurring theme is that beat sync is not one thing. Locking every element to the same kick drum produces something that pulses uniformly and reads as cheap. The articles on multi-band sync work through splitting bass, mid, and treble onto different layers so a visualizer responds to the actual arrangement, which is the single change that most reliably separates an amateur result from a releasable one.

Export is treated as a first-class topic rather than a footnote. Rendering happens locally via WebCodecs, which means no queue and no upload, but it also means the constraints are your device's, and knowing where they bite is the difference between a finished video and a stalled tab.