<dd>Ardour supports VST plugins that have been compiled for Linux.</dd>
<dt> AudioUnit (AU)</dt>
<dd>Mac OS X versions of Ardour support AudioUnit (AU) plugins. </dd>
-<dl>
+</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 found at <a href="/working-with-plugins">Working With Plugins</a>.</p>
- </dl>
-</dl>
</ul>
<p>You are strongly encouraged to invest in a two button mouse. You will find that a good quality mouse (especially one with a weighted, latchable scroll wheel) will make your use of Ardour vastly more efficient. They are cheap, and time is not.</p>
-<p>For more detailed instructions see <a href="/ardours-interface/basic-gui-operations/using-the-mouse/">Using the mouse</a>.</a></p>
+<p>For more detailed instructions see <a href="/ardours-interface/basic-gui-operations/using-the-mouse/">Using the mouse</a>.</p>
<p>
Ardour will only use a single interface. If you want to use more
than one interface you have two choices:
-
+</p>
<ol>
<li>
If you want to use Ardour to start JACK (which handles all
Use a different tool to start JACK and manage all the devices.
</li>
</ol>
-</p>
<p>
Ardour is fundamentally designed to be a component in a
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>
+<h2>OS X</h2>
<p>
Aggregate devices provide a method to use multiple soundcards as
a single device. For example, you can "aggregate" 2 different
</dd>
</dl>
-<h3>Linux</h3>
+<h2>Linux</h2>
<p>
Please see the instructions at <a href="http://jackaudio.org/faq"
on Ubuntu, and like Ubuntu Studio, has these settings preconfigured, while
also containing customized versions of Ubuntu packages, which often are
more up to date.
-<p>
+</p>
<h2>Installing Ardour</h2>
There may be unintended differences, and even bugs in Ubuntu native
<p>
The specific issues known at this time for all flavors of Ubuntu
12.04 and 12.10 are:
+</p>
<ul>
<li>a bug in PulseAudio that causes it not to give up the
soundcard when JACK asks (<a href="https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1163638">LP: #1163638</a>
(fixed in Ubuntu 13.04).</li>
</ul>
-</p>
</dd>
<dt>Symptoms</dt>
<dd>
</p>
</dd>
<dt>How to fix</dt>
+<dd>
<p>
These bugs do not affect the upcoming 13.04 release, and earlier
releases (12.04 and 12.10) are in the process of being fixed.
</p>
-<dd>
</dd>
</dl>
</dl>
<h2>Reporting Issues</h2>
<p>Given the difficulties in supporting Ubuntu and the limited time/resources of the Ardour team, the <code>Ubuntu Studio Project</code> has requested that issues and bug reports related to Ubuntu, Ubuntu Studio and other derivitives be directed to them.</p>
-<h4>Contact Information for Ubuntu Studio</h4>
+<h3>Contact Information for Ubuntu Studio</h3>
<p><a href="http://ubuntustudio.org" target="_blank">The Ubuntu Studio Homepage</a></p>
<p><a href="http://ubuntuforums.org/forumdisplay.php?f=335" target="_blank">The Ubuntu Studio Forums.</a></p>
<p><a href="https://help.ubuntu.com/community/UbuntuStudio/MailLists" target="_blank">Information on the Ubuntu Studio Mailing Lists.</a></p>
- <h2>Starting Ardour on the command line (Linux)</h2>
-<p>Like (almost) any other program on Linux, Ardour can be started on the command line.</p>
-<ul>
-<li>type the following command in a terminal window<br/><pre>ardour3</pre>
-</li>
-<li>to start Ardour with an existing session, type the following command in a terminal window<br
-/><pre>ardour3 /path/to/session</pre>
-<p>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 (including snapshots).</p>
-</li>
-<li>to start Ardour with a new, named session, type the following command in a terminal
-window<br/ ><pre>ardour3 -N /path/to/new/session</pre>
-<p>replacing /path/to/new/session with the name of the folder where you want the session stored.
+<h2>Starting Ardour on the command line (Linux)</h2>
+<p>Like (almost) any other program on Linux, Ardour can be started on the command line.
+Type the following command in a terminal window:
</p>
-</li>
-</ul>
+<code>ardour3</code>
+<p>To start Ardour with an existing session:</p>
+<code>ardour3 /path/to/session</code>
+<p>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 (including snapshots).</p>
+<p>To start Ardour with a new, named session:</p>
+<code>ardour3 -N /path/to/new/session</code>
+
<h3>Other Command Line Options</h3>
---
layout: default
-title: Ranges & Marks List
+title: Ranges & Marks List
---
---
layout: default
-title: Track & Bus Group List
+title: Track & Bus Group List
---
---
layout: default
-title: Tracks & Busses List
+title: Tracks & Busses List
---
Under the <code>Windows</code> item in the main menu you will find the "Big Clock" window, which also shows the playhead position in a big, fully resizable window. The big clock is very useful when you need to work away from the screen but still want to see the playhead position clearly (such as when working with a remote control device across, or in another, room). The big clock will also change its visual appearance to indicate when active recording is taking place. Below on the left is a screenshot showing a fairly large big clock window filling a good part of the display, and on the right, the same clock during active recording.
</p>
<p>
-<a href="/files/bigclock.png"><img src="/files/bigclock.png" height="100" alt="an image of the big clock filling a screen" /></a> <a href="/files/bigclock-recording.png"><img src="/files/bigclock-recording.png" height="100" alt="an image of the big clock while recording"></a>
+<a href="/files/bigclock.png"><img src="/files/bigclock.png" height="100" alt="an image of the big clock filling a screen" /></a> <a href="/files/bigclock-recording.png"><img src="/files/bigclock-recording.png" height="100" alt="an image of the big clock while recording"
+/></a>
</p>
<h4>The Special Role of the Secondary Transport Clock</h4>
<p>
-
<p>Ardour has many available commands for playback control that can be bound to keys. Many of them have default bindings, some do not, so the list below shows both the default bindings and command names.</p>
+<p>Ardour has many available commands for playback control that can be bound to keys. Many of them have default bindings, some do not, so the list below shows both the default bindings and command names.</p>
<dl class="wide-table">
<dt>Space</dt>
<dd>switch between playback and stop.</dd>
<dt>Home</dt>
<dd>Move playhead to session start marker</dd>
<dt>End</dt>
-<dd>Move playhead to session end marker<br><dd>
-</dd>
-</dd>
+<dd>Move playhead to session end marker</dd>
<dt>Right Arrow</dt>
<dd></dd>
<dt>Left Arrow</dt>
-<p>Rages are essentially two Location Markers the are grouped together to mark the beginning and end of a section in the timeline.
+<p>
+ Rages are essentially two Location Markers the are grouped
+ together to mark the beginning and end of a section in the timeline.
+</p>
<h3>Creating a Range on the timeline</h3>
-<p>To create a <code>Range</code> on the timeline, right click on the <code>Range Markers</code> <code>Ruler</code> at the top of the <code>Timeline</code> then select <code>New Range</code>. Two markers with the same name will appear along the ruler. Both marks can be moved along the timeline by clicking and dragging them to the desired location.
+<p>
+ To create a <code>Range</code> on the timeline, right click on the
+ <code>Range Markers</code> <code>Ruler</code> at the top of the
+ <code>Timeline</code> then select <code>New Range</code>.
+ Two markers with the same name will appear along the ruler.
+ Both marks can be moved along the timeline by clicking and dragging them to the desired location.
</p>
<h3>Creating a Range from the Ranges & Marks List</h3>
<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"/></p>
+<p><img src="/images/No%20problem.gif" alt="AATranslator Demo Animation"/></p>
<dd>Tracks using this mode do <strong>destructive</strong> recording: all data is recorded to a single file and if you overdub a section of existing data, the existing data is destroyed (irrevocably - there is no undo). Fixed crossfades are added at every punch in and out point. This mode can be useful for certain kinds of dubbing workflows, but it not suggested for normal use.</dd>
</dl>
<p>The screenshot below shows a subtle difference between results of an overdub in normal mode (upper track) and non-layered mode (lower track). Both tracks were created using identical audio data. The upper track shows an overdub (the middle shorter region) in normal mode. In normal mode Ardour created a new region which if you look carefully has been layered on top of the the existing (longer) region. The lower track is in non-layered mode, and rather than overlay the overdub region, it split the existing region and inserted the new overdub region in between. </p>
-<p><img src="/files/a3/a3_nonlayered_example.png" alt="normal and non-layered overdubbing comparision"></p>
+<p><img src="/files/a3/a3_nonlayered_example.png" alt="normal and non-layered overdubbing comparision"
+/></p>
<h2 id="channelconfiguration">Channel Configuration</h2>
<p>Ardour tracks can have any number of inputs and any number of outputs, and the number of either can be changed at any time (subject to restrictions caused by any plugins in a track). However it is useful to not have to configure this sort of thing for the most common cases, and so the <a href="/working-with-tracks/adding-tracks">Add Tracks</a> dialog allows you to select "Mono", "Stereo" and few other typical configurations.</p>
</li>
</ul>
<p>Any of these actions will open the Add Track or Bus dialog. Note that any new tracks from this dialog will appear after the last currently selected track (if any).</p>
-<p><img src="/ardour/manual/html/screenshots/add-track-or-bus.png" alt="the add-track dialog"></p>
+<p><img src="/ardour/manual/html/screenshots/add-track-or-bus.png" alt="the add-track dialog"
+/></p>
<p>From here, you can select firstly the number of tracks or busses to add, and the type; audio track, MIDI track or bus. There are also some options, which vary depending on the type of thing you are creating.</p>
<p>These options are:</p>
<dl class="wide-table">
<p>A typical control area or "bus header" is shown below:</p>
-<p><img src="/ardour/manual/html/screenshots/typical-bus-controls.png" alt="bus controls"></p>
+<p><img src="/ardour/manual/html/screenshots/typical-bus-controls.png" alt="bus controls"
+ /></p>
<p> At the top-left of the controls is the name of the bus. You can double click to edit the name, but the name must be unique within the session. Underneath the name is a copy of the bus' main level fader. The control buttons to the right-hand side are:</p>
<dl>
<dt id="mute">m</dt>
<p>A typical control area or "track header" for an audio track is shown below:</p>
-<p><img src="/ardour/manual/html/screenshots/typical-audio-track-controls.png" alt="audio track controls"></p>
+<p><img src="/ardour/manual/html/screenshots/typical-audio-track-controls.png" alt="audio track controls"
+ /></p>
<p> An audio track has the same <a href="/working-with-tracks/bus-controls">controls as a bus</a>, with the addition of two extras.
-
+</p>
<dl>
<dt id="record">[pink circle]</dt>
<dd>Record - The red button with the pink circle enables recording to the track. When this is clicked it will gain a bright red outline, and the track will then be recorded onto when the main session record enable is turned on with the transport rolling.</dd>
<p>A typical control area for a MIDI track is shown below:</p>
-<p><img src="/ardour/manual/html/diagrams/typical-midi-track-controls.png" alt="midi track controls"></p>
+<p><img src="/ardour/manual/html/diagrams/typical-midi-track-controls.png" alt="midi track controls"
+ /></p>
<p>To see the full set of MIDI track controls, as shown above, you need to increase the <a href="/working-with-tracks/controlling-track-appearance/track-height/">track height</a> beyond the default. MIDI tracks show only a few of the control elements when when there is insufficient vertical space.</p>
<p>A MIDI track has the same basic <a href="/working-with-tracks/audio-track-controls">controls as an audio track</a>, with the addition of two extra elements. The set of buttons below the main track controls controls the MIDI channels that should be visible in the editor. A MIDI track's data may span any number of the 16 available MIDI channels, and sometimes it is useful to view only a subset of those channels; different instruments may, for example, be put on different MIDI channels. Clicking on a channel number toggles its visibility.</p>
<p>To the right of the MIDI track controls is a representation of a piano keyboard called the ‘scroomer’. This performs a couple of functions. Firstly, the scrollbar controls the range of pitches that are visible on the track. Drag the body of the scrollbar up and down to display higher or lower pitches. Drag the scrollbar ‘handles’ to zooms in and out and increase and decrease the range of visible pitches. The piano keyboard gives a reference for the pitches visible on the track. In addition, clicking on the piano plays the corresponding MIDI note for reference. </p>
</li>
<li>Vocoder <a href="http://www.sirlab.de/linux/download_vocoder.html">http://www.sirlab.de/linux/download_vocoder.html</a>
</li>
-<li>WASP <a href="http://linux01.gwdg.de/~nlissne/wasp/index.html">http://linux01.gwdg.de/~nlissne/wasp/index.html</span></a> (mar wanted!)
+<li>WASP <a href="http://linux01.gwdg.de/~nlissne/wasp/index.html">http://linux01.gwdg.de/~nlissne/wasp/index.html</a> (mar wanted!)
</li>
<li>Nova <a href="https://tim.klingt.org/nova/download/nova_filters-0.2.tar.bz2">https://tim.klingt.org/nova/download/nova_filters-0.2.tar.bz2</a>
</li>
something worth planning on. Ardour releases for OS X ship with a
collection of many LADSPA plugins, some of which are very useful and
some of which are outright buggy.
+</p>
<p>
Most of the plugins you are likely to use on OS X will be in Apple's
AudioUnit format. These have their own installation process that tends to
<blockquote><p>
Notable exceptions are aux sends and connections to the monitor bus (if you are using one): these cannot be controlled from a patchbay, and are basically not under manual control at all.
</p></blockquote>
-<p><img align="center" src="/ardour/manual/html/screenshots/connection-manager.png" alt="an example patchbay" /></p>
+<p><img src="/ardour/manual/html/screenshots/connection-manager.png" alt="an example patchbay" /></p>
<p>The patchbay presents two groups of ports; one set of sources (which produce data), and one of destinations (which consume data). Depending on the relative number of each, the sources will be placed on the left or the top of the dialogue, and the destinations on the right or the bottom. Thus, in general, signal flow is from top or left to right or bottom.</p>
<p>Both sources and destinations are divided up into groups, with each group being given a tab. Click on the appropriate tab to show the ports in each group (‘Ardour Busses’, ‘Ardour Tracks’ and so on).</p>
<p>The groups that are used are as follows:</p>
-<p>This section explains the rules used to decide what regions are affected by editing operations. You don't really have to understand them - hopefully things will Just Work - but it may be useful to understand the rules some of the time.</p>
-<p>Ardour divides operations up into those that operate on a single point in time (Split being the obvious example) and those that operate on two points (which can also be considered to be a range of sorts), Separate is a good example of this.</p>
-<p> Most operations will operate on the currently selected region(s), but if no regions are selected, the region that the mouse is in will be used instead. Single-point operations will generally pick a set of regions to use based on the following rules:</p>
+<p>
+ This section explains the rules used to decide what regions are affected
+ by editing operations. You don't really have to understand them - hopefully
+ things will Just Work - but it may be useful to understand the rules some
+ of the time.
+</p>
+<p>
+ Ardour divides operations up into those that operate on a single point
+ in time (Split being the obvious example) and those that operate on two
+ points (which can also be considered to be a range of sorts), Separate
+ is a good example of this.
+</p>
+<p>
+ Most operations will operate on the currently selected region(s), but if
+ no regions are selected, the region that the mouse is in will be used
+ instead. Single-point operations will generally pick a set of regions to
+ use based on the following rules:</p>
<ol>
-<li> If the edit point is `mouse':
-<ul>
-<li>if the mouse is over a selected region, or no region, use all selected regions.
-</li>
-<li>if the mouse is over an unselected region, use just that region.
- </li>
-</ul>
-</li>
-<li> For all other edit points
-<ul><li>use the selected regions <strong>and</strong> those that are both under the edit position <strong>and</strong> on a selected track, or on a track which is in the same active edit-enabled route group<br>
- as a selected region.
- </li></ul>
-</li>
+ <li> If the edit point is `mouse':
+ <ul>
+ <li>if the mouse is over a selected region, or no region, use all selected regions.</li>
+ <li>if the mouse is over an unselected region, use just that region.</li>
+ </ul>
+ </li>
+ <li> For all other edit points
+ <ul>
+ <li>
+ use the selected regions <strong>and</strong> those that are both
+ under the edit position <strong>and</strong> on a selected track,
+ or on a track which is in the same active edit-enabled route group
+ as a selected region.
+ </li>
+ </ul>
+ </li>
</ol>
<p>The rationale here for the two different rules is that the mouse edit point is special in that its position indicates both a time and a track; the other edit points (Playhead,Marker) indicates only a time.</p>
<dt>Region Bounds</dt>
<dd>Snaps positions to the nearest region start or end</dd>
</dl>
-<p>To use Region starts/ends/syncs/bounds as snap choices, you must have either
+<p>To use Region starts/ends/syncs/bounds as snap choices, you must have
+either</p>
<ul>
<li><em>No</em> tracks selected, which means that Ardour snaps to regions on any track, or </li>
<li>Several tracks selected, which means that Ardour only snaps to regions on those selected tracks.</li>
<dt>
<em>Selecting, moving, copying, trimming, deleting</em> <strong>regions</strong><dt>
</dt>
-</dt>
<dd>leave "Note Level Editing" disabled, use object, range or other mouse modes</dd>
<dt>
<em>Selecting, moving, copying trimming, deleting</em> <strong>notes</strong>
<h3>Making an existing copy of a MIDI region independent</h3>
<p>
-<key>Context-click</key> on the MIDI region you want to be
+Context-click on the MIDI region you want to be
independent. From the context menu, select <code>MIDI > Unlink From
Other Copies</code>. The copy is now using an independent version of
the data, and edits to the copy will affect only the copy. Other
</ul>
<p>There are further options with when solo controls are listen controls: the part of the track or bus from which the listen signal is obtained can be configured. Underneath the ‘Solo controls are Listen controls’ option in ‘Ardour Preferences’ is an option for ‘listen position’, which can be either After-Fade Listen (AFL) or Pre-Fade Listen (PFL). AFL, as its name suggests, obtains its signal from some point after the track or bus’ fader, and PFL from before it. The precise point to get the signal from can further be configured using the ‘PFL signals come from’ and ‘AFL signals come from’ options.</p>
<p>The solo-mute arrangement with a monitor bus is shown below:</p>
-<p><img src="/ardour/manual/html/diagrams/solo-mute.png" alt="mute/solo signal flow"></p>
+<p><img src="/ardour/manual/html/diagrams/solo-mute.png" alt="mute/solo signal flow" /></p>
<p> Here we have a number of tracks or busses (in orange). Each one has an output which feeds the master bus. In addition, each has PFL and AFL outputs; we have a choice of which to use. PFL/AFL from each track or bus are mixed. Then, whenever anything is set to AFL/PFL, the monitor out becomes just those AFL/PFL feeds; the rest of the time, the monitor out is fed from the master bus.</p>
<p>In this scheme Solo has no effect other than to mute other non-soloed tracks; with solo (rather then listen), the monitor out is fed from the master bus.</p>
<h2>Other solo options</h2>
make them move within the space over time.
</p>
-<h3>Types of Panners</h3>
+<h2>Types of Panners</h2>
<p>
The way a panner works depends a great deal on how many signals it
number of signals to any number of ouputs. In reality, Ardour does
not have specific panners for each different situation. Currently,
it has dedicated panners for the following situations:
-
+</p>
<ul>
<li>1 signal distributed to 2 outputs (the "mono" panner)</li>
<li>2 signals distributed to 2 outputs (the "stereo" panner)</li>
<li>N signals distributed to N outputs (the "vbap" panner)</li>
</ul>
-
+<p>
Even for each of these cases, there are many different ways to
implement panning. Ardour currently offers just one solution to each
of these situations, but in the future will offer more.
</p>
-<h3>Panning is not Balance</h3>
+<h2>Panning is not Balance</h2>
<p>
If you are used to the "balance" control found on most home music
sound stage that has been created with pan pots.<sup><a href="#caveat">*</a></sup>
</p>
<div class="well">
-<p>
With the default values it is not possible to alter the position,
since the width is already spread entirely across both outputs. To
alter the position, you must first reduce the width.
-</p>
</div>
<h2>Stereo Panner User Interface</h2>
the top and bottom half. Click and/or drag in the top half to
control position; click and/or drag in the bottom half to control
width (see below for details).
-<p>
+</p>
<p>
In the top half is the position indicator, which shows where the
center of the stereo image is relative to the left and right
USA is not Kansas, but "Los Angeles: 50% New York: 50%".
</p>
-<h2>Examples In Use</h2>
+<h3>Examples In Use</h3>
<table>
<tr><th>Appearance</th><th>Settings</th></tr>
L=0 R=100</td></tr>
</table>
-<h2>Using the mouse</h2>
+<h4>Using the mouse</h4>
<p>
Mouse operations in the upper half of the panner adjust the position
implementation must therefore include the possibility to define this
layout.
</p>
-<img src="/images/VBAP-panner-5.png" class="small right"/>
+<img src="/images/VBAP-panner-5.png" class="small right" alt="The VBAP
+panner with 5 outputs"/>
<p>
Ardour currently uses a simplified approach: if a track or bus has more
than two output channels (which implies stereo), it assumes that you
any desired spatialisation.
</p>
<h3>Experimental 3D VBAP</h3>
-<img src="/images/VBAP-panner-10.png" class="small right"/>
+<img src="/images/VBAP-panner-10.png" class="small right" alt="The VBAP
+panner with 10 outputs, in experimental 3D mode"/>
<p>
For tracks with 10 outputs, Ardour will currently assume a 3-dimensional
speaker layout corresponding to Auro-3D 10.1, which is a horizontal 5.1
</p>
<h2>N:M panning</h2>
-<img src="/images/VBAP-panner-4in5.png" class="small right"/>
+<img src="/images/VBAP-panner-4in5.png" class="small right" alt="The VBAP
+panner in 4 in, 5 out mode"/>
<p>
For tracks and busses with more than one input, Ardour will (for now) assume that
you wish to distribute the inputs symmetrically along the latitude around
There are three common timecode formats:
</p>
<ul>
-<li>LTC – Linear/Longitudinal Time Code</li>
-<li>MTC – MIDI Time Code</li>
-<li>MIDI-Clock – tempo based time</li>
+ <li>LTC – Linear/Longitudinal Time Code</li>
+ <li>MTC – MIDI Time Code</li>
+ <li>MIDI-Clock – tempo based time</li>
</ul>
<p>
As well as a JACK specific timecode implementation:
</p>
<ul>
-<li>JACK-transport</li>
+ <li>JACK-transport</li>
</ul>
<p>
<h3>LTC Generator</h3>
<p>
-The volume of the LTC signal can be conigured in in the <code>Preferences > Transport</code> dialog. By default it is set to -18dBFS which corresponds to 0dBu in an EBU calibrated system.
+The volume of the LTC signal can be configured in in the <code>Preferences > Transport</code> dialog. By default it is set to -18dBFS which corresponds to 0dBu in an EBU calibrated system.
</p>
<p>
<p>
LTC is send regardless of Ardour's transport-speed. It is accurately generated even for very slow speeds (<5%) and only limited by the soundcard's sampling-rate and filter (see <a href="http://en.wikipedia.org/wiki/Gibbs_phenomenon#Signal_processing_explanation" title="http://en.wikipedia.org/wiki/Gibbs_phenomenon">Gibbs phenomenon</a>) for high speeds.
+</p>
<h2>Ardour Slave Configuration</h2>
When Ardour is chasing an external timecode source the following cases need to be distinguished:
</p>
<ol>
-<li>the timecode source shares the clock</li>
-<li>the timecode source is independent (no wordclock sync)</li>
+ <li>the timecode source shares the clock</li>
+ <li>the timecode source is independent (no wordclock sync)</li>
</ol>
-
-<p>
-and
-</p>
+<p>and</p>
<ol>
-<li>the timecode source uses the same FPS setting as Ardour</li>
-<li>the timecode source runs at different frames-per-second</li>
+ <li>the timecode source uses the same FPS setting as Ardour</li>
+ <li>the timecode source runs at different frames-per-second</li>
</ol>
<p>
</dd>
<dt> /ardour/routes/gaindB [remote_id] [gain_db]
</dt>
-<dd>where [gain_db] is a float ranging from -400 to 6 representing the desired gain of the track in dB.<br>
+<dd>where [gain_db] is a float ranging from -400 to 6 representing the desired gain of the track in dB.
</dd>
</dl>
<h2>Menu actions</h2>
<p>
-Every single menu item in Ardour's GUI is accessible via OSC. There is<br>
-a single common syntax to trigger the action as if it was selected<br>
+Every single menu item in Ardour's GUI is accessible via OSC. There is
+a single common syntax to trigger the action as if it was selected
with the mouse (or keyboard):</p>
<pre>
/ardour/access_action [action_name]
</pre>
-<p>The list below shows all available values of [action-name] as of<br>
-mid-March 2010 for Ardour 2.X. You can get the current list at any<br>
+<p>The list below shows all available values of [action-name] as of
+mid-March 2010 for Ardour 2.X. You can get the current list at any
time by running Ardour with the -b flag.</p>
<ul>
<li> Common/About
projects / ardour-manual / commitdiff