On 11/4/24 15:48, Alberto Novello wrote:
Which is what worries me cause there is no Pure Data even if it's running....
right, that would explain why 'aconnect' cannot connect :-)
the default MIDI backend in Pd is "OSS MIDI". in order to ALSA seq as a MIDI backend, you have to explicitly choose it. the simplest way is obviously via the "Media" menu (pick the aptly named "ALSA-MIDI", and make sure to set the "In Ports" and/or "Out Ports" to some non-0 value (e.g. "1"). to make the settings persistent, you have to "Save All Settings".
alternatively (if you start Pd from the cmdline), you could simply add the "-alsamidi -mididev 1" flags.
note: for some obscure reason which i do not remember, the default number of in/out ports for ALSA-MIDI is 0 (zero, nada). Adding the flag "-mididev 1" will make sure you get one port in each direction. contrary to common sense, the actual number you put there does not matter (so you could also use "-mididev 0" to get one port. If you want multiple ports, specify them with multiple comma-separated numbers. e.g. "-mididev 1,2" will give you to ports. that's because with "-mididev" you are actually 'selecting' (pseudo-)MIDI devices rather than specifying their number. this is for consistency with other backends.
mfgasdr IOhannes
PS: personally i think that this behaviour is non-intuitive (even though iirc it was me who implemented it like this) and should probably be fixed as in:
- '-alsamidi' (without any "-mididev" argument) should default to a
single port.
- '-alsamidi -mididev 2' should probably create a single port as well,
but with a port-number "2" (for both in and out port). similarily, "-alsamidi -mididev 1,4" should create two ports with port-numbers "1" resp "4". probably time for a feature request :-)