|
|
|
|
|
by jerf
1504 days ago
|
|
I like the idea with the octaves. I'm not as sure about the chromatic stuff; the key signatures are there for a reason and I'm not sure it reduces the cognitive load in an expert. It would in an novice, sure. Possibly said novice would then move on to prefer it as they become an expert, so it's hard to tell. On-the-fly transposition would probably be a bit harder, but perhaps that's a skill level already so high that it's hardly worth optimizing for in the notation anyhow. But definitely there's too much dependency on where note heads are versus the staff. Even in the typography used in the example, the note heads seem to noticeably hang below the line. I'm not sure the vaguely elliptical blobs really work with this system and I'd consider pushing another step away from conventional notation and distinguishing with something more visually clear, e.g., normal heads on the lines, squared-off heads if they are a half step away or something. Something that makes it completely unambiguous whether a note is on or in the line. ("Unfortunately" conventional notation that this is trying to be compatible with has already consumed whether the head is hollow.) I would also like to see something less trivial on the intro page. In HN terms, visual programming always looks awesome as long as you're demonstrating something drop-dead simple like simply traversing a linked list or something. Show something with a bit more crunch in it, like even something as simple as a quicksort, and the vast majority of visual programming pitches suddenly look a lot less compelling. All the PDFs on the bottom of the page 404'd for me, but I'd like to see something inline. Still, some interesting ideas here. The standard system is definitely a bit wrapped around a piano. I could see how this could simplify teaching any instrument that makes one tone at a time; all the rules for reading music become "this note -> this fingering/position/valves/etc", which would smooth over the first couple of years nicely. One of the tensions of the current system is the learning novice vs. the expert. The current system is heavily tilted towards an expert. At the time it was written, that was appropriate. Building some more novice-friendly features in might be more appropriate in a more democratized era. (Though how one gets past the switching costs here for any alternate notation I have no idea.) |
|