14 Dec
2009
14 Dec
'09
4:32 p.m.
Hi folks, I have a Firepod with midi on board. I got it working ( thanks to
help from here ) and jack starts up, qjackctl shows its ports in the connect
window. I'm stumped with how to route midi signals from the firepods midi
port, which *only* appears in the jack-midi tab of connections, to the
alsa-seq midi ports of the applications I want to control.
I read this:
http://wiki.linuxaudio.org/faq/start?redirect=1#qwhat_is_the_difference_bet…
And it says that I can start qjackctl with three options for midi-in-jack:
none, raw, and seq. Sounds like seq is what I want but I can't find anywhere
in qjackctl to choose this.
Thanks
iain
14 Dec
14 Dec
6:54 p.m.
On Mon, 2009-12-14 at 12:32 -0800, Iain Duncan wrote:
And it says that I can start qjackctl with three
options for
midi-in-jack: none, raw, and seq. Sounds like seq is what I want but I
can't find anywhere in qjackctl to choose this.
That option is only available if you are using the ALSA audio driver.
However, a2jmidid will do what you're after.
6:58 p.m.
On 12/15/2009 06:32 AM, Iain Duncan wrote:
I can start qjackctl with three options for
midi-in-jack: none, raw, and seq. Sounds like seq is what I want but I
can't find anywhere in qjackctl to choose this.
Setup > Settings tab, bottom left, where it says Midi driver.
Another option for bridging Jack to Alsa midi or vice versa is a2jmidid,
which can either run as daemon and bridge automatically, or let you
start static bridges from the commandline on a needs basis.
http://home.gna.org/a2jmidid/
11:13 p.m.
On 14/12/2009, "M Watts" <zwy648rct(a)gmail.com> wrote:
On 12/15/2009 06:32 AM, Iain Duncan wrote:
If you're only connecting a small number of ports you could always use
the simple method of connecting the jack-midi port to jack-midi-through
which magically connects to alsa-midi-through which you then connect to
the alsa-midi-port. (or am I missing something?)
I can start qjackctl with three options for
midi-in-jack: none, raw, and seq. Sounds like seq is what I want but I
can't find anywhere in qjackctl to choose this.
Setup > Settings tab, bottom left, where it says Midi driver.
Another option for bridging Jack to Alsa midi or vice versa is a2jmidid,
which can either run as daemon and bridge automatically, or let you
start static bridges from the commandline on a needs basis.
http://home.gna.org/a2jmidid/ 
15 Dec
15 Dec
5:07 a.m.
On Tuesday 15 December 2009 04:13:38 james morris wrote:
On 14/12/2009, "M Watts"
<zwy648rct(a)gmail.com> wrote:
>On 12/15/2009 06:32 AM, Iain Duncan wrote:
>> I can start qjackctl with three options for
>> midi-in-jack: none, raw, and seq. Sounds like seq is what I want but I
>> can't find anywhere in qjackctl to choose this.
>
>Setup > Settings tab, bottom left, where it says Midi driver.
<snip>
If you're only connecting a small number of ports you could always use
the simple method of connecting the jack-midi port to jack-midi-through
which magically connects to alsa-midi-through which you then connect to
the alsa-midi-port. (or am I missing something?)
Yes, you are both missing that the jack-midi-to-alsa-midi bridge is only
included in the alsa backend, not in the ffado (aka firewire) backend.
a2jmidid (or similar apps) are the only solution here.
Or just use jack-midi enabled apps:-)
Arnold
5505
days inactive
5506
days old
linux-audio-user@lists.linuxaudio.org
4 comments
5 participants
participants (5)
-
Arnold Krille -
Iain Duncan -
james morris -
M Watts -
Peter Nelson