so Ive just been hosting the midihub on the Organelle (arch linux) rPI (raspbian latest) and found an oddity
on alsa we see
aconnect -l client 28: 'midihub MH-2BXG0QD' [type=kernel] 0 'midihub MH-2BXG0QD MIDI 1' 1 'midihub MH-2BXG0QD MIDI 2' 2 'midihub MH-2BXG0QD MIDI 3' 3 'midihub MH-2BXG0QD MIDI 4' 4 'midihub MH-2BXG0QD MIDI 5' amidi -l IO hw:0,0,0 midihub MH-2BXG0QD MIDI 1 IO hw:0,0,1 midihub MH-2BXG0QD MIDI 2 IO hw:0,0,2 midihub MH-2BXG0QD MIDI 3 IO hw:0,0,3 midihub MH-2BXG0QD MIDI 4 IO hw:0,0,4 midihub MH-2BXG0QD MIDI 5 IO hw:1,0,0 Ableton Push 2 MIDI 1 IO hw:1,0,1 Ableton Push 2 MIDI 2 IO hw:2,0 pisound MIDI PS-3TG77SW
the issue is, 28:0 MIDI 1 is actually whats called port 5 on the mac , i.e. the control port
and so port 1 on the mac is MIDI 2 on the Organelle/rpi
(or if you wish hw:0,0,1 midihub MH-2BXG0QD MIDI 2, actually is USB A !)
it confused me quite a bit, as wasn’t getting any data , and theres no indicator of usb activity
(see previous issue )
ideally, hw:0,0,0 should be port 1 (USB A), and so the control port would be on hw:0,0,4
this is because quite a bit of software defaults to the first port, and some ‘dodgy’ software don’t even cope with usb subports, and just assume first port !
(not your issue, but if you want high compatibility its worth being aware of)
also perhaps in the usb description , you could label ‘port 5’ as CONTROL.
perhaps also it would be better to have the ports labelled A-D as well, given the case and editor labelling.
midihub MH-2BXG0QD MIDI A
midihub MH-2BXG0QD MIDI B
midihub MH-2BXG0QD MIDI C
midihub MH-2BXG0QD MIDI D
midihub MH-2BXG0QD CONTROL
(similar to ableton push which labels them LIVE, and the other USER)
note: i recognise some os/software does not use the usb description, but thats their problem