Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Why use this piano-roll visualization rather than just color coding notes on sheet music? You lose a lot of other information in the process (like, almost all of it).




You're very close to Aikin shape note heads! These help sight-read in any key, since they're always shaped according to whatever the relative major is, and so it's easy to learn the intervals between any two shapes.

https://en.wikipedia.org/wiki/Jesse_B._Aikin


Yeah this is basically shape notes with colors, in a MIDI format. Not helpful for non-digital musicians

Fair point.

In my approach I got very dense yet readable information density on the screen. Eg. the entire Mov. 1 of Moonlight sonata is a single screen on my 16" Mac, yet all tonal effects are there, visible: https://rawl.rocks/f/Sonate_No._14_Moonlight_1st_Movement


The first movement. Which is 4 pages long. You could display 2 pages on a 16" screen, so you improved density by 2x but you have no articulation, no dynamics or tempo markings, no legato/phrasing notation, no LH/RH indication.

If you really wanted to show the harmony as densely as possible you could fit the whole movement on 1 page with figured bass and a comment or two about how to play the arpeggios.

I'm not a hater, I encourage the exploration. Just get personally frustrated when we aren't ever building on 1000 years of music notation and instead starting with MIDI and DAW style slop - it's not value-add for serious classically trained artists, and (imo) pushes music dilettantes in the wrong directions


So here I stand with dilettantes :)

Being a jazz college dropout, I stopped building around standard notation when after two years of training - and I started learning piano at 25 - I still didn't get any fluency in instantly seeing harmonic structure in the scores.

I don't care that much about articulation. I can hear articulation anyways. What I care about is the elusive layer of harmony which is so hard to reason about without the right tools.

That's why people do Roman numerals, figured bass, all sorts of annotation: https://github.com/vpavlenko/study-music/blob/main/parts/cla...

And that's what I was chasing. Something that gives me, a guy who didn't spent formative years of K-12 by sight-reading at the piano, a way to build mental models of how Western harmony works.

And here, I believe, I'm with the majority of people.


OK let me suggest something to meet you halfway. As someone who is fluent/sight reading/ singing etc and can "hear" harmony and/or "read" it on a page of regular notes (lines and spaces and intervals all you really need, but to your point requires experience), something that would be far more interesting and useful to me, rather than color-coding solfege, would be something more along these lines:

Color code each chord by its diatonic value (e.g. in a I chord every note in the triad is red, in a IV chord every note in the triad is blue) and then highlight the extended notes as well (e.g. add 9 is yellow, add 11 is green)

That is something that MIGHT be interesting to me (personally - I know I am not your audience). But even thinking it through this technique sort of washes out the interesting bits of substitution/interpretation etc that you can find because you are committing to interpreting a chord with a single root


Yeah, I see your point. You want same alterations on different Roman numerals to look the same. (In my current system b9 over I and b9 over V look different.)

I briefly explored this appoach: https://rawl.vercel.app/edit?a=beethoven_op10no1mov1 (Although it was a mess.)

In current Rawl terms I call it "annotate modulation at every chord".

Back in the days I thought it's better.

It turned out that:

- You need to do tedious annotation. So you can only work with classical repertoire datasets like https://github.com/MarkGotham/When-in-Rome

- Worse even, you need to look at two places simultaneously: to the score and to the string of Roman numerals

- And worse still, all chords then look the same. The score itself becomes bland. Most of the time, if you aren't deep inside the jazz repertoire, there isn't that many alterations. So you'd mostly see the same four colors - root, minor third, major third, perfect fifth.

- And, as evident in Mozart-Beethoven repertoire, you need to decide what to do with fully diminished chords. Because they sorta don't have a root, acoustically.


Thanks for the example. Devils advocate:

> You need to do tedious annotation. Worse even, you need to look at two places simultaneously: to the score and to the string of Roman numerals

The more work it takes to create your notation, the more useful information it contains. Developer-user tradeoff

> And worse still, all chords then look the same. The score itself becomes bland. Most of the time, if you aren't deep inside the jazz repertoire, there isn't that many alterations. So you'd mostly see the same four colors - root, minor third, major third, perfect fifth.

Isn't the same true for your current method? Only there are more colors of the rainbow to distract you from how bland it is :)


Well said! I agree. I find that standard notation is an amazing tool for conveying how to perform a piece, and absolutely terrible for understanding the harmonic structure and reasoning about a piece. That stuff is all hidden and inferred if you have the years of experience to just know all the intervals present at a glance.



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: