Forum

Very cool, both from the what-it-does and the how-it's-done (Python only) side!
Perhaps we could use Lilypond export for note lengths (so you don't have to know the song) and pictures of the chord shape for better memorization:
http://lilypond.org/doc/v2.12/input/lsr/lilypond-snippets/Fretted-strings
It seems to be possible to use 5 string tabs and special tunings, here an example for a banjo:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Banjo.en.html

-Ferdinand

@Ferdinand, that could be an interesting avenue, feel free to take a stab at it. One thing that might not be possible (need to check) is that on the Eigenharp each course can have multiple keys pressed, which is why I added a notation like: 3|5|6 where three keys on the same course are pressed simultaneously. With traditional stringed instruments that's not meaningful to write, so I'm not sure it's possible in traditional notation packages.

Yes, a notation GUI with editing capabilities would be important as no existing solution does it for the Eigenharps (optimally with sequencer capabilities that allow to show and edit the underlaying unquantized per-note events)
Playback with lights that even waits until you pressed the keys is very cool, too. (You can have something similar by using the MIDI illuminator and playing the phrase you want to practise in a loop)

Am still trying to find really matching notations that focus on these properties
1) easy on the mind regarding transfer from score to instrument (this is quite good with tabulature)
2) allows to understand musical structure on the score (that's one of the weak points of tabulature)
3) works with various layouts (a weak point of the bar graph "groups of four" approach I was fiddling around with - it is pretty good in 1&2 but only really works for the horizontal layout. This is nice with Tabulature)
4) easy to write with (one) pen&paper (one of the major selling points of traditional notation)
5) "dense" enough that you can play from printed scores without having to turn pages too often

Getting all those things together is challenging, but I don't give up - yet.

Diagrams wouldn't be that difficult with what I have now since it has a concept of 'chords' based on the time interval between key presses. Ideally I think though that it would probably require metronome support to be useful. It could then detect which keys have been played during bars/beats and aggregate those in a chord diagram. However, I suspect that there will be a lot of 'wrong' diagrams though, so maybe a manual process would indeed be better.