From 037f00b703c6baec519c7f7443c0eb72e6a80703 Mon Sep 17 00:00:00 2001 From: David Bolton Date: Sun, 7 Jul 2013 02:05:05 -0500 Subject: [PATCH] replace 'acronym' HTML tags with 'abbr' tags --- .../02_understanding-basic-concepts-and-terminology.html | 2 +- .../01_understanding-playlists.html | 2 +- .../01_region-and-track-selection.html | 2 +- .../05_common-region-editing-operations.html | 2 +- _manual/20_default-keyboard-bindings.html | 2 ++ .../01_controlling-ardour-with-osc.html | 9 ++++++++- _manual/23_video-timeline/01_setup.html | 4 ++-- 7 files changed, 16 insertions(+), 7 deletions(-) diff --git a/_manual/02_introducing-ardour/02_understanding-basic-concepts-and-terminology.html b/_manual/02_introducing-ardour/02_understanding-basic-concepts-and-terminology.html index e4aabb7..b57e797 100644 --- a/_manual/02_introducing-ardour/02_understanding-basic-concepts-and-terminology.html +++ b/_manual/02_introducing-ardour/02_understanding-basic-concepts-and-terminology.html @@ -17,7 +17,7 @@ title: Understanding Basic Concepts and Terminology

More details can be found at Working With Sessions.

Tracks

-

A track is a concept common to most DAWs, and also used 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.

+

A track is a concept common to most DAWs, and also used 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.

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.

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.

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.

diff --git a/_manual/09_working-with-playlists/01_understanding-playlists.html b/_manual/09_working-with-playlists/01_understanding-playlists.html index 66eae3c..87f1589 100644 --- a/_manual/09_working-with-playlists/01_understanding-playlists.html +++ b/_manual/09_working-with-playlists/01_understanding-playlists.html @@ -11,7 +11,7 @@ title: Understanding Playlists

Tracks are not Playlists

It is important to understand that a track is not a playlist. A track has a playlist. A track is a mechanism for generating the audio stream represented by the playlist and passing it through a signal processing pathway. At any point in time, a track has a single playlist associated with it. When the track is used to record, that playlist will have one or more new regions added to it. When the track is used for playback, the contents of the playlist will be heard. You can change the playlist associated with a track at (almost) any time, and even share playlists between tracks.

-

If you have some experience of other DAWs, then you might have come across the term "virtual track", normally defined as a track that isn't actually playing or doing anything, but can be mapped/assigned to a "real track". This concept is functionally identical to Ardour's playlists. We just like to be little more clear about what is actually happening rather than mixing old and new terminology ("virtual" and "track") into confusing terminology.

+

If you have some experience of other DAWs, then you might have come across the term "virtual track", normally defined as a track that isn't actually playing or doing anything, but can be mapped/assigned to a "real track". This concept is functionally identical to Ardour's playlists. We just like to be little more clear about what is actually happening rather than mixing old and new terminology ("virtual" and "track") into confusing terminology.

Playlists are Cheap

One thing you should be clear about is that playlists are cheap. They don't cost anything in terms of CPU consumption, and they have very minimal efforts on memory use. Don't be afraid of generating new playlists whenever you want to. They are not equivalent to tracks, which require extra CPU time and significant memory space, or audio files, which use disk space, or plugins that require extra CPU time. If a playlist is not in use, it occupies a small amount of memory, and nothing more.

diff --git a/_manual/10_working-with-tracks/03_selecting-tracks/01_region-and-track-selection.html b/_manual/10_working-with-tracks/03_selecting-tracks/01_region-and-track-selection.html index 601a3d1..55d0727 100644 --- a/_manual/10_working-with-tracks/03_selecting-tracks/01_region-and-track-selection.html +++ b/_manual/10_working-with-tracks/03_selecting-tracks/01_region-and-track-selection.html @@ -6,6 +6,6 @@ title: Region and Track Selection

By default, selecting regions has no impact on track selection. You can select a track, then select a region in another track (or vice versa) and both selections will co-exist happily. Operations that are applied to tracks will use the track selection, and those that apply to regions will use the region selection. Similarly, deselecting a region will not deselect the track it is in (if that track was selected).

-

In some workflows, and particularly if you have experience with other DAWs, this is not the most comfortable way to work. You may prefer to work in a style where selecting a region will also select the track that the region is in. Similarly, when the last selected region in a track is deselected, the track will also become unselected.

+

In some workflows, and particularly if you have experience with other DAWs, this is not the most comfortable way to work. You may prefer to work in a style where selecting a region will also select the track that the region is in. Similarly, when the last selected region in a track is deselected, the track will also become unselected.

To control this behaviour, set Edit > Preferences > Editor > Link selection of regions and tracks.

