[Ardour-Users] latest changes to 2.0-ongoing

[Paul Davis]

I have just committed some fairly significant changes to the way Ardour
starts up. Ardour now has its own JACK control panel. If you start
Ardour with JACK already running, this control panel will not be
accessible or visible, and everything is intended to work as it always
has. Ardour assumes that you know what you are doing, and that JACK is
running under the control of some other app (e.g. qjackctl or the
shell).

However, if you start Ardour without JACK running, the session control
dialog that shows up initially will include a new tab called "Audio
Setup". It is intended to offer the same (or better) control over JACK
as Rui's fine qjackctl does. It does not (currently) offer any status
information of any kind (running/stopped, transport state, xruns etc
etc).

Work on this is still ongoing - for example, the Audio Setup stuff does
not save its state at present, so each time you start Ardour you will
get the "default" set up. If anyone tries it out and finds obvious
problems with the way I've changed the startup logic, please let me know
ASAP. There are definitely some logic issues surrounding what the "Open"
button in the session control dialog does, for example, but once you get
it to do what you intended, things should be entirely normal.

There is also a new -m flag to ardour to select menu files at run time.
The new file "ardour-sae.menus" contains an early version of what the
SAE menus might look like. You can also set ARDOUR_SAE in your
environment to pick up a series of about-to-get-a-lot-more-obvious
changes being done for the SAE "version" of Ardour.

--p