Leaderboard

No worries, PCBs should be here today if DHL get their act together. I have white 0.96" OLEDs on the way, could possibly try with a yellow-blue I have left. The thing is, you don't have an ordinary button layout, so maybe traditional SCS LCD functions don't make sense anyway. But as far as the display goes, a 2*20 CLCD is 100 pixels across with a gap of ~1 pixel in between characters. So the horizontal resolution is comparable. I chose the 6 button "hex" layout just to try something different. My thought was that there's enough space to provide two menu rows of 3 items each. Have to see though, my guess is @Hawkeye will do most of the hard work with the Programma builds ;-). This gives an idea of how the text fits, approximately 20 characters:

I also see some use for an abstraction layer for the hardware I/O. To me the logical place to do this would be the MIDI router menu. Hardware ports could be mapped to virtual port. Tracks are then mapped to these virtual ports. One nice side effect could be that only mapped virtual ports could be mapped to tracks thereby reducing the number of outputs avalible to a tracks to only ports that are used, assuming the physical>virtual mapping is set up correctly.

Some virtual mapping layer defo seems like the way to go. The world can never have too many API layers.

Dear Peter, thanks for your reply. I'm thinking about another approach with groups, patterns and tracks that has more flexibility and could solve this. But I worrying that it also would lead to a MBSEQ V5 .... Best Michael