ardour
/
manual
13
0
Fork 0
Code Pull Requests Releases Activity

copy-editing chapter 7.

This commit is contained in:
Jörn Nettingsmeier 2014-02-05 01:17:18 +01:00
parent 2e006d9b93
commit 5432a9fe7d
16 changed files with 347 additions and 220 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
STYLE_GUIDE
View File

@ -175,8 +175,9 @@ elements</q>.
------------------------------------
<kbd>
Any keys or key combinations, mouse buttons, or controllers should be marked
with this element.
Any keys or key combinations, mouse buttons or controllers, menu items or
textual user input should be marked with this element. It is used here in
the widest possible sense, qualified by classes.
E.g.:
"Press <kbd>F</kbd> to fit all tracks to the height of the Editor window."
"Move <kbd>Fader 1</kbd> on your MIDI controller to bind it.

2
_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html
View File

@ -10,7 +10,7 @@ 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:
</p>
<kbd class="cmd lin">ardour3</kbd>>
<kbd class="cmd lin">ardour3</kbd>
<p>
To start Ardour with an existing session:
</p>

3
_manual/04_ardours-interface/02_basic-gui-operations/04_tooltips.html
View File

@ -5,7 +5,8 @@ title: Tooltips
<p>
By default, Ardour will show helpful <dfn>tooltips</dfn> about
the purpose and use of each GUI element if you position the pointer
the purpose and use of each <abbr title="Graphical User
Interface">GUI</abbr> element if you position the pointer
over it and hover there for a short while.
These little pop-up messages can be a good way to discover the
purpose of many aspects of the GUI.

22
_manual/04_ardours-interface/02_basic-gui-operations/06_using-the-mouse.html
View File

@ -6,9 +6,7 @@ title: Using the Mouse
<h2>Clicking</h2>
<p>
Throughout this manual, the term <dfn>click</dfn> refers to the act of pressing
and releasing the leftmost mouse button (technically identified as
<kbd class="mouse">Button1</kbd>, but your operating system may allow
this to be reassigned). This action is used to select objects, activate
and releasing the <kbd class="mouse">Left</kbd> mouse button. This action is used to select objects, activate
buttons, turn choices on and off, pop up menus and so forth.<br />
On touch surfaces, it also corresponds to a single, one-finger tap on
the GUI.
@ -17,28 +15,34 @@ title: Using the Mouse
<h2>Right Clicking</h2>
<p>
The term <dfn>right-click</dfn> refers to the act of pressing and releasing
the rightmost mouse button (internally called <kbd class="mouse">Button2</kbd>,
but again your operating system may allow this to be reassigned).
the <kbd class="mouse">Right</kbd> mouse button.
This action is used to pop up <dfn>context menus</dfn> (hence the term
"context click", which you will also see). It is also used by default in
combination with the shift key to delete objects within the editor
window.
</p>
<p class="note mac">
Mac OS mice sometimes have only one button. On Mac OS if you press and hold
the Control key this is equivalent to right-clicking.
Some mice designed for use with Mac OS X may have only one button. By
convention, pressing and holding the Control key while clicking is
interpreted as a right-click by many application..
</p>
<h2>Middle Clicking</h2>
<p>
A <dfn>middle-click</dfn> refers to the act of pressing and releasing the
middle mouse button (<kbd class="mouse">Button3</kbd>, which may also be
reassigned). Not all all mice have a middle click button
<kbd class="mouse">Middle</kbd> mouse button. Not all all mice have a middle click button
(see the <a href="/setting-up-your-system/mouse/">Mouse</a> chapter for
details). Sometimes the scroll wheel acts as a clickable middle button.
This action is used for time-constrained region copying and mapping MIDI
bindings.
</p>
<p class="note">
Internally, your operating system may identify the mouse buttons as
<kbd class="mouse">Button1</kbd>, <kbd class="mouse">Button2</kbd>, and
<kbd class="mouse">Button3</kbd>, respectively. It may be possible to
invert the order of buttons to accommodate left-handed users, or to re-assign
them arbitrarily. This manual assumes the canonical order.
</p>
<h2>Double Clicking</h2>
<p>

