Re: [LAD] [PATCH] jack dbus and logs improvement

From: Rui Nuno Capela <rncbc@email-addr-hidden>
Date: Mon Dec 10 2007 - 20:46:01 EET

Nedko Arnaudov wrote:
> Dave Robillard <dave@email-addr-hidden> 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?

eh... right, now that qjackctl is having a free ride on windows we can
put it back where it belongs :)

this d-bus interface seems a good idea nevertheless, and now that kde4
is almost on the brink, it sounds logical to push it as duct tape for
phonon and jack, eh?

cheers

-- 
rncbc aka Rui Nuno Capela
rncbc@email-addr-hidden
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Tue Dec 11 00:15:01 2007

This archive was generated by hypermail 2.1.8 : Tue Dec 11 2007 - 00:15:01 EET