Why a melody wants to be a number

The first time I wrote out a Cantonese folk song as numbers instead of noteheads, something that had felt fussy on a staff went quiet and simple. The melody was the same. What changed was how much the page was trying to tell me.

A staff is an absolute instrument. It insists on this exact pitch, in this exact octave, before it will tell you anything about the tune. That precision is a gift when you're writing for an orchestra, where the difference between a G and a G-sharp is somebody's afternoon. It's a tax when you're writing a melody that a dozen different people will sing in a dozen different keys.

What the number keeps

Numbered notation keeps the part of a melody that actually travels: the relationships between the notes. A 5 leaning home to a 1. A 3 that wants to fall to a 2. Those pulls are the melody. They don't change when you move the whole thing up a fourth to suit a lower voice — so a notation built on scale degrees doesn't change either.

• The staff answers "what pitch is this?"
• The number answers "where is this in the key?"
• A singer transposing on the fly needs the second answer, not the first.

What it gives up, on purpose

It's not free. You lose the instant, spatial read of a staff — the way a rising line looks like it rises. You lose absolute pitch, which instrumentalists lean on. For polyphony, for anything where exact register is the point, the staff wins and it isn't close.

Every notation is an argument about what matters most. The staff argues for pitch. The number argues for the key-relative shape of a line. Neither is wrong; they're answering different questions.

Building a tool around numbered notation has mostly been an exercise in taking that argument seriously — in resisting the urge to bolt every feature of a staff back on, and trusting that a melody, written as the thing it actually is, is enough.