nah, after hours of looking... I can't find out where and why /dev/midi1 is linked to hw:1,0,0 , or anyway to tell it to create more raw devices, or to change where it points.
the documentation is absolutely dreadful, and misleading, e.g. the /dev/midiXX is clearly documented, yet not only bela, but also raspbian and ubuntu 14 don't seem to do this, they all use /dev/midi1 - its really frustrating the lack of documentation, and then the quality is so poor/out of date.
I looked into the sequencer, there is no /dev/sequencer i suspect this only get created when an app registers itself as a sequencer, i.e. bela would need to use the alsa api to become a client.
virtual midi, the snd-virmidi does not exist on bela.
Im coming to the conclusion the rawmidi is really only backwards compatible, and perhaps not as 'feature rich' as Alsa, so I think it would be wise to perhaps move bela to use the alsa raw midi api.
(Id give it a go, but Ive not worked out how to compile my own version of bela yet 🙂 )
Pure data does allow for multiple midi devices/ports, and it 'fakes' it by using midi channels 😉
i.e. midi channel 17 = device/port 2, midi channel 1 (see http://en.flossmanuals.net/pure-data/midi/using-midi/)
not every elegant , but works and could be not too tricky to implement, if you allow for multiple midi ports.