replace 'acronym' HTML tags with 'abbr' tags
This commit is contained in:
David Bolton
parent
85e48bfa70
commit
037f00b703
|
|
@ -17,7 +17,7 @@ title: Understanding Basic Concepts and Terminology
|
|||
<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 <acronym title="Digital Audio Workstation">DAWs</acronym>, 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.</p>
|
||||
<p> A track is a concept common to most <abbr title="Digital Audio Workstation">DAWs</abbr>, 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.</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>
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ title: Understanding Playlists
|
|||
|
||||
<h3>Tracks are not Playlists</h3>
|
||||
<p>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.</p>
|
||||
<p>If you have some experience of other <acronym title="Digital Audio Workstations">DAWs</acronym>, 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.</p>
|
||||
<p>If you have some experience of other <abbr title="Digital Audio Workstations">DAWs</abbr>, 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.</p>
|
||||
|
||||
<h3>Playlists are Cheap</h3>
|
||||
<p>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.</p>
|
||||
|
|
|
|||
|
|
@ -6,6 +6,6 @@ title: Region and Track Selection
|
|||
|
||||
|
||||
<p>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).</p>
|
||||
<p>In some workflows, and particularly if you have experience with other <acronym title="Digital Audio Workstation">DAW</acronym>s, 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.</p>
|
||||
<p>In some workflows, and particularly if you have experience with other <abbr title="Digital Audio Workstation">DAW</abbr>s, 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.</p>
|
||||
<p>To control this behaviour, set <code>Edit > Preferences > Editor > Link selection of regions and tracks</code>. </p>
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ title: Common Region Editing Operations
|
|||
|
||||
|
||||
|
||||
<p>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 <acronym title="Digital Audio Workstation">DAW</acronym>s) you'll find some of these operations critical while others used only rarely. </p>
|
||||
<p>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 <abbr title="Digital Audio Workstation">DAW</abbr>s) you'll find some of these operations critical while others used only rarely. </p>
|
||||
<p>You can carry out all of these operations from the keyboard (see <a href="/default-keyboard-bindings">Default Keyboard Shortcuts</a> for a list). Equivalent operations can be done with mouse in most cases. </p>
|
||||
<p>You may want to review your understanding of <a href="/editing-and-arranging/the-edit-point">the edit point/range</a> and <a href="/editing-and-arranging/what-regions-are-affected">which regions will be affected by region operations</a>.</p>
|
||||
<dl class="wide-table">
|
||||
|
|
|
|||
|
|
@ -6,6 +6,8 @@ title: Default Keyboard Bindings
|
|||
|
||||
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<p>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
|
||||
|
|
|
|||
|
|
@ -6,13 +6,16 @@ title: Controlling Ardour with OSC
|
|||
|
||||
|
||||
|
||||
<p>Open Sound Control (<abbr title="Open Sound Control">OSC</abbr>) 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).</p>
|
||||
<p>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.</p>
|
||||
<h2>Connecting to Ardour via OSC</h2>
|
||||
|
||||
<h2>Connect to Ardour via OSC</h2>
|
||||
<p>
|
||||
OSC support is not enabled by default, but can be turned on via <code>Edit > Preferences > User Interaction</code>. 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:</p>
|
||||
<pre>
|
||||
<Option name="osc-port" value="YourChoiceHere"/>
|
||||
</pre>
|
||||
|
||||
<h2>Transport Control</h2>
|
||||
<dl class="wide-table">
|
||||
<dt>/ardour/transport_stop
|
||||
|
|
@ -46,6 +49,7 @@ OSC support is not enabled by default, but can be turned on via <code>Edit >
|
|||
<dt>/ardour/loop_toggle<br>
|
||||
</dt>
|
||||
</dl>
|
||||
|
||||
<h2>Editing-related</h2>
|
||||
<dl class="wide-table">
|
||||
<dt> /ardour/undo
|
||||
|
|
@ -57,6 +61,7 @@ OSC support is not enabled by default, but can be turned on via <code>Edit >
|
|||
<dd>(this is regular Session _> Save operatio)<br>
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
<h2>Recording control</h2>
|
||||
<dl class="wide-table">
|
||||
<dt> /ardour/toggle_punch_in
|
||||
|
|
@ -70,6 +75,7 @@ OSC support is not enabled by default, but can be turned on via <code>Edit >
|
|||
<dd>(toggles all tracks recording state). !currently toggles on but not off for 2.0 branch.<br>
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
<h2>Track specific operations</h2>
|
||||
<p>
|
||||
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
|
|||
<dd>where [gain_db] is a float ranging from -400 to 6 representing the desired gain of the track in dB.<br>
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
<h2>Menu actions</h2>
|
||||
<p>
|
||||
Every single menu item in Ardour's GUI is accessible via OSC. There is<br>
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@ Setting up a proper A/V post-production studio can be a complicated task. As muc
|
|||
</p>
|
||||
|
||||
<ul>
|
||||
<li>Synchronization ardour → video-display-box should be accomplished by external means jack-transport(netjack), MTC, LTC (<acronym title="Open Sound Control - "postmodern MIDI"">OSC</acronym> and/or ssh-pipe work but introduce additional latency + jitter)
|
||||
<li>Synchronization ardour → video-display-box should be accomplished by external means jack-transport(netjack), MTC, LTC (<abbr title="Open Sound Control - "postmodern MIDI"">OSC</abbr> and/or ssh-pipe work but introduce additional latency + jitter)
|
||||
</li>
|
||||
</ul>
|
||||
<ul>
|
||||
|
|
@ -72,7 +72,7 @@ Setting up a proper A/V post-production studio can be a complicated task. As muc
|
|||
</li>
|
||||
</ul>
|
||||
<ul>
|
||||
<li>..or override xjremote's behavior – instead of IPC with a local running xjadeo-process, using <acronym title="Open Sound Control - "postmodern MIDI"">OSC</acronym> for example. xjadeo would run permanently and ardour will just tell it to load files and set offsets via <acronym title="Open Sound Control - "postmodern MIDI"">OSC</acronym>. see <a href="http://xjadeo.git.sourceforge.net/git/gitweb.cgi?p=xjadeo/xjadeo;a=blob_plain;f=contrib/xjremote-osc" title="http://xjadeo.git.sourceforge.net/git/gitweb.cgi?p=xjadeo/xjadeo;a=blob_plain;f=contrib/xjremote-osc" rel="nofollow">xjremote-osc</a> example script.
|
||||
<li>..or override xjremote's behavior – instead of IPC with a local running xjadeo-process, using <abbr title="Open Sound Control - "postmodern MIDI"">OSC</abbr> for example. xjadeo would run permanently and ardour will just tell it to load files and set offsets via <acronym title="Open Sound Control - "postmodern MIDI"">OSC</acronym>. see <a href="http://xjadeo.git.sourceforge.net/git/gitweb.cgi?p=xjadeo/xjadeo;a=blob_plain;f=contrib/xjremote-osc" title="http://xjadeo.git.sourceforge.net/git/gitweb.cgi?p=xjadeo/xjadeo;a=blob_plain;f=contrib/xjremote-osc" rel="nofollow">xjremote-osc</a> example script.
|
||||
</li>
|
||||
</ul>
|
||||
<ul>
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user