Just for completeness here’s a linux based midi-monitor sketch. If any one has any alternatives please pipe up. . .
(The & run it in the background so you get a prompt back),
Will give you . . .
> chris@ellie-Inspiron-N5030:~$ Waiting for data at port 128:0. Press Ctrl+C to end.
> Source Event Ch Data
As it say’s it ‘looking’ at MIDI Alsa Port 128:0 so until something is patched into that it isn’t going to register anything.
So let’s confirm what we have in the Alsa world.
aconnect -lo (list the Alsa outputs)
chris@ellie-Inspiron-N5030:~$ aconnect -lo
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 128: 'aseqdump' [type=user,pid=9216]
0 'aseqdump '
client 129: 'QmidiNet' [type=user,pid=9227]
0 'port 0 '
1 'port 1
Ooooh look we have two qmidinet ports cos this linux machine is running qmidinet on it, and a sperate remote zynthian is also running with the qmidinet option turned on…
so connect the qmidinet:0 bus to aseqdump . . . .
chris@ellie-Inspiron-N5030:~$ aconnect 129:0 128:0
0:1 Port subscribed 129:0 -> 128:0
And play some notes on the remote zynthian . . .
chris@ellie-Inspiron-N5030:~$ 129:0 Pitch bend 0, value 0
129:0 Note on 0, note 33, velocity 55
129:0 Note off 0, note 33, velocity 52
129:0 Pitch bend 0, value 0
129:0 Note on 0, note 33, velocity 71
129:0 Note off 0, note 33, velocity 108
This has been:
- An example of Alsa MIDI monitoring on Linux (which perhaps with the wolfpaw98 post be moved to a seperate new thread…?)
- A call for any other linux MIDI monitoring techniques people use.
- A shameless advert for qmidinet networking on Zynthian. . .
I’ll go back to water pumps. . . .