X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fnewopen-session-dialog.html;h=e62ec7e2a08a4865e57387dad1c9491467c867ed;hb=ca8c53473dfbcb7d4b483a5ce792bbf4b5caffe8;hp=3e442e0ab6db36af6447e940fa5c4f8da22a22a2;hpb=f09800ba11cbbae5bcfe1c3d15d190c7f9850b1e;p=ardour-manual diff --git a/include/newopen-session-dialog.html b/include/newopen-session-dialog.html index 3e442e0..e62ec7e 100644 --- a/include/newopen-session-dialog.html +++ b/include/newopen-session-dialog.html @@ -1,51 +1,75 @@

- The initial Session dialog consists of several consecutive pages: + The initial Session dialog, displayed at each start of Ardour, consists + of several consecutive pages:

Open Session Page

+ +
+ The Session Setup Dialog +
+ The Session Setup Dialog +
+
+ +

+ On this page, an existing session can be opened. Any snapshot + of a particular session can also be accessed by clicking on the arrow next to + the session name to display all snapshots, and then selecting one. + +

+

+ If the session is not displayed in the Recent Sessions list, the Other Sessions button will bring up a file selection dialog + to navigate the file system. +

- On this page, you can open an existing session. You can also - open any snapshot of a - particular session by clicking on the arrow next to the session name to - display all snapshots, and then selecting one. If your session is - not displayed in the Recent Sessions list, the Other - Sessions button will bring up a file selection dialog to navigate - your hard drive.
- Alternatively, you can opt to create a New - Session. + Alternatively, a New Session can be created.

-

New Session page

+

New Session page

+ +
+ The New Session Dialog +
+ The New Session Dialog +
+
+

- Here you can type in the name of a session, select a folder to save in, and + This page allows to type in the name of a session, select a folder to save it in, and optionally use an existing template.

- Under Advanced Options, you can select whether you wish to create - a Master Bus, or a Control Bus, and how many channels you wish either to have. - You can also decide whether you want Ardour to automatically connect all inputs - to the physical ports of your hardware. Ardour will do so + Under Advanced Options, some fine tuning can be done, like selecting + whether Ardour should create a Master Bus, or a Control Bus, and how many channels + the output should have. +

+

+ Other options also decide whether Ardour should automatically connect all inputs + to the hardware's physical ports. Ardour will do so sequentially and in round-robin fashion, connecting the first track's - input to the first input of your hardware and so on. When Ardour has used + input to the first input of the hardware and so on. When Ardour has used all available hardware inputs, it will begin again with the first physical input. - You can limit the number of channels on your physical hardware that Ardour - uses. +

+

+ The number of hardware channels used by Ardour can also be limited.

By default Ardour will connect all tracks and busses to the Master Bus if - there is one. However you can also tell it to automatically connect each - output to the physical outputs of your interface or sound card, and limit + there is one. However, it can also be told to automatically connect each + output to the physical outputs of the interface or sound card, and limit the number of physical outputs used, as above.

-

Audio/MIDI Setup

+

Audio/MIDI Setup

-
- The Audio+MIDI Setup Dialog +
+ The Audio/MIDI Setup Dialog
- The Audio+MIDI Setup Dialog + The Audio/MIDI Setup Dialog
@@ -54,58 +78,57 @@ current work session, for hardware and software and is made of:

-
-
Audio System
-
Depending on the operating system, Ardour can possibly use different audio + + + + + + + + + + + + + + + + + + + +
Audio SystemDepending on the operating system, Ardour can possibly use different audio systems, e.g. on Linux, both ALSA and JACK are available. - -
Driver
-
+
Driver On Mac OS X this will typically be CoreAudio. On Linux usually this will be either FFADO or ALSA, depending on whether or not you are - utilizing a firewire device. Advanced users on all platforms may also + Architecture">ALSA, depending on whether or not a firewire device + is used. Advanced users on all platforms may also use NetJack which provides network audio I/O. - -
Device
-
The selector should show all availiable interfaces provided by the +
DeviceThe selector should show all availiable interfaces provided by the driver above and which are capable of duplex operation.

- If you are using an Intel Mac running OS X and the builtin audio - interface, you must - first merge - its separate input and output devices into a single "aggregate - device" before Ardour will be able to use it. + When using an Intel Mac running OS X and the builtin audio + interface, its separate input and output devices must be + merged first into a single "aggregate device" before Ardour will be able + to use it.

- -
Sample Rate
-
- The selector will allow you to select from any sample rate - supported by the device selected above it. -
-
Buffer Size
-
- You can adjust the size of the buffer used by your audio interface +
Sample Rate + The selector will allow to select from any sample rate supported by the device + selected above it. +
Buffer Size + The size of the buffer used by the audio interface can be adjusted to allow for either lower latency, or lower CPU usage and higher latency. - -
Input/Output Channels
-
- Here you can specify the number of hardware channels to use. The - default is all available channels.
-
Hardware Input/Output Latency
-
Specify the hardware delay in samples for precise latency compensation.
-
Calibrate
-
- This button guides you through a semi-automated process to obtain - precise hardware latency measurements for the above option.
-
MIDI System
-
- Select the MIDI driver to use. On Mac OS X, this will be CoreMIDI. On Linux, you can change between two legacy - ALSA drivers or the (preferred) new JACK+ALSA implementation.
- +
Input/Output Channels + Specifies the number of hardware channels to use. The + default is all available channels.
Hardware Input/Output LatencySpecify the hardware delay in samples for precise latency compensation.
Calibrate + This button runs a semi-automated guided process to obtain + precise hardware latency measurements for the above option.
MIDI System + Selects the MIDI driver to use. On Mac OS X, this will be CoreMIDI. On Linux, it can be changed between two legacy + ALSA drivers or the (preferred) new JACK+ALSA implementation.