murRipple, closed out — a song woven into visible ripples
The project is done. It leaves two documents behind, one for readers who want to understand it and one for people who want to use it.
What murRipple does fits in one sentence. Give it an mp3 and a lyrics file and it hands back a zero-dependency single-file web page and a video with the same content: the song is separated into voices, and each voice sends its own ripples across the screen. The project is now finished, and this is its close-out record.
Finished does not mean shelved. It has a pipeline that runs end to end, a gate that turns “what you see in the browser is what comes out in the video” into a check that runs itself, and a stated boundary of what it cannot do. All of that went into two documents, both written in Chinese.
Two documents, two kinds of reader
The technical teardown is for anyone who wants to know how it was built: how the architecture is layered, why the render is a deterministic function of time, how the checks were raised one by one, and the pitfalls hit along the way — each listed together with its fix.
The product introduction is for anyone who wants to use it, and answers exactly four questions: what it turns into what, what you can do with it, where to start, and what it cannot do. The fourth question gets a full section of its own, not a footnote.
Neither document requires reading the other first. Both are in Chinese; no translation exists yet.
Three ways in
- Product page: murripple.miao-yu.com
- Public repository: github.com/ymustc/murRipple-public
- Live demo: ymustc.github.io/murripple-demo
The documents keep to my standing rule: no number without a source. What it is and how far it got is stated in things you can open and recount yourself.