diff --git a/_manual/15_editing-and-arranging/05_common-region-editing-operations.html b/_manual/15_editing-and-arranging/05_common-region-editing-operations.html index 3422f16..d1a9691 100644 --- a/_manual/15_editing-and-arranging/05_common-region-editing-operations.html +++ b/_manual/15_editing-and-arranging/05_common-region-editing-operations.html @@ -6,7 +6,7 @@ title: Common Region Editing Operations -

This section covers a set of region editing operations that you are likely to use again and again while working on a session. Depending on your work habits (and experience of other DAWs) you'll find some of these operations critical while others used only rarely.

+

This section covers a set of region editing operations that you are likely to use again and again while working on a session. Depending on your work habits (and experience of other DAWs) you'll find some of these operations critical while others used only rarely.

You can carry out all of these operations from the keyboard (see Default Keyboard Shortcuts for a list). Equivalent operations can be done with mouse in most cases.

You may want to review your understanding of the edit point/range and which regions will be affected by region operations.

diff --git a/_manual/20_default-keyboard-bindings.html b/_manual/20_default-keyboard-bindings.html index 8b0ac8f..47d8f16 100644 --- a/_manual/20_default-keyboard-bindings.html +++ b/_manual/20_default-keyboard-bindings.html @@ -6,6 +6,8 @@ title: Default Keyboard Bindings +

Almost every available function in Ardour can be executed via a keyboard shortcut (or OSC command). There are many more functions available than there are keys on even the largest current computer keyboards, so only a subset of them are bound to keys by default.

+

Ardour comes with a rich set of default bindings. The default bindings are "mnemonic" in that they focus on trying use to the letter that starts the name of an operation as the binding for that operation. This is not always possible, but it acts as a general diff --git a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html index 283605c..5a723f2 100644 --- a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html +++ b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html @@ -6,13 +6,16 @@ title: Controlling Ardour with OSC +

Open Sound Control (OSC) lets synthesizers and other devices communicate with Ardour. OSC devices can send commands relating to playback (such as play or stop), performance (such as volume, play, stop, and almost any other function (such as Edit, or Undo).

Ardour is probably one of the most OSC-controllable audio applications around, but as with all OSC-controllable apps, you can't do much without knowing what messages can be sent. This document describes the various categories of messages that Ardour understands. It is subject to change, particular the "Actions" part below, since this relates to the GTK GUI for Ardour rather than the backend.

-

Connecting to Ardour via OSC

+ +

Connect to Ardour via OSC

OSC support is not enabled by default, but can be turned on via Edit > Preferences > User Interaction. Once enabled, Ardour will listen on port 3819 by default. This port number can be changed by editing $ARDOUR_CONFIG and adding this line within the <Config> section:

   <Option name="osc-port" value="YourChoiceHere"/>
+

Transport Control

/ardour/transport_stop @@ -46,6 +49,7 @@ OSC support is not enabled by default, but can be turned on via Edit >
/ardour/loop_toggle
+

Editing-related

/ardour/undo @@ -57,6 +61,7 @@ OSC support is not enabled by default, but can be turned on via Edit >
(this is regular Session _> Save operatio)
+

Recording control

/ardour/toggle_punch_in @@ -70,6 +75,7 @@ OSC support is not enabled by default, but can be turned on via Edit >
(toggles all tracks recording state). !currently toggles on but not off for 2.0 branch.
+

Track specific operations

For each of the following, [remote_id] is the remote_id or the track @@ -96,6 +102,7 @@ For each of the following, [remote_id] is the remote_id or the track

where [gain_db] is a float ranging from -400 to 6 representing the desired gain of the track in dB.
+

Menu actions

Every single menu item in Ardour's GUI is accessible via OSC. There is
diff --git a/_manual/23_video-timeline/01_setup.html b/_manual/23_video-timeline/01_setup.html index 82c8fd3..3cd8684 100644 --- a/_manual/23_video-timeline/01_setup.html +++ b/_manual/23_video-timeline/01_setup.html @@ -60,7 +60,7 @@ Setting up a proper A/V post-production studio can be a complicated task. As muc

    -
  • Synchronization ardour → video-display-box should be accomplished by external means jack-transport(netjack), MTC, LTC (OSC and/or ssh-pipe work but introduce additional latency + jitter) +
  • Synchronization ardour → video-display-box should be accomplished by external means jack-transport(netjack), MTC, LTC (OSC and/or ssh-pipe work but introduce additional latency + jitter)
    @@ -72,7 +72,7 @@ Setting up a proper A/V post-production studio can be a complicated task. As muc
    -
  • ..or override xjremote's behavior – instead of IPC with a local running xjadeo-process, using OSC for example. xjadeo would run permanently and ardour will just tell it to load files and set offsets via OSC. see xjremote-osc example script. +
  • ..or override xjremote's behavior – instead of IPC with a local running xjadeo-process, using OSC for example. xjadeo would run permanently and ardour will just tell it to load files and set offsets via OSC. see xjremote-osc example script.