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

typos from Stuzz on IRC

This commit is contained in:
Paul Davis 2013-02-14 07:30:39 -05:00
parent c59be8cb6d
commit 0535ac9499
4 changed files with 58 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_manual/02_introducing-ardour/01_creating-music-with-ardour.html
View File

@ -32,5 +32,5 @@ title: Creating Music with Ardour
<p>Ardour will allow you to automate changes to any mixing parameters (such as volume, panning, and effects controls) - it will record the changes you make over time, using a mouse or keyboard or some external control device, and can play back those changes later. This is very useful because often the changes you need, even for just one track, will vary in one part of a session compared to another - rather than a single new setting for the volume, you will often need increases followed by decreases (for example, to track the changing volume of a singer). Using automation can make all of this relatively simple.</p>
<h3>Stage 5: Export</h3>
<p>Once you are really satisfied with the arrangement and mix of your session, you will typically want to produce a single audio file that contains a ready-to-listen to version of the work. Ardour will allow you to <em>export</em> audio files in a variety of formats (simultaneously in some cases). This exported file would typically be used in creating a CD, or be the basis for digital distribution of the work.</p>
<p>OI course sometimes you will want to do export material that isn't finished yet, for example to give a copy to someone else to try to mix on their own system. Ardour will allow you to export as much of a session as you want, at any time, in any supported format.</p>
<p>Of course sometimes you will want to do export material that isn't finished yet, for example to give a copy to someone else to try to mix on their own system. Ardour will allow you to export as much of a session as you want, at any time, in any supported format.</p>

10
_manual/02_introducing-ardour/02_understanding-basic-concepts-and-terminology.html
View File

@ -13,19 +13,19 @@ title: Understanding Basic Concepts and Terminology
<p>Ardour's session file is kept in XML format, which is advantageous as it is somewhat human-readable, and human-editable in a crisis. Sound files are stored in one of a number of optional formats, and MIDI files as SMF (standard MIDI format).</p>
<p>It is also possible for Ardour sessions to reference sound and MIDI files outside the session directory.</p>
<p>Ardour has a single current session at all times; if Ardour is started without specifying one, it will offer to load or create one. </p>
<p>More details can be bound at <a href="/working-with-sessions">Working With Sessions</a>.</p>
<p>More details can be found at <a href="/working-with-sessions">Working With Sessions</a>.</p>
<h3>Tracks</h3>
<p> A track is a concept common to most DAWs, and used also in Ardour. Tracks can record audio or MIDI data to disk, and then replay it with processing. They also allow the audio or MIDI data to be edited in a variety of different ways.</p>
<p>In a typical pop production, one might use a track each for the kick drum, another for the snare, more perhaps for the drum overheads and others for bass, guitars and vocals.</p>
<p>Ardour can record to any number of tracks at one time, and then play those tracks back. On playback, a track's recordings may be processed by any number of plugins, panned, and its level altered to achieve a suitable mix.</p>
<p>A track's type is really only related to the type of data that it stores on disk. It is possible, for example, to have a MIDI track with a synthesizer plugin which converts MIDI to audio. Even though the track remains ‘MIDI’, in the sense that its on-disk recordings are MIDI, its output may be audio-only.</p>
<p>More details can be bound at <a href="/working-with-tracks">Working With Tracks</a>.</p>
<p>More details can be found at <a href="/working-with-tracks">Working With Tracks</a>.</p>
<h3>Regions</h3>
<p>A track may contain many segments of audio or MIDI. Ardour contains these segments in things called regions, which are self-contained snippets of audio or MIDI data. Any recording pass, for example, generates a region on each track that is enabled for recording. Regions can be subjected to many editing operations; they may be moved around, split, trimmed, copied, and so on. </p>
<p>More details can be bound at <a href="/working-with-regions">Working With Regions</a>.</p>
<p>More details can be found at <a href="/working-with-regions">Working With Regions</a>.</p>
<h3>Playlists</h3>
<p>The details of what exactly each track should play back is described by a playlist. A playlist is simply a list of regions; each track always has an active playlist, and can have other playlists which can be switched in and out as required.</p>
<p>More details can be bound at <a href="/working-with-playlists">Working With Playlists</a>.</p>
<p>More details can be found at <a href="/working-with-playlists">Working With Playlists</a>.</p>
<h3>Busses</h3>
<p>Busses are another common concept in both DAWs and hardware mixers. They are similar in many ways to tracks; they process audio or MIDI, and can run processing plugins. The only difference is that their input is obtained from other tracks or busses, rather than from disk.</p>
<p>One might typically use a buss to collect together the outputs of related tracks. Consider, for example, a 3-track recording of a drum-kit; given kick, snare and overhead tracks, it may be helpful to connect the output of each to a bus called ‘drums’, so that the drum-kit's level can be set as a unit, and processing (such as equalisation or compression) can be applied to the mix of all tracks.</p>
@ -42,6 +42,6 @@ title: Understanding Basic Concepts and Terminology
<dd>Mac OS X versions of Ardour support AudioUnit (AU) plugins. </dd>
<dl>
<p>Ardour has some support for running Windows VST plugins on Linux, but this is rather complicated, extremely difficult for the Ardour developers to debug, and generally unreliable. If it is at all possible, you are strongly advised to use native LADSPA, LV2 or Linux VST plugins on Linux, or AU on Mac OS X.</p>
<p>More details can be bound at <a href="/working-with-plugins">Working With Plugins</a>.</p>
<p>More details can be found at <a href="/working-with-plugins">Working With Plugins</a>.</p>
</dl>
</dl>

