0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, // row1
0x05, 0x06, 0x07, 0x08, 0x09, 0x0a, 0x0b, 0x0c, // row2
0x0a, 0x0b, 0x0c, 0x0d, 0x0e, 0x0f, 0x10, 0x11, // row3
0x0f, 0x10, 0x11, 0x12, 0x13, 0x14, 0x15, 0x16, // row4
0x14, 0x15, 0x16, 0x17, 0x18, 0x19, 0x1a, 0x1b, // row5
0x19, 0x1a, 0x1b, 0x1c, 0x1d, 0x1e, 0x1f, 0x20, // row6
0x1e, 0x1f, 0x20, 0x21, 0x22, 0x23, 0x24, 0x25, // row7
0x23, 0x24, 0x25, 0x26, 0x27, 0x28, 0x29, 0x2a, // row8
I was never comfortable with hexadecimal but I think I did well :P
So, I think that's how it would be laid out where each row increases by 5 semitones, I know the notes get doubled, but this makes interesting for interesting 3 octave chords.
I'm making 2 8x8 matricies which will sit next to eachother; I take it that all these number are in relation to the base note correct? If that's the case then I wouldn't have to make 2 separate tables, because the second table would be the same just transposed up 8 semitones.
And if this table editing method is incorporated into the csv file, it would help with creating different "tunings" for my box of buttons.