[Jack-Devel] Client-Server models are just fine. Please?

[tom at trellis.ch]

On Mon, February 1, 2016 18:12, Paul Davis wrote:
> On Mon, Feb 1, 2016 at 12:01 PM, <tom at trellis.ch> wrote:
>
>
>> On Mon, February 1, 2016 17:47, Paul Davis wrote:
>>
>>
>>> it is just amazing to me, given all the other useful things that JACK
>>>  could be made to do, that anyone is talking about the mechanics of
>>> starting it.
>>
>> apropos startup: can a client today start up a dummy server with given
>> properties? for a temporary non-default/private ecosystem i.e. for
>> freewheeling without interrupting the default jack that is possibly
>> attached to the hardware.
>>
>
> Configuring a given JACK server is always a potentially complex
> operation, given the number of possible parameters for both the server and
> the backend.
>
> Any client can start a server with any parameters. But for that to be
> useful to the user, it probably has to present the options to the user and
>  gather their choices; That isn't trivial, which is partly why almost no
> clients bother to even try this (Ardour is one of the few non-control
> applications that does, and even it imposes drastic limitations on
> options the user can select from).
>

to put in other words i wondered if a client can ask to "autostart" a
temporary dummy server with only a few arguments easily code-wise
(assuming *any* jack has a dummy backend built-in) instead of relying on
the ~/.jackrc file.
the other non-dummy cases are more dialogue-demanding, no question.