22 Jan
2008
22 Jan
'08
8:14 p.m.
Ok, I have a two part question. First, is there a tool like
jack.plumbing to maintain MIDI connections. If there's not, I'd be
happy to help in the development of one. I would use QJackCtl's
patchbay feature but I need to set up and maintain these connections
quickly and would prefer to use a simple text file for connections rules
and have a daemon that maintains them.
Secondly, what is the difference between the JACK midi and the ALSA
midi. So far, I haven't seen many applications that support the JACK
MIDI. Can I communicate between ALSA MIDI applications and JACK midi
ones? If not, what is the point of adding MIDI capabilities to JACK?
Thanks in advance,
Miguel
--
My Website:
http://eckz.zapto.org/eckz/
23 Jan
23 Jan
6:19 a.m.
hi m
1. i think you need "aconnectgui" or "kaconnect", very simple tools to
route your midi connections. there is "aconnect" as a command line tool.
2. as far as i know there is no difference between jack midi and alsa
midi - jack is using alsa midi.
hope this helps
nikola
Miguel M wrote:
Ok, I have a two part question. First, is there a
tool like
jack.plumbing to maintain MIDI connections. If there's not, I'd be
happy to help in the development of one. I would use QJackCtl's
patchbay feature but I need to set up and maintain these connections
quickly and would prefer to use a simple text file for connections rules
and have a daemon that maintains them.
Secondly, what is the difference between the JACK midi and the ALSA
midi. So far, I haven't seen many applications that support the JACK
MIDI. Can I communicate between ALSA MIDI applications and JACK midi
ones? If not, what is the point of adding MIDI capabilities to JACK?
Thanks in advance,
Miguel
9:52 a.m.
On Wed, 23 Jan 2008 11:19:29 +0100
jeremaja niko <jeremaja.niko(a)googlemail.com> wrote:
hi m
1. i think you need "aconnectgui" or "kaconnect", very simple tools
to route your midi connections. there is "aconnect" as a command line
tool.
2. as far as i know there is no difference between jack midi and alsa
midi - jack is using alsa midi.
hope this helps
nikola
2. is true for older jack, however newer versions and the 0.109 release
also support jack midi where the big difference is, as far as I
understand it, that jack midi has the same time source as jack audio,
whereas alsa midi and jack audio have different time sources.
They are not compatible by default, recent qjackctl and patchage can
manage both. There are little apps like a2jmidid that allow you to
connect alsa midi to jack midi ports.
hope it doesn't confuse even more ;)
regards
Philipp
1:59 p.m.
On Wed, 2008-01-23 at 14:52 +0100, hollunder(a)gmx.at wrote:
On Wed, 23 Jan 2008 11:19:29 +0100
jeremaja niko <jeremaja.niko(a)googlemail.com> wrote:
They _are_ compatible by default (to some degree) - just start jackd
0.109 with the '-X seq' command line parameters to the ALSA driver and
all ALSA sequencer ports will appear as JACK MIDI ports.
--ll
hi m
1. i think you need "aconnectgui" or "kaconnect", very simple tools
to route your midi connections. there is "aconnect" as a command line
tool.
2. as far as i know there is no difference between jack midi and alsa
midi - jack is using alsa midi.
hope this helps
nikola
2. is true for older jack, however newer versions and the 0.109 release
also support jack midi where the big difference is, as far as I
understand it, that jack midi has the same time source as jack audio,
whereas alsa midi and jack audio have different time sources.
They are not compatible by default, recent qjackctl and patchage can
manage both. There are little apps like a2jmidid that allow you to
connect alsa midi to jack midi ports.
2:59 p.m.
>
> 2. is true for older jack, however newer versions and the 0.109 release
> also support jack midi where the big difference is, as far as I
> understand it, that jack midi has the same time source as jack audio,
> whereas alsa midi and jack audio have different time sources.
>
Oh, ok, to it's the time source. I'm guessing it would be better to
for
applications to use the native jack midi that way the transport and MMC
time can be in sync. I wonder if there are timing issues when using
a2jmidid, or if it's better to use the -X seq option as suggested.
Oh well, it's time to experiment a bit.
BTW, aconnect is what I'm looking for. I'll wrap if in a script to
re(a)connect the midi connections if an application were to crash.
Thanks for the info,
Miguel
On Wed, 2008-01-23 at 18:58 +0100, Lars Luthman wrote:
> On Wed, 2008-01-23 at 14:52 +0100, hollunder(a)gmx.at wrote:
> > On Wed, 23 Jan 2008 11:19:29 +0100
> > jeremaja niko <jeremaja.niko(a)googlemail.com> wrote:
> >
> > > hi m
> > >
> > > 1. i think you need "aconnectgui" or "kaconnect", very
simple tools
> > > to route your midi connections. there is "aconnect" as a command
line
> > > tool.
> > >
> > > 2. as far as i know there is no difference between jack midi and alsa
> > > midi - jack is using alsa midi.
> > >
> > > hope this helps
> > > nikola
>
> 2. is true for older jack, however newer versions and the 0.109 release
> also support jack midi where the big difference is, as far as I
> understand it, that jack midi has the same time source as jack audio,
> whereas alsa midi and jack audio have different time sources.
>
> > They are not compatible by default, recent qjackctl and patchage
can
> > manage both. There are little apps like a2jmidid that allow you to
> > connect alsa midi to jack midi ports.
>
> They _are_ compatible by default (to some degree) - just start jackd
> 0.109 with the '-X seq' command line parameters to the ALSA driver and
> all ALSA sequencer ports will appear as JACK MIDI ports.
>
>
> --ll
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
--
My Website:
http://eckz.zapto.org/eckz/
10:25 p.m.
Miguel M <therevoltingx(a)gmail.com> writes:
a2jmidid and -X seq should have same timing issues. In fact they are
almost same code. a2jmidid is there mainly to auto expose ALSA seq
clients when using -X raw
Some ppl use it to expose hardware ALSA seq port of card, different from
one used through different ALSA audio backend. After doing small tweak
in the code to disable fitering of hardware ports.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
> 2. is
true for older jack, however newer versions and the 0.109 release
> also support jack midi where the big difference is, as far as I
> understand it, that jack midi has the same time source as jack audio,
> whereas alsa midi and jack audio have different time sources.
>
Oh, ok, to it's the time source. I'm guessing it would be better to
for
applications to use the native jack midi that way the transport and MMC
time can be in sync. I wonder if there are timing issues when using
a2jmidid, or if it's better to use the -X seq option as suggested.
Oh well, it's time to experiment a bit. 
24 Jan
24 Jan
6:55 a.m.
Am Donnerstag, 24. Januar 2008 schrieb Nedko Arnaudov:
Miguel M <therevoltingx(a)gmail.com> writes:
a2jmidid and -X seq should have same
timing issues. In fact they are
almost same code. a2jmidid is there mainly to auto expose ALSA seq
clients when using -X raw
Some ppl use it to expose hardware ALSA seq port of card, different from
one used through different ALSA audio backend. After doing small tweak
in the code to disable fitering of hardware ports.
I will probably send nedko a patch for that (and for switching off the debug)
this weekend. ;-)
Very handy tool, when you use the firewire-backends...
Arnold
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a "rm -rf /". Or ask your
administrator to do so...
> 2.
is true for older jack, however newer versions and the 0.109
> release also support jack midi where the big difference is, as far as
> I understand it, that jack midi has the same time source as jack
> audio, whereas alsa midi and jack audio have different time sources.
Oh, ok,
to it's the time source. I'm guessing it would be better to for
applications to use the native jack midi that way the transport and MMC
time can be in sync. I wonder if there are timing issues when using
a2jmidid, or if it's better to use the -X seq option as suggested.
Oh well, it's time to experiment a bit.
6183
days inactive
6185
days old
linux-audio-user@lists.linuxaudio.org
6 comments
6 participants
participants (6)
-
Arnold Krille -
hollunder＠gmx.at -
jeremaja niko -
Lars Luthman -
Miguel M -
Nedko Arnaudov