LilyPond as well as ABC notation cannot be stored in an int array, which makes moving things back and forth more difficult.
GUIDO looks cool and looks similar to an earlier format I tried using strings to store data. It looks fully featured, but it is not hex.
MusicXML takes a bunch of time writing tags. If I were to write it out by hand, it would require more tags and more lines than hex.
RTTTL : I'm not sure how to do dotted quarter notes, tied 8th to a dotted triplet. It seems similar to a text2Midi solution I created earlier, except my solution accounts for those edge cases.
I took your suggestion on getting started and put it into a github readme: https://github.com/fornof/hexNoteG9/blob/master/README.md
I used LMMS and have taken a look at AbletonLive - both require heavy use of the mouse to get anything setup for music generation. My plan is to start at the bottom of the stack - sending notes through hex , and build on that so an artist could go in and edit the hex notes if they really wanted to, that it would be more readable than midi, and then the changes would show up in the layer above the hexnotes with buttons, sliders, a staff, and general UI.
do any of those alternatives have standards for machine-readable notation?
edit:
one way to get started would be to put together your own first draft of the specification, with examples, on a place where others can easily read it and suggest improvements (e.g. it could start off being a file in a git repo hosted on github.com, say ).
answering my own question:
some random alternatives might include:
MIDI -- https://www.midi.org/specifications
LilyPond -- https://en.wikipedia.org/wiki/LilyPond#Overview_of_input_syn...
GUIDO -- https://github.com/grame-cncm/guidolib/blob/dev/doc/GUIDO-Mu...
MusicXML -- http://w3c.github.io/musicxml/
RTTTL (RingTone Text Transfer Language) -- http://www.panuworld.net/nuukiaworld/download/nokix/rtttl.ht...