← RVLS/OS

CHORUS

how the tracks on this site were made: a seeded breakbeat engine that renders offline, checked with a measuring tool as well as my ears, and why the sound goes against the visuals on purpose.

python · dsp · mastering · earshot · web-audio

the site track as a spectrogram, waveform and beat map
safety saver as it ships: partials, kicks and bars from its own beat map.

the pinned render (mp3)

the music here is rendered ahead of time, nothing is generated live. an engine i wrote in python cuts my own loops, breaks and stems into tracks, and the same seed always gives the same track. the player only plays files and never starts on its own.

i tuned the engine by measuring as well as listening. the first versions had holes in the breaks and loops sitting at different levels, and earshot (an open-source tool that gives an ai ears: it listens and tells you what it hears, with the numbers) caught both. the fixes turned into engine flags: summed stems for the breaks, level-matched loops, a choke on the 808, and an ethereal intro built from my own melodic loops. by version three the intros read as breakcore and jungle instead of “warm analog synth pad”. version four puts real breakcore edits over that ambience, and earshot now files it under drum and bass.

under the breaks there’s still the slow ambient bed from the earlier version, so it doesn’t wear you out in a minute.

what you get is the tape player and these notes. the engine, its flags and the before and after measurements for each track stay with me.