Coding Beats
A public study of rhythm written as code: patterns, motion, and measured sound.
I want to study beats that are written as code.
Tools like Strudel make rhythm visible. A beat is not only an audio file. It is tempo, samples, rests, repetition, probability, filters, space, and timing written into a system.
That matters because coded music can be inspected. Change one line and the beat changes. Save the pattern and the idea becomes repeatable. Compare two versions and you can hear what moved.
That is the research question: what happens when a beat is treated like software and sound at the same time?
The study is simple. Build small coded sketches. Document the pattern. Listen to the result. Measure the audio. Map the signal to movement or visuals.
It is also a memory system. I can come back later and see the beat as code: the tempo, the rests, the drum choices, the filter shape, the space, and the pulse.
Someone else can open the same sketch in Strudel, press play, and change it. That is different from posting an audio clip.
The beat is not only something to hear. It is something to inspect.
This is not a claim that AI understands music. It is a public study of how coded rhythm becomes measurable sound and movement.
MaloSound is the public music lane for XIV. This note is the coded rhythm lane.
The first sketch is a slow coded beat in Strudel: readable, playable, and changeable.
The beat is not only something to hear. It is something to inspect.