From: Ed Ward Date: Tue, 10 Jan 2017 09:11:27 +0000 (+0100) Subject: Updating *Starting Ardour* X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bb400ffa627fb979b9530c775491f850354e6728;p=ardour-manual Updating *Starting Ardour* --- diff --git a/_manual/04_ardours-interface/01_starting-ardour.html b/_manual/04_ardours-interface/01_starting-ardour.html index e610c2c..3beb5ed 100644 --- a/_manual/04_ardours-interface/01_starting-ardour.html +++ b/_manual/04_ardours-interface/01_starting-ardour.html @@ -22,19 +22,15 @@ title: Starting Ardour Edit > Preferences dialog.

- In general, it is sensible to start JACK before you run Ardour. This is not - necessary, but will provide you with more control and options over JACK's - operation. + If you want to use JACK, in general, it is sensible to start it before you run Ardour. This is not + necessary, but will provide you with more control and options over JACK's operation. + You can start JACK through its CLI, or using a GUI + program, like QjackCtl or Cadence.

If you open Ardour without specifying an existing session it will display - the Session > New... dialog. If JACK is not already - running, there will be an extra Audio Engine tab in - that dialog to configure JACK, which Ardour will then start automatically. -

-

- If you did specify an existing session but JACK is not already running, the - New Session dialog will contain just the Audio Engine tab. + the Session > New... dialog and the Audio/MIDI Setup dialog. + See New/Open Session Dialog for a description of those dialogs.

diff --git a/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html b/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html index eb18620..b8d5d56 100644 --- a/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html +++ b/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html @@ -4,17 +4,15 @@ title: Starting Ardour From the Command Line (Linux) menu_title: Starting from Linux Cmdline --- - -

Like (almost) any other program on Linux, Ardour can be started on the command line. Type the following command in a terminal window:

-ardour3 +Ardour5

To start Ardour with an existing session:

-ardour3 /path/to/session +Ardour5 /path/to/session

replacing /path/to/session with the actual path to your session. You can specify either the session folder or any session file inside the folder, @@ -23,6 +21,6 @@ menu_title: Starting from Linux Cmdline

To start Ardour with a new, named session:

-ardour3 -N /path/to/session +Ardour5 -N /path/to/session

Other Command Line Options

diff --git a/_manual/10_working-with-tracks/02_busses-and-vcas.html b/_manual/10_working-with-tracks/02_busses-and-vcas.html index 0c27d58..8bd2370 100644 --- a/_manual/10_working-with-tracks/02_busses-and-vcas.html +++ b/_manual/10_working-with-tracks/02_busses-and-vcas.html @@ -4,7 +4,7 @@ title: Busses and VCAs ---

- In order to use the process of mixing, Ardour offers two tools traditionally found on hardware mixing consoles : Busses and VCAs. + In order to ease the process of mixing, Ardour offers two tools traditionally found on hardware mixing consoles : Busses and VCAs.

Busses

@@ -30,7 +30,7 @@ title: Busses and VCAs

- MIDI bus are provide a particularly efficient workflow for virtual drumkits where the arrangement uses different MIDI tracks. Moreover, busses with both Audio and MIDI inputs are well suited for vocoders and similar plugins. + MIDI busses provide a particularly efficient workflow for virtual drumkits where the arrangement uses different MIDI tracks. Moreover, busses with both Audio and MIDI inputs are well suited for vocoders and similar plugins.

@@ -46,7 +46,7 @@ title: Busses and VCAs

- Obviously, doing so will (by default) disconnect the output from the Master's input, which means all the audio/MIDI will be routed to the bus. For more complex routing, the OUTPUT button allows to show the Routing Grid that allows to plug the output of the track to multiple outputs at once, be it busses, tracks, Master... The button will then reflect these multiple connections by showing a *number*, number being the number of connections made in the routing grid. + Obviously, doing so will (by default) disconnect the output from the Master's input, which means all the audio/MIDI will be routed to the bus. For more complex routing, the OUTPUT button allows to show the Routing Grid that allows to plug the output of the track to multiple outputs at once, be it busses, tracks, Master... The button will then reflect these multiple connections by showing a *number*, number being the number of connections made in the routing grid.

Connecting a track to a bus via Sends