Re: Question

On Thu, Jun 4, 2015 at 4:05 PM, Fons Adriaensen <[email protected]> wrote:

> On Thu, Jun 04, 2015 at 07:08:50PM +0200, Robin Gareus wrote:
>
> > The current policy regarding the setup dialog on application start in
> > 4.0 is as follows: If jackd is already running and jack was the most
> > recently used backend, no dialog is displayed. Ardour silently joins the
> > jack session.
> > In all other cases the setup dialog is displayed when Ardour4 starts.
>
> So that measn that a dialog will be presented when Jack is already
> running, it was not the last backend used, but the user selects Jack
> for the current session.


The user has no way to select anything without the dialog. The dialog is
HOW the user makes the choice.

If JACK is not running, then the user has a clear choice: start+use JACK,
or use the ALSA backend. Thus: show dialog.

If JACK is running, then the user might intend to just use it, or might be
planning to use a different device via the ALSA backend.

Our way to resolve those two choices is to check if they used JACK last
time. If so, just connect to JACK. If not, offer the choice to connect to
JACK or use the ALSA backend.

If JACK is running and it was used last time, but the user still didn't
intend to use JACK, they can just popup the audio/MIDI dialog and change
backends on the fly.

--p

_______________________________________________
ardour-dev mailing list
[email protected]
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org