So I have had a quick look and the situation has changed with respect to what the OP described.
Running
root@bela:~# aconnect -i -o
now gives:
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 16: 'f_midi' [type=kernel]
0 'f_midi '
client 20: 'MIDI Mix' [type=kernel]
0 'MIDI Mix MIDI 1 '
So the connected MIDI device (and the virtual one to the host, too) do show up as available I/O in the ALSA sequencer.
Therefore, when running
MIDIClient.init;
inside sclang
, it gives:
MIDI Sources:
MIDIEndPoint("System", "Timer")
MIDIEndPoint("System", "Announce")
MIDIEndPoint("Midi Through", "Midi Through Port-0")
MIDIEndPoint("f_midi", "f_midi")
MIDIEndPoint("MIDI Mix", "MIDI Mix MIDI 1")
MIDIEndPoint("SuperCollider", "out0")
MIDIEndPoint("SuperCollider", "out1")
MIDIEndPoint("SuperCollider", "out2")
MIDI Destinations:
MIDIEndPoint("Midi Through", "Midi Through Port-0")
MIDIEndPoint("f_midi", "f_midi")
MIDIEndPoint("MIDI Mix", "MIDI Mix MIDI 1")
MIDIEndPoint("SuperCollider", "in0")
MIDIEndPoint("SuperCollider", "in1")
MIDIEndPoint("SuperCollider", "in2")
MIDIEndPoint("SuperCollider", "in3")
MIDIEndPoint("SuperCollider", "in4")
Now, I don't know much of Supercollider or of how sclang
should handle MIDI, but the above seems promising. Can you reproduce the above? How can I reproduce your problem?