--- /dev/null
+---
+layout: default
+title: Mouse
+---
+
+
+
+
+<p>Ardour is designed to work best with a three button mouse equipped with a scroll wheel. </p>
+<p>It can be used with a two button mouse or touchpad, but at least two key operations will not (easily) be available to you:</p>
+<ul>
+<li>time-constrained region copying
+</li>
+<li><a href="/using-control-surfaces/midi-learn/">MIDI bindings</a> created by "learning" them from incoming MIDI
+</li>
+</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>
+++ /dev/null
----
-layout: default
-title: The Mouse
----
-
-
-
-
-<p>Ardour is designed to work best with a 3 button mouse equipped with a scroll wheel. </p>
-<p>It can be used with a 2 button mouse or touchpad, but at least 2 key operations will not (easily) be available to you:</p>
-<ul>
-<li>time-constrained region copying
-</li>
-<li><a href="/using-control-surfaces/midi-learn/">MIDI bindings</a> created by "learning" them from incoming MIDI
-</li>
-</ul>
-<p>You are strongly encouraged to invest in a 3 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>
<h2>Clicking</h2>
<p>Throughout this manual, the term "click" refers to the act of pressing and releasing the leftmost mouse button (technically identified as Button1, but your operating system may allow this to be reassigned). This action is used to select objects, activate buttons, turn on/off choices, popup menus and so forth.</p>
<p>On touch surfaces, it also corresponds to a regular, single-finger tap on the GUI.</p>
+
<h2>Right Clicking</h2>
<p>Throughout this manual, the term "right-click" refers to the act of pressing and releasing the rightmost mouse button (technically identified as Button2, but your operating system may allow this to be reassigned). This action is used to pop up "context menus" (hence the term "context click", which you will also see). It is also used by default in combination with the shift key for deleting objects within the editor window. 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.</p>
+
<h2>Middle Clicking</h2>
-<p>Throughout this manual, the term "middle-click" refers to the act of pressing and releasing the middle mouse button (technically identified as Button3, but your operating system may allow this to be reassigned). Not all all mice have a middle click button (see <a href="/setting-up-your-system/the-mouse/">the mouse</a> 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>Throughout this manual, the term "middle-click" refers to the act of pressing and releasing the middle mouse button (technically identified as Button3, but your operating system may allow this to be reassigned). Not all all mice have a middle click button (see <a href="/setting-up-your-system/mouse/">mouse</a> 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>
+
<h2>Double Clicking</h2>
<p>A "double click" refers to two rapid press/release actions on the leftmost mouse button. The time interval between the two press/release actions that determines whether this is seen as two clicks or one double click is controlled by your system preferences, not by Ardour.</p>
+
<h2>Drags</h2>
<p>Throughut this manual, the term "drag" primarily refers to the act of pressing the leftmost mouse button, then moving the mouse with the button held down, and then releasing the button. On touch surfaces, this term also corresponds to a normal single finger touch-motion-release action.</p>
<p>Ardour also uses the middle mouse button for certain kinds of drags, which will be referred to as "middle-drag" - these are identical to a normal drag except that they involve using the middle button rather than the left button.</p>
+
<h2>Modifiers</h2>
<p>There are many actions in Ardour that can be carried out using a mouse button in combination with a "modifier key". When the manual refers to Ctrl-click, it means that you should first press the Control key, then carry out a normal click while the Control key is held down, and then finally release the Control key. On Mac OS use Cmd-click instead. Available modifiers depend on the platform you are using Ardour on:</p>
+
<h3>Linux Modifiers</h3>
<ul>
<li>Control (Ctrl)
<li>Mod5</li>
</ul>
<p>Mod2 typically correspond to the NumLock key on many systems. On most Linux systems, there are no keys that will function as modifiers Mod3, Mod4 or Mod5 by default, but they can be setup using xmodmap(1). This can be rather useful.</p>
+
<h3>OS X Modifiers</h3>
<ul>
<li>Command (Cmd)
<li>Shift
</li>
</ul>
+
<h2>Scroll Wheel</h2>
<p>Ardour can make good use of a scroll wheel on your mouse, which can be utilized for a variety of purposes. Scroll wheels can generate both vertical scroll events (ScrollUp and ScrollDown) and/or horizontal events (ScrollLeft and ScrollRight). When appropriate, Ardour will differentiate between these two different scroll axes. Otherwise it will interpret ScrollDown and ScrollLeft as equivalent and similarly interpret ScrollUp and ScrollRight as equivalent. </p>
<p>Typically, scrolling is used to adjust continuous controls (e.g. faders/knobs), or to scroll vertically or horizontally.</p>
---
layout: default
-title: Getting To Know the Ranges & Marks List
+title: Ranges & Marks List
---
---
layout: default
-title: The Loop Range
+title: Loop Range
---
---
layout: default
-title: The Marker Context Menu
+title: Marker Context Menu
---
---
layout: default
-title: The Punch Range
+title: Punch Range
---
<li> a layer</li>
</ul>
<p>There are other attributes as well, but they do not define the region. Things you should know about regions:</p>
-<h3>Regions are Cheap</h3>
+
+<h3>Regions Are Cheap</h3>
<p>By themselves, regions consume very little of your computer's resources. Each region requires a small amount of memory, and represents a rather small amount of CPU work if placed into an active track. So, don't worry about creating regions whenever you need to.</p>
-<h3>Regions are not files</h3>
-<p>Although a region can represent an entire audio file, they are never equivalent to an audio file. Most regions represent just parts of an audio file(s) on disk, and removing a region from a track has nothing to do with removing the audio file(s) from the disk (the Destroy operation, one of Ardour's few destructive operations, can affect this). Changing the length of a region has no effect on the audio file(s) on disk. Splitting and copying regions does not alter the audio file in anyway, nor does it create new audio files (only recording, and the Export , Bounce and Reverse operations create new audio files).</p>
+
+<h3>Regions Are Not Files</h3>
+<p>Although a region can represent an entire audio file, they are never equivalent to an audio file. Most regions represent just parts of an audio file(s) on disk, and removing a region from a track has nothing to do with removing the audio file(s) from the disk (the Destroy operation, one of Ardour's few destructive operations, can affect this). Changing the length of a region has no effect on the audio file(s) on disk. Splitting and copying regions does not alter the audio file in anyway, nor does it create new audio files (only recording, and the Export, Bounce and Reverse operations create new audio files).</p>
<p>This chapter covers the following:</p>
<ul>
<li> the name of the playlist for which they were recorded
</li>
-<li> the name of the track for wich they were recorded
+<li> the name of the track for which they were recorded
</li>
<li> the name of the embedded/imported file they represent
</li>
<h3>Normal Region Names</h3>
<p>When a region is inserted into a track/playlist, its initial name will end in a version number, such as ".1" or ".103". For a recorded region, if the whole file region was "Hang drum-1", then the region in the track will appear with the name "Hang drum-1.1". For an imported/embedded region, if the whole file region was "Bach:Invention3", then the region in the track will appear with the name "Bach:Invention3.1".</p>
<h3>Copied Region Names</h3>
-<p>If the region is a copy of another region, it will begin life with the same name as the original. When an operation is carried out that modifies one of the copies, that particular copy will be renamed by incrementing the version number.</p>
+<p>If you copy a region, it initially shares the same name as the original. When you perform an operation modifies one of the copies, Ardour will increment the version number on the particular copy that changed.</p>
<h3>Renaming Regions</h3>
-<p>You can rename a region at any time. Use the region context menu to popup the rename dialog. The new name does not need to have a version number in it (in fact, it probably should not). The region will retain its name until it is modified after being copied.</p>
+<p>You can rename a region at any time. Use the region context menu to popup the Rename dialog. The new name does not need to have a version number in it (in fact, it probably should not). Ardour will add a version number in the future if needed (e.g. if you copy or split the region).</p>
- <p>Track Groups have a property titled "Select" which, if enabled, will cause Ardour to try to propagate a region selection in one of a group's member tracks to the other members of the group.. </p>
+ <p><a href="/working-with-tracks/track-and-bus-groups/">Track Groups</a> have a property titled "Select" which, if enabled, Ardour to tries to propagate a region selection in one of a group's member tracks to the other members of the group.. </p>
<p>For example, let's assume you have used multiple microphones to record a drum kit to multiple tracks. You have created a track group, added all the drum tracks, enabled the group and enabled the "Select" property for the group. When you select a region in one of the drum tracks, Ardour will select the corresponding track in every other drum track, which in turn means that a subsequent edit operation will affect all the selected regions (and thus all the drum tracks) together. </p>
-<h2>How Ardour decides which regions are "equivalent"</h2>
+
+<h2>How Ardour Decides Which Regions are "Equivalent"</h2>
<p>Regions in different tracks are considered to be equivalent for the purposes of sharing "selection" if they satisfy all the following criteria:</p>
<ol>
<li>Each region starts at the same offset within its source file</li>
<li>Each region is located at the same position on the timeline</li>
<li>Each region has the same length</li>
</ol>
+
<h2>Overlap Equivalence</h2>
-<p>Sometimes, the rules outlined above are too strict to get Ardour to do what you want. Regions may be slightly different lengths, or positioned slightly differently, and this will cause Ardour to not select regions in other grouped tracks that you would like it to.</p>
+<p>Sometimes, the rules outlined above are too strict to get Ardour to do what you want. Regions may be slightly different lengths, or positioned slightly differently, and this will cause Ardour to not select regions in other grouped tracks.</p>
<p>In this case, enable <code>Edit > Preferences > Editor > Use overlap equivalency for regions</code>. With this option enabled, regions in different tracks will be considered equivalent for the purposes of selection if they overlap. This is much more flexible and will cover almost all of the cases that the fixed rules above might make cumbersome.</p>
---
layout: default
-title: The Region Context Menu
+title: Region Context Menu
---
- <p>In the editor window, context clicking on a region brings up a menu to provide access to many region operations. The menu begins with the name of the region, or "Selected Regions" if multiple regions are selected.</p>
-<p> If there is more than
1 region layered at the point where you clicked, the menu will also contain an item "Choose Top" that if selected will show a dialog that allows you to adjust the layering of regions there. See <a href="manual/region_layering">Adjusting Region Layering</a> for more details.</p>
-<p>Below these items is the rest of the <a href="/working-with-tracks/the-track-context-menu">Track Context Menu</a>, which provides access to track-level operations. To see the region context menu's contents, select the region name or "Selected Regions", and a submenu will appear with the following structure/contents:</p>
+ <p>In the editor window, right clicking (context clicking) on a region displays a menu with many region operations. The menu begins with the name of the region, or "Selected Regions" if multiple regions are selected.</p>
+<p> If there is more than
one region layered at the point where you clicked, the menu will also contain an item "Choose Top." The "Choose Top" dialog lets you select which layer you want on top. See <a href="manual/region_layering">Adjusting Region Layering</a> for more details.</p>
+<p>Below these items is the rest of the <a href="/working-with-tracks/track-context-menu">Track Context Menu</a>, which provides access to track-level operations. To see the region context menu's contents, select the region name or "Selected Regions", and the following submenu structure appears:</p>
<dl class="narrower-table">
<dt>Play</dt>
<dd></dd>
-<p>All operations on playlists start by clicking on the playlist button (labelled p) in a track header in the editor window. Clicking the button will popup a menu with the following choices:</p>
+<p>In the track header (editor window, left pane) is a button labelled "p" (for "Playlist"). If you click on this button, Ardour displays the following menu:</p>
<dl class="wide-table">
<dt> (Local Playlists)</dt>
<dd> Shows all of the playlists associated with this track, and indicates the currently selected playlist</dd>
<dt>Rename</dt>
-<dd>Pops up a dialog that allows the current playlist to be renamed</dd>
+<dd>Displays a dialog to rename the current playlist</dd>
<dt>New</dt>
-<dd>Creates a new empty playlist, and switches this track to use it</dd>
+<dd>Creates a new empty playlist; and the track switches to the new playlist</dd>
<dt>New Copy</dt>
-<dd>Creates a new playlist that is a copy of the current playlist, and switches this track to use it</dd>
+<dd>Creates a new playlist that is a copy of the current playlist; and the track switches to the new playlist</dd>
<dt>Clear Current</dt>
<dd>Removes all regions from the current playlist</dd>
-<dt>Select from All</dt>
-<dd>pops up a playlist browser to manually choose which playlist this track should use ( you can even select playlists from other tracks here)</dd>
+<dt>Select From All</dt>
+<dd>Displays a playlist browser to manually choose which playlist this track should use. (You can even select playlists from other tracks here)</dd>
</dl>
<h3>Renaming Playlists</h3>
<p>Playlists are created with the name of the track of which they are associated, plus a version number. So, the first playlist for a track called "Cowbell" will be called "Cowbell.1". This name will be used to define the names of any regions added to the playlist by recording. You can change the name at any time, to anything you want. Ardour does not require that your playlist names are all unique, but it will make your life easier if they are. Suggested examples of user-assigned names for a playlist might include "Lead Guitar, 2nd take", "vocals (quiet)", and "downbeat cuica". Notice how these might be different from the associated track names, which for these examples might be "Lead Guitar", "Vocals" and "Cuica". The playlist name provides more information because it is about a specific version of the material that may (or may not) end up in the final version of the track.</p>
---
layout: default
-title: The Track Context Menu
+title: Track Context Menu
---
---
layout: default
-title: The Role of JACK
+title: Plugin Manager
---
---
layout: default
-title: The Processor Box
+title: Processor Box
---
---
layout: default
-title: The Import Dialog
+title: Import Dialog
---
---
layout: default
-title: The Patchbay
+title: Patchbay
---
---
layout: default
-title: The Plugin Manager
+title: Role of JACK
---
---
layout: default
-title: The Edit Point
+title: Edit Point
---
projects / ardour-manual-diverged / commitdiff