[LAD] [PATCH] jack dbus and logs improvement

Nedko Arnaudov nedko at arnaudov.name
Mon Dec 10 18:18:38 UTC 2007


Dave Robillard <dave at drobilla.net> writes:

> On Sun, 2007-12-09 at 22:35 +0200, Nedko Arnaudov wrote:
>> Attached are two patches:
>>  * The logs patch replaces various calls to fprintf(),printf() and
>>    fputs() with calls to jack_error() and newly appeared jack_info()
>>    functionality. It also fixes some obvious error/info log mismatches
>>    in current code.
>
> I proposed this ages ago and Paul called it 'bloat' :)

logs patch has taken some direct directions from Paul that I followed
with fate that this will ease its way to jack trunk (pre 1.0).

Paul and others in charge, what you think?

>> Multiconfig functionality is provided by separate object to be reused by
>> control apps like patchage and qjackctl.
>
> I don't understand what this means in concrete terms.  Simple example?

Apps like patchage and qjackctl access the multiconfig object with
interface (quick draft):
 * get_presets() - return available presets names
 * new_preset() - add new preset
 * remove_preset() - remove existing preset
 * set/get of preset settings: engine options, selected driver, driver
   options of selected driver

That object will presist its settings in XML configuration file. I've
made example one available here:

http://nedko.arnaudov.name/soft/jack/jack.xml

or here:

http://triton.atia.com/nedko/soft/jack/jack.xml

This file is not acessed by control apps directly. Object methods are
used instead (see above).

Also either autosave mode (settings persistence) and manual save may be
viable. What will get implemented will probably be shaped by people in
charge of existing control apps (qjackctl,patchage). So put your
opinions please.

>> All of them will reuse jack
>> presets and user will get transparent workflow.
>> If they adapt it. Dave, Rui?
>
> Hm.. if the connection and new client/port callbacks are mapped to dbus
> messages (jack-dbus -> client) it would be possible to implement things
> like qjackctl/patchage/lash without a dependency on libjack at all.
> Nice...

This is the plan. We will need that for lash on dbus too (I want lash
to control jack server not vice versa). libjack interface is still
available as alternative method (dbus is not available on MacOSX by
default).

Speaking of MacOSX, I saw that there is fink package for D-Bus. It may
be worth for someone with Tiger/Leopard JACK audio setup to check how
well fink dbus package works with jackdbus.

-- 
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-dev/attachments/20071210/91fe68db/attachment.pgp>


More information about the Linux-audio-dev mailing list