10 Nov
2008
10 Nov
'08
12:46 p.m.
On Mon, 2008-11-10 at 10:08 -0600, Jack O'Quin wrote:
On Mon, Nov 10, 2008 at 9:28 AM, Stéphane Letz
<letz(a)grame.fr> wrote:
agreed. and it may be easier to remain that way if users want easy
control over MMC ID and a few other parameters related to MMC handling.
however the appeal of using some "parameter setting protocol" to set
this in a client that is otherwise invisible is fairly apparent.
--p
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).
Stephane has a good point.
But, implementing it as an external client probably makes sense right
now. It should be simpler to support both jackd and jackdmp servers
with the same code that way.