What's the MIDI driver you're telling jackd to use (ie. the -X command line option) ?
If it's -X raw then that explains it: all external MIDI ports most probably will get owned and locked to JACK-MIDI backend and there's no way you can handle connections on those from the ALSA-MIDI side of things, not even from QjackCtl ALSA tab for that matter.
I'll suggest you to get rid of the -X raw JACK-MIDI setup, and bring either -X seq or better yet all around a2jmidid into the scene .
What's the MIDI driver you're telling
jackdto use (ie. the-Xcommand line option) ?If it's
-X rawthen that explains it: all external MIDI ports most probably will get owned and locked to JACK-MIDI backend and there's no way you can handle connections on those from the ALSA-MIDI side of things, not even from QjackCtl ALSA tab for that matter.I'll suggest you to get rid of the
-X rawJACK-MIDI setup, and bring either-X seqor better yet all arounda2jmididinto the scene .Cheers