Hello Aaron and Jack-Team!
There seems to be a bug in my jack_lsp. I just started a2jmidid and
j2amidi_bridge. when I do a jack_lsp I get all the ports.
When I do: jack_lsp -t midi I only get one port from jack_midi_clock, but
none of the other ones.
When I type: jack_lsp -t, I can't see a difference between the
jack_midi_clock port and the others:
jack_lsp -t
[...]
a2j:Virtual Raw MIDI 0-0 [16] (capture): VirMIDI 0-0
8 bit raw midi
a2j:Virtual Raw MIDI 0-0 [16] (playback): VirMIDI 0-0
8 bit raw midi
a2j:Virtual Raw MIDI 0-1 [17] (capture): VirMIDI 0-1
8 bit raw midi
a2j:Virtual Raw MIDI 0-1 [17] (playback): VirMIDI 0-1
8 bit raw midi
a2j:Virtual Raw MIDI 0-2 [18] (capture): VirMIDI 0-2
8 bit raw midi
a2j:Virtual Raw MIDI 0-2 [18] (playback): VirMIDI 0-2
8 bit raw midi
a2j:Virtual Raw MIDI 0-3 [19] (capture): VirMIDI 0-3
8 bit raw midi
a2j:Virtual Raw MIDI 0-3 [19] (playback): VirMIDI 0-3
8 bit raw midi
a2j:M Audio Delta 1010LT [20] (capture): M Audio Delta 1010LT MIDI
8 bit raw midi
a2j:M Audio Delta 1010LT [20] (playback): M Audio Delta 1010LT MIDI
8 bit raw midi
j2a_bridge:playback
8 bit raw midi
a2j:j2a_bridge [129] (capture): capture
8 bit raw midi
Jack MIDI Clock:midi_out
8 bit raw midi
Or is the argument "midi" only seen as the start of a port_name?
If so, Aaron, you must rewrite this part of jackctl (I guess you do what I
described, because I get exactly your output). You should rewrite it using:
jack_lsp -t
And then parse the type info underneath each name. I think a simple grabbing
for "audio" or "midi" will do. But I guess, that in the long run,
using the
python module for jack, will be more efficient and easy to use.
Kindly yours
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de