[LAU] Bridging alsa and jack midi

[Harry van Haaren]

On Fri, Sep 26, 2014 at 6:32 PM, Will Godfrey
<willgodfrey at musically.me.uk> wrote:
> I confess I'm getting *more* confused about all of this :(
I won't claim to understand the whole eco-system: just enough to
suffice for my needs.

> I use up to 3 hardware MIDI ports for my compositions along with Rosegarden
> (which is ALSA MIDI only). Up to now I've been getting along quite well with
> this, as all the other software I use can work with ALSA.
My experience of a2jmidid (or indeed the -X switch on modern Jack1) is
flawless: I no longer worry about what type of port MIDI ports are: be
they ALSA hardware MIDI, FFADO MIDI, or "virtual" JACK MIDI, they can
all be connected to eachother. That's a +1 for UX IMO.

> While I fully appreciate the issues around supporting both forms I'm getting a
> bit concerned by the push towards a JACK only system.
>From a techie-POV, Jack audio & MIDI is sample accurate: it stays in
sync, and no matter how often its bounced between programs, the events
will stay true in timing. The same can not be said for ALSA MIDI,
which involves processing from a different thread, buffering, etc.

That's my experience with JACK MIDI, -Harry

-- 

www.openavproductions.com