64
_manual/03_setting-up-your-system/07_using_more_than_one_audio_device.html
View File

@ -2,31 +2,69 @@
layout: default
title: Using More Than One Audio Device
---
<p>Ardour will only use a single interface. If you want to use more than one interface you will need to lock them all to a sample clock, and then set up the device outside of Ardour.</p>
<blockquote>
<p>
Ardour is fundamentally designed to be a component in a pro-audio/music creation environment and standard operating practice for such setups involves using only a single digital sample "clock" (something counting off the time between audio samples). This means that trying to use multiple independent soundcards is problematic, because each soundcard has its own sample clock, running independently from the others. Over time, these different clocks drift out of sync with each other, and cause glitches in the audio. You can't stop this drift, although in some cases the effects may be insignificant enough that some people might not care about them.</p>
<p>Thus in an ideal world you should not use multiple independent soundcards but instead use a single device with a single clock and all the inputs, outputs and other features that you need.</p>
<p>Of course, a lot of people don't live in an ideal world, and believe that software should make up for this.
Ardour will only use a single interface. If you want to use more
than one interface you have two choices:
<ol>
<li>
If you want to use Ardour to start JACK (which handles all
audio I/O) you will need to create a "fake" audio device on your
computer the represents all the multiple devices you wish to
use. How to do this is platform dependent and described below.
</li>
<li>
Use a different tool to start JACK and manage all the devices.
</li>
</ol>
</p>
</blockquote>
<p>
Ardour is fundamentally designed to be a component in a
pro-audio/music creation environment and standard operating practice
for such setups involves using only a single digital sample "clock"
(something counting off the time between audio samples). This means
that trying to use multiple independent soundcards is problematic,
because each soundcard has its own sample clock, running independently
from the others. Over time, these different clocks drift out of sync
with each other, and cause glitches in the audio. You can't stop this
drift, although in some cases the effects may be insignificant enough
that some people might not care about them.</p>
<p>
Thus in an ideal world you should not use multiple independent
soundcards but instead use a single device with a single clock and all
the inputs, outputs and other features that you need.
</p>
<p>
Of course, a lot of people don't live in an ideal world, and believe that software should make up for this.
</p>
<h3>OS X</h3>
<p>The precise instructions for creating an "aggregate device" on OS X have varied from one released to another.</p>
<dl class="wide-label">
<dt>OS X 10.5</dt>
<dd>Please read <a href="http://support.apple.com/kb/HT1215">http://support.apple.com/kb/HT1215</a>
</dd>
<dt>OS X 10.6 or later<br><dt>
<dt>OS X 10.6 or later<dt>
</dt>
</dt>
<dd>Please read <a href="http://support.apple.com/kb/HT3956">http://support.apple.com/kb/HT3956</a>
</dd>
</dl>
<p>Aggregate devices also provide a method to use multiple soundcards as a single device. For example, you can "aggregate" 2 different 8-channel devices so that you can record 16 channels into Mixbus.</p>
<p>
Aggregate devices also provide a method to use multiple soundcards as
a single device. For example, you can "aggregate" 2 different
8-channel devices so that you can record 16 channels into Mixbus.
</p>
<h3>Linux</h3>
<p>Please see the instructions at <a href="http://jackaudio.org/faq" title="http://jackaudio.org/faq">http://jackaudio.org/faq</a></p>
<p>
Please see the instructions at <a href="http://jackaudio.org/faq"
title="http://jackaudio.org/faq">http://jackaudio.org/faq</a>
</p>

2
_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html
View File

@ -32,7 +32,7 @@ menu_title: Mackie/Logic Control Devices
<p>Now that you have both control surface and Ardour MIDI ports available, cross connect the control surface MIDI ports and the two mackie ports.</p>
<p>Once you have made these connections once, Ardour will recreate them when it is started in the future (as long as you leave Mackie Control enabled as a control protocol).</p>
<h2>Customizing your control surface</h2>
<p>Every possible Mackie Control button can be bound to any action present in Ardour's GUI. </p>
<p>Every possible Mackie Control button can be found to any action present in Ardour's GUI. </p>
<p>Please check your control surface page for suggestions.</p>