On Mon, Nov 24, 2008 at 11:28 AM, Alex Montgomery
<apmontgomery(a)gmail.com> wrote:
I think this kind of tools is a good candidate to
be developed as an "in
server" JACK client. With the dbus based dynamic access of available "in
server" clients installed on a machine, it will be quite easy to load/unload
this kind of tool when needed (Netjack2 uses this model of "in server"
clients).
Ok, so Nedko and I got a release out that supports goto/locate MMC messages
and command-line parameters. We're going to switch it over to using JACK
midi instead of ALSA midi next. Should we start thinking about making this
an "in server" client now? Could someone familiar with this stuff comment on
this?
I recommend making it a normal external client. That will be easier
to code and test, and easier to make work with both jack1 and jack2
servers.
--
joq