119
_manual/07_working-with-sessions/01_new-session-dialog.html
View File

@ -1,24 +1,115 @@
---
layout: default
title: New Session Dialog
title: New/Open Session Dialog
---
<p>
The initial <dfn>Session</dfn> dialog consists of several consecutive pages:
</p>
<h3>New Session Page</h3>
<p>In this tab you can type in the name of a session, select a folder to save in, and optionally use an existing <a href="/working-with-sessions/session-templates/">template</a>.</p>
<h2>Open Session Page</h2>
<p>
On this page, you can open an <dfn>existing session</dfn>. You can also
open any <a href="/working-with-sessions/snapshots/">snapshot</a> 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 <kbd class="menu">Other
Sessions</kbd> button will bring up a file selection dialog to navigate
your hard drive.<br />
Alternatively, you can opt to create a <kbd class="menu">New
Session</kbd>.
</p>
<h4>Advanced Options</h4>
<p>Under the Advanced Options, you can select specific behaviors that occur by default. This includes settings whether you wish to create a Master Bus, or a Control Bus, and how many channels you wish either to have.</p>
<p> You can also select whether you want Ardour to automatically connect all inputs to the physical ports of your hardware. If you select this Ardour will do so sequentially, to give an example, the first input of a track or bus will be connected to the first input of your hardware. The second input of a track or bus will be automatically connected to the second input of your hardware, and so on. When Ardour reaches the limits of your hardware, it will circle around and begin connecting with the first physical input of your hardware again. You can limit the number of channels on your physical hardware Ardour uses if you desire, and if that is the case, Ardour will only connect that many physical inputs to your tracks. Useful if you only want to connect the first input to do some voice over recording for instance.</p>
<p> Just like you can tell Ardour not to automatically connect track inputs, you can also modify how it automatically connects the outputs of the track or bus. 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 like inputs can also limit the amount of physical outputs used, so for instance if you only have stereo monitors attached to the first two outputs of your sound card, you would not want Ardour to automatically connect to the next 6 that may be there with nothing attached to them.</p>
<h2>New Session page</h2>
<p>
Here you can type in the name of a session, select a folder to save in, and
optionally use an existing <a href="/working-with-sessions/session-templates/">template</a>.
</p>
<p>
Under <dfn>Advanced Options</dfn>, 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
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
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.
</p>
<p>
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
the number of physical outputs used, as above.
</p>
<h3>Open Session Page</h3>
<p>The Open Session Tab lets you to open an existing session. You can also open any <a href="/working-with-sessions/snapshots/">snapshot</a> of a particular session by clicking on the arrow next to the session name to display all snapshots, and then selecting a snapshot. If a session is not displayed by default in the dialog you can click on the button next to "Browse" in order to bring up a file selection dialog to navigate your hard drive to find the file.</p>
<h3>Audio/MIDI Setup</h3>
<h3>Audio Setup Page</h3>
<p>More details on this dialog/tab can be found below. Note that this tab is not visible if JACK is already running when the New Session dialog is displayed.</p>
<img class="right" src="/images/Audio-MIDI_Setup.png" alt="The Audio+MIDI
Setup Dialog"/>
<p>
This page is not displayed if <abbr title="JACK Audio Connection
Kit">JACK</abbr> is already running when you start
Ardour. It provides a simple interface to configure JACK, which
will then be started by Ardour. For more control and options regarding
JACK, it is recommended that you start JACK before using Ardour, via a
JACK control application such as QJackCtl (sometimes called "Jack
Control"), JackPilot, etc.
</p>
<dl>
<dt>Audio System</dt>
<dd>Currently, the only option here is <kbd class="menu">JACK</kbd>. In the future, native
hardware access may be supported.</dd>
<dt>Driver</dt>
<dd>
On Mac OS X this will typically be <kbd class="menu">CoreAudio</kbd>. On Linux usually
this will be either <kbd class="menu"><abbr title="Free Firewire Audio Driver fOr
linux">FFADO</abbr></kbd>
or <kbd class="menu"><abbr title="Advanced Linux Sound
Architecture">ALSA</abbr></kbd>, depending on whether or not you are
utilizing a firewire device. Advanced users on all platforms may also
use <kbd class="menu">NetJack</kbd> which provides network audio I/O.
</dd>
<dt>Device</dt>
<dd>The selector should show all availiable interfaces provided by the
driver above and which are capable of duplex operation.
<p class="warning">
If you are using an Intel Mac
running OS X and the builtin audio interface, you must
first <a href="setting-up-your-system/us
ing_more_than_one_audio_device/">merge its separate input and
output devices into a single "aggregate device"</a> before
Ardour will be able to use it.
<p>
</dd>
<dt>Sample Rate</dt>
<dd>
The selector will allow you to select from any sample rate
supported by the device selected above it.
</dd>
<dt>Buffer Size</dt>
<dd>
You can adjust the size of the buffer used by your audio interface
to allow for either lower latency, or lower CPU usage and higher
latency.
</dd>
<dt>Input/Output Channels</dt>
<dd>
Here you can specify the number of hardware channels to use. The
default is <kbd class="menu">all available channels</kbd>.</dd>
<dt>Hardware Input/Output Latency</dt>
<dd>Specify the hardware delay in samples for precise latency compensation.</dd>
<dt>Calibrate</dt>
<dd>
This button guides you through a semi-automated process to obtain
precise hardware latency measurements for the above option.</dd>
<dt>MIDI System</dt>
<dd>
Select the MIDI driver to use. On Mac OS X, this will be <kbd
class="menu">CoreMIDI</kbd>. On Linux, you can change between two legacy
ALSA drivers or the (preferred) new JACK+ALSA implementation.</dd>
</dl>
{% children %}

82
_manual/07_working-with-sessions/01_the-new-session-dialog/01_audio-setup.html
View File

@ -1,82 +0,0 @@
---
layout: default
title: Audio Setup
---
<p>
This is a tabbed-dialog within the New Session dialog that will
appear only if JACK is <strong>not</strong> already running as you
start Ardour. It provides a simple interface to configure JACK, which
will then be started by Ardour. For more control and options regarding
JACK, it is recommended that you start JACK before using Ardour, via a
JACK control application such as qjackctl (sometimes called "Jack
Control"), JackPilot, etc.
</p>
<h3>Device Tab</h3>
<p> On this tab you can tell Ardour about the device it should use.
The driver setting will tell it what driver to attempt to
access.
</p>
<dl class="wide-table">
<dt>Driver</dt>
<dd>
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
use NetJack which provides network audio I/O
</dd>
<dt>Interface</dt>
<dd>The selector should show all availiable interfaces that driver
provides that are duplex capable for Ardour to
use. <strong>Important</strong> if you are using an Intel Mac
running OS X and the builtin audio interface, you must
first <a href="setting-up-your-system/us
ing_more_than_one_audio_device/">merge its separate input and
output devices into a single "aggregate device"</a> before
Ardour will be able to use it.
</dd>
<dt>Sample Rate</dt>
<dd>
The selector will allow you to select from any sample rate
supported by the device selected above it.
</dd>
<dt>Buffer Size</dt>
<dd>
You can adjust the size of the buffer used by your audio interface
to allow for either lower latency, or lower CPU usage and higher
latency.
</dd>
</dl>
<h3>Options Tab</h3>
<p>
This tab has a few options that should be rarely used by most
users. The Realtime Option allows Jack to run with Realtime
privileges, which allows for smoother audio. The Verbose Output
checkbox is primarily used for troubleshooting, it will cause Jack to
use verbose messaging and output it to the console. The client
timeout will help prevent clients from disconnecting from Jack if they
don't respond to Jack fast enough. The number of ports changes the
total number of ports that Jack will provide to all clients. And the
server dropdown will allow you to change the path to the Jack
executable to match where it is installed on your system.
</p>
<h3>Advanced Tab</h3>
<p>
The Advanced tab lets you to set some advanced settings that
are rarely needed. By default the input and output channels will
automatically try to give you the amount of inputs and outputs as
requested by the software, however some software doesn't always
request as many as you need. This option provides more channels to software that can handle it.
</p>
{% children %}

57
_manual/07_working-with-sessions/02_whats-in-a-session.html
View File

@ -2,33 +2,38 @@
layout: default
title: What's in a Session?
---
<p>The Session is the fundamental document type that is created and modified by the Ardour workstation. A "Session" is a folder on your computer filesystem that contains all the items that pertain to a particular project or "recording/editing/mixing session".</p>
<p>The Session folder includes these files and folders:</p>
<p>
The <dfn>Session</dfn> is the fundamental document type that is created and
modified by the Ardour workstation. A Session is a folder on your computer
filesystem that contains all the items that pertain to a particular project
or "recording/editing/mixing session".
</p>
<p>
The Session folder includes these files and folders:
</p>
<ul>
<li> The main session snapshot (session_name.ardour)
</li>
<li> Any additional snapshots (filenames ending in .ardour)
</li>
<li> the auto-backup snapshot (session_name.ardour.bak)
</li>
<li> the undo history for the session (session_name.history)
</li>
<li> the instant file (instant.xml) which records the last-used zoom scale and other metadata
</li>
<li> a folder called "interchange" which holds your raw audio and MIDI files (whether imported or recorded)
</li>
<li> a folder called "export" which contains any files created by the "Export" function
</li>
<li> a folder called "peaks" which contains a waveform rendering of each raw audio file in the session
</li>
<li> a folder called "analysis" which contains transient and pitch information of each raw audio file
</li>
<li> a folder called "dead sounds" which contains sounds which Ardour has detected are no longer used in the session
</li>
<li><code><em>session_name</em>.ardour</code> the main session snapshot</li>
<li><code>*.ardour</code>, any additional snapshots </li>
<li><code><em>session_name</em>.ardour.bak</code>, the auto-backup snapshot</li>
<li><code><em>session_name</em>.history</code>, the undo history for the session </li>
<li><code>instant.xml</code>, which records the last-used zoom scale and other metadata</li>
<li><code>interchange/</code>, a folder which holds your raw audio and MIDI
files (whether imported or recorded)</li>
<li><code>export/</code>, a folder which contains any files created by the
<kbd class="menu">Session &gt; Export</kbd> function</li>
<li><code>peaks/</code>, a folder which contains waveform renderings of
all audio files in the session</li>
<li><code>analysis/</code>, a folder which contains transient and pitch
information of each audio file that has been analysed</li>
<li><code>dead sounds/</code>, a folder which contains sound files which
Ardour has detected are no longer used in the session (during a <kbd
class="menu">Session &gt; Clean-up &gt; Clean-up Unused Sources</kbd>
operation, will be purged by <kbd class="menu">Flush Waste Basket</kbd>)</li>
</ul>
<p>A session combines some setup information (such as audio and MIDI routing, musical tempo &amp; meter, timecode synchronization, etc.) with one or more Tracks and Buses, and all the Regions and Plug-Ins they contain.</p>
<p>
A session combines some setup information (such as audio and MIDI routing,
musical tempo &amp; meter, timecode synchronization, etc.) with one or more
Tracks and Buses, and all the Regions and Plug-Ins they contain.
</p>

21
_manual/07_working-with-sessions/03_where-are-sessions-stored.html
View File

@ -3,10 +3,19 @@ layout: default
title: Where Are Sessions Stored?
---
<p>Sessions are stored in a single folder on your computer's filesystem. </p>
<p>The first time you run Ardour, you will be asked where you would like the default location for sessions to be, with the initial choice being your home folder. </p>
<p>After the first-run dialog, you can still change the default location at any time via <code>Edit &gt; Preferences &gt; Misc &gt; Session Management</code>. You can also specify a particular (different) location for a session when creating it, in the <a href="/working-with-sessions/new-session-dialog/">New Session dialog</a>.</p>
<p>
<dfn>Sessions</dfn> are stored in a single folder on your computer's filesystem.
</p>
<p>
The first time you run Ardour, you will be asked where you would like the
default location for sessions to be, with the initial choice being your
home folder.
</p>
<p>
After the first-run dialog, you can still change the default location at
any time via <kbd class="menu">Edit &gt; Preferences &gt; Misc &gt; Session
Management</kbd>. You can also specify a particular (different) location for
a session when creating it, in the
<a href="/working-with-sessions/new-session-dialog/">New Session dialog</a>.
</p>

29
_manual/07_working-with-sessions/04_backup-and-sharing-of-sessions.html
View File

@ -3,12 +3,25 @@ layout: default
title: Backup and Sharing of Sessions
---
<p>An Ardour session is stored in a single folder on your computer's filesystem. This makes backup very easy - any tool capable of backing up a folder (i.e. all of them) can be used to backup a session. You pick the location of a session when it is created - by default it will be in your default session location, which can be altered via <code>Edit &gt; Preferences &gt; Misc &gt; Session Management</code>. </p>
<blockquote><p>
There is complication: a session may reference embedded media that are stored outside of the session folder. At this time (December 2012), there is no particularly good solution for this. Backing up a session with embedded files will not create a copy of the session containing those files.
</p></blockquote>
<p>The single folder approach also makes sharing a project easy. Simply copy the session folder (onto a storage device, or across a network) and another Ardour user (on any platform) will be able to use it. The limitation regarding embedded files applies to session sharing as well.</p>
<p>
An Ardour session is stored in a single folder on your computer's filesystem.
This makes <dfn>backup</dfn> very easy &mdash; any tool capable of backing up
a folder can be used to backup a session. You pick the location of a session
when it is created &mdash; by default it will be in your default session location,
which can be altered via <kbd class="menu">Edit &gt; Preferences &gt; Misc &gt; Session
Management</kbd>.
</p>
<p class="warning">
There is one complication: a session may reference media files that are stored
outside of the session folder, if the user has opted not to select <kbd
class="optoff">Session &gt; Import &gt; Copy to Session</kbd> during
import. Backing up a session with embedded files will not create a
copy of the session containing those files.
</p>
<p>
The single folder approach also makes sharing a project easy. Simply copy the session
folder (onto a storage device, or across a network) and another Ardour user (on any
platform) will be able to use it. The limitation regarding embedded files applies to
session sharing as well.
</p>

37
_manual/07_working-with-sessions/05_interchange-with-other-daws.html
View File

@ -2,33 +2,34 @@
layout: default
title: Interchange with other DAWs
---
<p>It has never been particularly easy to move sessions/projects created on one DAW to another. There are two "standards" that exist that have reasonably widespread support:</p>
<p>
It has never been particularly easy to move sessions or projects from one
<abbr title="Digital Audio Workstation">DAW</abbr> to another. There are two
<dfn>interchange standards</dfn> that have reasonably widespread support:</p>
<ul>
<li>OMF (Open Media Framwwork), also known as OMFI. Developed and controlled by Avid, never standardized</li>
<li>AAF (Advanced Authoring Format). Developed by a consortium of media-related corporations.</li>
<li>OMF (Open Media Framwwork), also known as OMFI. Developed and controlled
by Avid, never standardized</li>
<li>AAF (Advanced Authoring Format). Developed by a consortium of media-related
corporations.</li>
</ul>
<p>but in practice both of these "standards" have such complex and/or incomplete specifications that different DAWs support them partially, differently or not at all. </p>
<h3>Moving an Ardour session to another DAW</h3>
<p
In practice both of these standards have such complex and/or incomplete
specifications that different DAWs support them only partially,
differently, or not at all.
</p>
<h2>Moving an Ardour session to another DAW</h2>
<p>To move an Ardour session to another DAW, you have 3 basic choices:</p>
<ul>
<li>Stem exports
</li>
<li>Copy the interchange folder
</li>
<li>Use AATranslator
</li>
<li>Stem exports</li>
<li>Copy the interchange folder</li>
<li>Use AATranslator</li>
</ul>
<h3>Moving another DAW session to Ardour</h3>
<p>To move a session from another DAW to Ardour, you have 2 basic choices:</p>
<ul>
<li>Stem exports
</li>
<li>Use AATranslator
</li>
<li>Stem exports</li>
<li>Use AATranslator</li>
</ul>
{% children %}

15
_manual/07_working-with-sessions/05_interchange-with-other-daws/01_copying-the-interchange-folder.html
View File

@ -2,9 +2,16 @@
layout: default
title: Copying The Interchange Folder
---
<p>All media in a session folder is stored in a sub-folder called "interchange". Below that is another folder with the name of the session. You can copy either of these to another location and use the files within them with any other application, importing them all into a project/session. You will lose all information about regions, tracks, and timeline positioning, but all the data that Ardour was working with will be present in the other DAW. Nothing below the "interchange" folder is specific to Ardour - any DAW or other audio/MIDI application should be able to handle the files without any issues.</p>
<p>
All media in a session folder is stored in a sub-folder called
<samp>interchange</samp>. Below that is another folder with the name
of the session. You can copy either of these to another location and
use the files within them with any other application, importing them
all into a project/session. You will lose all information about regions,
tracks, and timeline positioning, but all the data that Ardour was working
with will be present in the other DAW. Nothing below the interchange
folder is specific to Ardour &mdash; any DAW or other audio/MIDI
application should be able to handle the files without any issues.
</p>

12
_manual/07_working-with-sessions/05_interchange-with-other-daws/02_stem-exports.html
View File

@ -2,9 +2,13 @@
layout: default
title: Stem Exports
---
<p>Stem exports are covered fully in the <a href="/exporting">Export</a> chapter. A stem export creates 1 file per track, starting at the beginning of the session. You can then import each track into another DAW and begin working on it. You lose all data except the actual audio/MIDI (no plugins, no automation). This is one of the most common methods of interchange because it works between all DAWs.</p>
<p>
<dfn>Stem exports</dfn> are covered fully in the
<a href="/exporting">Export</a> chapter. A stem export creates one file
per track, starting at the beginning of the session. You can then import
each track into another DAW and begin working on it. You lose all data
except the actual audio/MIDI (no plugins, no automation). This is one of
the most common methods of interchange because it works between all DAWs.
</p>

26
_manual/07_working-with-sessions/05_interchange-with-other-daws/03_using-aatranslator.html
View File

@ -2,12 +2,24 @@
layout: default
title: Using AATranslator
---
<p>
<dfn>AATranslator</dfn> is a Windows
application that can convert sessions/projects from many diffferent DAWs
into other formats. At the present time (December 2012), it can read and
write Ardour 2.X sessions, and can read Ardour 3 sessions.
</p>
<p>
The program runs very well on Linux using
<a href="http://www.winehq.org/">Wine</a> (a Windows environment for Linux).
There are equivalent solutions for running Windows applications on OS X,
but we have no experience with them at this time. Ardour users have reported
great results using AATranslator on Ardour 2.X sessions.</p>
<p>
The <a href="http://www.aatranslator.com.au/">AATranslator website</a>
has full details on supported formats and DAWs. The list includes
ProTools, Live, Reaper, OMF, AAF and many more.
</p>
<img src="/images/No problem.gif" alt="AATranslator Demo Animation"/>
<p><a href="http://www.aatranslator.com.au/">AATranslator</a> is a Windows application that can convert sessions/projects from many diffferent DAWs into other formats. At the present time (December 2012), it can read and write Ardour 2.X sessions, and can read Ardour 3 sessions. </p>
<p>The program runs very well on Linux using <a href="http://www.winehq.org/">Wine</a> (a Windows environment for Linux). There are equivalent solutions for running Windows applications on OS X, but we have no experience with them at this time. Ardour users have reported great results using AATranslator on Ardour 2.X sessions.</p>
<p>The <a href="http://www.aatranslator.com.au/">AATranslator website</a> has full details on which formats/DAWs it supports, but they include ProTools, Live, Reaper, OMF, AAF and many more.</p>
<p><img src="/images/No%20problem.gif" alt="AATranslator Demo Animation"/></p>

22
_manual/07_working-with-sessions/06_renaming-a-session.html
View File

@ -2,11 +2,21 @@
layout: default
title: Renaming a Session
---
<p>
Use <kbd class="menu">Session &gt; Rename</kbd> to give your session a
new name. A dialog will appear to ask you for the new name.
</p>
<p>
This operation does <strong>not</strong> make a new session folder &mdash;
the existing session folder and relevant contents are renamed. If your
session was not saved before a rename operation, it will be saved
automatically and then renaming will continue.
</p>
<p class="warning">
Ardour's <kbd class="menu">Session &gt; Save As</kbd> operation will not
make a new copy of the session folder and its contents. All it does is
create a new session file.
</p>
<p>Use <code>Session &gt; Rename</code> to give your session a new name. A dialog will appear to ask you for the new name.</p>
<p>This operation does <strong>not</strong> make a new session folder - the existing session folder and relevant contents are renamed. If your session was not saved before a rename operation, it will be saved automatically and then renaming will continue.</p>
<blockquote><p>Ardour has no "Save As" operation that actually makes a new copy of the session folder and its contents. </p></blockquote>

43
_manual/07_working-with-sessions/07_session-templates.html
View File

@ -2,23 +2,34 @@
layout: default
title: Session Templates
---
<p>Session templates are a way to store the setup of a session for future use. They do not store any <em>audio</em> data but can store:</p>
<p>
<dfn>Session templates</dfn> are a way to store the setup of a session
for future use. They do not store any <em>audio</em> data but can store:</p>
<ul>
<li>The number of tracks and busses, along with their names
</li>
<li>The plugins present on each track or bus (if any)
</li>
<li>All I/O connections
</li>
<li>The number of tracks and busses, along with their names</li>
<li>The plugins present on each track or bus (if any)</li>
<li>All I/O connections</li>
</ul>
<h3>Creating a Session Template</h3>
<p>Choose <code>Session &gt; Save Template</code>. A dialog will ask you for the name of the new template.</p>
<h3>Using a Session Template</h3>
<p>In the New Session dialog, choose the desired template from the combo selector.</p>
<p>Note that you can also use an existing session as a template, without saving it as one. This is available as an option in the New Session dialog. Doing this will not alter the existing session at all, but will use its track, bus and plugin configuration just like a template.</p>
<p>See also <a href="/missing">Track &amp; Bus templates</a> for information on templates for individual tracks or busses.</p>
<h2>Creating a Session Template</h2>
<p>
Choose <kbd class="menu">Session &gt; Save Template</kbd>. A dialog will ask
you for the name of the new template.
</p>
<h2>Using a Session Template</h2>
<p>
In the New Session dialog, choose the desired template from the combo
selector.
</p>
<p>
Note that you can also use an existing session as a template, without
saving it as one. This is available as an option in the New Session dialog.
Doing this will not alter the existing session at all, but will use its track,
bus and plugin configuration just like a template.
</p>
<p>
See also <a href="/missing">Track &amp; Bus templates</a> for information
on templates for individual tracks or busses.
</p>

72
_manual/07_working-with-sessions/08_snapshots.html
View File

@ -2,21 +2,61 @@
layout: default
title: Snapshots
---
<p>Sometimes you will want to save the current state of a session for possible use in the future. For example, you may be about to change the entire arrangement of a piece, or drastically alter the signal processing, and want a reference to come back to should that not work out.</p>
<p>This is easily accomplished using <code>Session &gt; Snapshot</code>. A small dialog will appear allowing you to enter a name for the snapshot. The default name is based on the current date and time.</p>
<p>Creating a snapshot does <strong>not</strong> modify your session, nor does it save your session. Instead, it saves an "alternate" version of the session, within the session folder. The snapshot shares all data present in the session. You can create any number of snapshots. </p>
<p>After creating a snapshot, you can continue working on the session and save it normally using <code>Session &gt; Save</code> and any existing snapshots will remain unchanged. </p>
<h3>Switching to a Snapshot</h3>
<p>If you are already working on a session and want to to switch to an existing snapshot, navigate the Snapshots tab of the <a href="/ardours-interface/introducing-the-editor-window/editor-lists">Editor Lists</a>. Find the name of the snapshot in the list and click it. Ardour will switch to the snapshot. If the session has not been saved, Ardour will ask what you want to do.</p>
<h3>Starting Ardour With a Snapshot</h3>
<p>Since a snapshot is just another session file stored within the session folder, you can specify that "version" when loading an existing session. The browser in the "Open Session" dialog will show an expander arrow for sessions that have more than 1 session file (i.e. snapshots) present - click on it to see the list, and then click on the name of the snapshot you want to load.</p>
<h3>Saving and Switching to a Snapshot</h3>
<p>Sometimes you want to create a snapshot and then have all future edits and modifications saved to that snapshot rather than the main session. This is easily done using <code>Session &gt; Save As</code>. This does not create a new session folder, but saves your session as a new snapshot and then switches the "current snapshot" to the newly created one. All subsequent saves of the session will be stored in this new snapshot, and existing snapshots (and the main session) will be left unaffected. </p>
<p>
Sometimes you will want to save a <dfn>snapshot</dfn> of the current state of a session for possible
use in the future. For example, you may be about to change the entire
arrangement of a piece, or drastically alter the signal processing, and
want a reference to come back to, should that not work out.
</p>
<p>
This is easily accomplished using <kbd class="menu">Session &gt;
Snapshot</kbd>.
A small dialog will appear, allowing you to enter a name for the snapshot.
The default name is based on the current date and time.<br />
You can create any number of snapshots.
</p>
<p class="warning">
Creating a snapshot does <strong>not</strong> modify your session,
nor does it save your session. Instead, it saves an alternate version
of the session, within the session folder. The snapshot shares all data
present in the session.
</p>
<p>
After creating a snapshot, you can continue working on the session and
save it normally using <kbd class="menu">Session &gt; Save</kbd> and any
existing snapshots will remain unchanged.
</p>
<h2>Switching to a Snapshot</h2>
<p>
If you are already working on a session and want to to switch to an
existing snapshot, navigate the Snapshots tab of the
<a href="/ardours-interface/introducing-the-editor-window/editor-lists">Editor List</a>.
Find the name of the snapshot in the list and click it. Ardour will switch
to the snapshot. If there are unsaved changes in the current session, Ardour will
ask what you want to do.
</p>
<h2>Starting Ardour With a Snapshot</h2>
<p>
Since a snapshot is just another session file stored within the session
folder, you can specify that "version" when loading an existing session.
The browser in the "Open Session" dialog will show an expander arrow for
sessions that have more than 1 session file (i.e. snapshots) present
&mdash; click on it to see the list, and then click on the name of the
snapshot you want to load.
</p>
<h2>Saving and Switching to a Snapshot</h2>
<p>
Sometimes you mey want to create a snapshot and then have all future
edits and modifications saved to that snapshot rather than the main
session. This is easily done using <kbd class="menu">Session &gt; Save
As</kbd>. This does not create a new session folder, but saves your
session as a new snapshot and then switches the "current snapshot"
to the newly created one. All subsequent saves of the session will
be stored in this new snapshot, and existing snapshots (and the main
session) will be left unaffected.
</p>