Piano Simulator 1000

Alpha 1 — QA Candidate 1

build alpha-1-qa-rc1+2419770 · 2026-09-23

This is a QA candidate, not a release. It is here so a few people can break it before anything is called "Alpha build 1". Everything below was produced automatically from a recording and published unedited — the mistakes are the point.

Open a song, press play, and the notation and keyboard follow the recording. Tap a bar to jump there; loop a few bars and slow them down. Nothing to install, nothing to sign in to, and nothing you do here is sent anywhere.

The songs

NieR:Automata — Soundtrack Medley

Piano arrangement by Animenz · music by Keiichi Okabe, Keigo Hoashi and Kuniyuki Takahashi

15:45
Open NieR:Automata — Soundtrack Medley
Silo Season 2 Episode 4 Outro Song

Music by Loney Dear

0:55
Open Silo Season 2 Episode 4 Outro Song

What to test

Does it sound like the song? Play the recording, then the generated piano. Notes that are missing, invented or in the wrong octave are the most useful thing you can find.
Can you read it? Look at the notation while it plays. Is the music on a staff that makes sense, and can you follow a line with your eye?
Can you practise from it? Loop a few bars, slow them to 50%, switch to one hand. Does the loop land where you asked, and stay there?
Does it break? Seek around, change speed mid-phrase, switch between the recording and the piano, turn your phone sideways, reload the page.

For the musician reviewers

These links open on the passage and loop it. The question is not whether the notes are right — it is whether a person could read and play what is on the page.

NieR — bars 83–90 The passage PD-3 was built for: the left hand used to be stranded on a bass staff it had left. This is where the staff distribution should be visibly better.
NieR — bars 93–119 What happens around that change. A repair that fixes one passage and unsettles its neighbours is not a repair.
NieR — bars 1–22 Ordinary two-staff writing that PD-3 should not have touched. If anything here reads worse than it used to, that is a regression.

For each one, we would like to know:

Are the clefs and staff changes easier to read?
Are the musical lines easy to follow?
Are there remaining collisions or overcrowded passages?
Could you actually practise this section?

Report an issue

Every song page has a Report an issue panel at the bottom. It asks what kind of problem it was, what happened, and what you expected — and it attaches where you were: the bar, the time, the speed, the hand mode and the loop.

There is no server behind it. Your report is saved on this device until you press Copy report or Download and send it back to whoever gave you this link. It survives a reload, so you can collect several and send them together.

Known limitations

The notes and the rhythm are worked out automatically, and both are imperfect. There is no accuracy figure to quote and we are not going to invent one.
Solo piano and mixed-instrument music are different problems. A piano recording is what this is built for; a song with vocals, synths and drums is much harder, and one of the two songs here is exactly that case.
Dense passages can still be hard to read.
Conventional printed pickups (upbeats) are not finished.
MIDI keyboard support depends on your browser: Chrome and Edge on desktop can do it, Safari and Firefox generally cannot. Without a keyboard the page still plays and lights the notes — it just does not grade you.
No physical MIDI keyboard has been tested on this build. The MIDI path has been exercised with a simulated keyboard only.
An experimental metrical analysis that we measured and rejected is switched off here.

What this build is not

You cannot add your own song: turning a recording into a page needs a machine with the models on it, and that is done on our side. There are no accounts, no uploads and no payments. A "faithful score" here means the page shows what the app decided — not that what it decided matches the original recording.