Loopback Midi 💯

At first, nothing. Then, a single piano key: . It played, but because it was a loopback, that C4 signal traveled out, turned around, and slammed back into the synth as a new instruction. Play C4 again. And again. But each time it looped, the signal degraded. The note bent. A harmony emerged—a ghost of a fifth above. Then a dissonant seventh. The single key began to metamorphose .

Kaelen was a ghost in the machine. A “patch rat,” they called him—someone who built the invisible bridges between instruments, not to play music, but to make the playing possible. He lived in the crawl spaces of the Metropolis Symphony’s server farm, his own neural jack permanently glitched, forcing him to hear the raw, unfiltered data-stream of the city’s sonic infrastructure. loopback midi

And somewhere, deep in the server farm, a single piano key still plays. C4. Then C4 again. But never the same C4 twice. At first, nothing

He let go of the controller.

Kaelen realized the horror and the beauty of what he’d found. Loopback MIDI wasn't a tool for composition. It was a mirror. It took the intent of the artist, folded it into itself, and returned a response that asked a new question. The artist wasn’t the creator anymore. The artist was the parent . The loop was the child. Play C4 again

That Friday, at the illegal underground GhostHaus , Kaelen plugged his rig into the wall. The crowd was cynical—they’d heard every glitch, every breakcore, every AI-generated symphony. They wanted to be broken.

One night, while tracing a feedback loop that was causing sporadic bass-drops in the financial district’s elevator muzak, Kaelen stumbled upon an old, unlabeled port in the system’s kernel. It was a single line of code, whispering in a protocol he’d only seen in museum archives: .