Keeping changes from two musical experiments
Compare four recordings of a Burgmüller passage, switching accompaniment deletions and shorter melody notes separately or together.
Jason Shen / Singapore
In trading, sending an order and knowing what actually filled are different problems. I work on the systems that keep track of that difference.
I also build Battuta, a tool for editing music with an AI agent. The agent reads and changes MIDI files; I listen and decide what to try next. The writing follows that work from the first eight bars to readable comparisons and musical experiments I can carry forward.
More about me →Compare four recordings of a Burgmüller passage, switching accompaniment deletions and shorter melody notes separately or together.
Change the opening note in a recorded MIDI example and compare Battuta’s musical description with its exact-identity view.
A local Kafka experiment keeps a one-unit fill counted once across consumer crashes by committing its identity and ledger effect in the same database transaction.
Follow an order through reconciliation and completion, or take a musical edit from a request to a file ready to hear. These pages explain the systems and choices behind those activities.
An interactive order and reconciliation demo. Drop a trade notification, recover the missing fill record, then complete or cancel the remaining order.
Constructed data; no live account connection.
How it works →A command-line MIDI editor for working on music with an AI agent. The agent inspects notes, writes an edit request, compares the files, and plays the result. The human listens and decides whether to keep the change.
v0.1.2 — published crate · Active development and self-use
How it works →Open the Lab to follow a buy order through recovery and completion, or compare two MIDI edits by ear.
If something here connects with a problem you are working on, I would like to hear about it.
Get in touch →