27 Oct
2007
27 Oct
'07
6:44 p.m.
Ken Restivo <ken(a)restivo.org> writes:
On Sat, Oct 27,
2007 at 10:23:23PM +0300, Nedko Arnaudov wrote:
I never used jackdmp, so I really have no idea.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Ken Restivo <ken(a)restivo.org> writes:
Thanks.
Will it also work with jackdmp?
I have been procrastinating trying out jackdmp because JACK MIDI
hasn't been merged in to it yet, but if this will bridge that gap for
me, I'll try it out. On Sat, Oct 27, 2007 at 04:40:59PM +0300, Nedko
Arnaudov wrote:
> a2jmidid is daemon for exposing legacy ALSA sequencer
> applications in JACK MIDI system. It is based on
> jack-alsamidi-0.5 (jackd alsa seq midi backend) by Dmitry
> Baikov. The main purpose is to ease usage of legacy, not
> JACK-ified apps, in JACK MIDI enabled systems.
[snip]
Now, just to make sure I understand: this is for
people who are
using released versions of jackd that *do* suppport JACK MIDI (i.e
0.103.0), but aren't using the lastest jackd from SVN which has
suport for the -X option to do this functionality within jackd,
correct?
It will help them, but not with hardware ALSA seq MIDI ports,
because currently a2jmidid ignores them. This can be fixed easily in
code until a2jmidid gets more configurable.
Once there's a new jackd release, with the -X
option, will this
too be needed anymore?
It will still be needed for users that want using raw ALSA
MIDI
backend (and skipping additional ALSA sequencer layer). This is
setup I have here, I use -X raw but I still need connecting legacy
ALSA MIDI apps to JACK MIDI apps.
Althrough not intentional, it may help for JACK drivers that don't
support JACK MIDI nativily yet. IIRC JACK MIDI ffado driver support
is not ready yet.