On Thu, 25 Sep 2014 18:17:56 -0400
Paul Davis <paul(a)linuxaudiosystems.com> wrote:
On Thu, Sep 25, 2014 at 4:56 PM, Philipp Überbacher
<murks(a)tuxfamily.org> wrote:
on as far as timing.
So I remember correctly that there used to be issues with -X seq.
the -X seq option in current JACK1 is just a backward compatible hack
to allow qjackctl and other tools to invoke the relevant stuff.
the actual implementation is nothing to do with the old -X seq code,
and is actually a2jmidid converted into an internal client. Note that
JACK2 could use this client too - its source code is even in the
theoretically "shared" git repo for JACK tools.
Is there a new, recommended way to do the same thing? I only found -X
alsa_midi in the man page but it does not have the same effect.
Why isn't jack2 using the same client? It seems more convenient to just
use jack with -X seq rather than running another program.
Regards,
Philipp