Hacker News new | ask | show | jobs
by wam 4811 days ago
The discussion here reminds me of the longstanding debate over editors like vim/emacs vs (whatever you want to call the other editors). Or semicolons vs indentation, to make a slightly more "reading" oriented comparison.

There's obviously a difficult learning curve for many people, but others who are already proficient argue that the rewards of learning standard music notation are worth an extended effort, if that's what it takes.

The thing I've noticed most about sheet music as I'm learning it is that it's compressed. It uses different symbols and techniques to say the same thing in a smaller space, and reuses space and symbols more efficiently by applying modifier symbols at the beginning of the staff and elsewhere. It allows notes on lines and spaces instead of just spaces or just lines. Tighter, smaller, more on the page. Changes in pitch can also be indicated by modifier codes next to the notes, sharp and flat, allowing further combinations with only 2 more symbols.

So I have to learn to decompress the information at the same time I'm interpreting it. Tricky! I do stop and wonder if this compression algorithm is the right fit for humans. I don't buy the argument that continuity with the volume of existing sheet music is a good reason to never develop an alternative. But any alternative needs to be much better on some metric that outweighs continuity. Otherwise we should just keep hacking the learning process with color coding and mnemonics and whatnot.

It's funny, I was talking to a friend about my struggle to learn sheet music and music theory, and he said "It seems hard at first but you'll start to get it pretty soon." And I said "Yeah, it's sort of like math in that way." To which he replied "oh, I don't know about that, I can't do math. I've never been good at it."

1 comments

The difference between "editor wars" and a new musical notation is that choosing a particular editor does not limit you in reading or writing things that people have already done. If I learn to read music via new notation, that's great, but I'll still have to learn traditional notation if I want to play a piece by Chopin (assuming someone hasn't "translated" it to the new notation). If I use vim, I can still read a program written in emacs. Editing it may be a different process, but consuming it isn't.
That's true, but the comparison I'm getting at is the learning curve. The process of consuming an algorithm or procedure is more of a tabs-vs-semicolons thing, a language war.

I mention editors because the arguments about learning one often have to do with the trade-off between expert efficiency and expressiveness and the painful learning curve (for many). And because that's honestly what the discussion reminds me of, whether or not it's a perfect match :)

Why can't notation be shown "on the fly"?

I mean, any notation editor knows the pitches/timing/etc encoded in the score, and it should be able to trivially show it to the musician in a customized way - transposed to the instrument, if neccessary; with or without fingering information where applicable; and in custom/wierd notations like this one.

Of course, printed/photocopied scores can't do that, but we're not in stone&paper age anymore and can fix things to improve functionality.