Ardour is designed to work best with a three button mouse equipped with a scroll wheel.
+It can be used with a two button mouse or touchpad, but at least two key operations will not (easily) be available to you:
+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.
+ +For more detailed instructions see Using the mouse.
diff --git a/_manual/03_setting-up-your-system/02_the-mouse.html b/_manual/03_setting-up-your-system/02_the-mouse.html deleted file mode 100644 index 9e7b1523..00000000 --- a/_manual/03_setting-up-your-system/02_the-mouse.html +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: default -title: The Mouse ---- - - - - -Ardour is designed to work best with a 3 button mouse equipped with a scroll wheel.
-It can be used with a 2 button mouse or touchpad, but at least 2 key operations will not (easily) be available to you:
-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.
- -For more detailed instructions see Using the mouse.
diff --git a/_manual/04_ardours-interface/02_basic-gui-operations/06_using-the-mouse.html b/_manual/04_ardours-interface/02_basic-gui-operations/06_using-the-mouse.html index 23e2a9da..27f53e0d 100644 --- a/_manual/04_ardours-interface/02_basic-gui-operations/06_using-the-mouse.html +++ b/_manual/04_ardours-interface/02_basic-gui-operations/06_using-the-mouse.html @@ -8,17 +8,23 @@ title: Using the MouseThroughout 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.
On touch surfaces, it also corresponds to a regular, single-finger tap on the GUI.
+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.
+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 the mouse 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
+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 mouse 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
+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.
+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.
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.
+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:
+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.
+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.
Typically, scrolling is used to adjust continuous controls (e.g. faders/knobs), or to scroll vertically or horizontally.
diff --git a/_manual/06_working-with-markers/03_getting-to-know-the-rangesmarks-list.html b/_manual/06_working-with-markers/03_rangesmarks-list.html similarity index 98% rename from _manual/06_working-with-markers/03_getting-to-know-the-rangesmarks-list.html rename to _manual/06_working-with-markers/03_rangesmarks-list.html index 517d40c1..8982b7e0 100644 --- a/_manual/06_working-with-markers/03_getting-to-know-the-rangesmarks-list.html +++ b/_manual/06_working-with-markers/03_rangesmarks-list.html @@ -1,6 +1,6 @@ --- layout: default -title: Getting To Know the Ranges & Marks List +title: Ranges & Marks List --- diff --git a/_manual/06_working-with-markers/05_the-loop-range.html b/_manual/06_working-with-markers/05_loop-range.html similarity index 93% rename from _manual/06_working-with-markers/05_the-loop-range.html rename to _manual/06_working-with-markers/05_loop-range.html index a7e39255..95f50f71 100644 --- a/_manual/06_working-with-markers/05_the-loop-range.html +++ b/_manual/06_working-with-markers/05_loop-range.html @@ -1,6 +1,6 @@ --- layout: default -title: The Loop Range +title: Loop Range --- diff --git a/_manual/06_working-with-markers/06_the-marker-context-menu.html b/_manual/06_working-with-markers/06_marker-context-menu.html similarity index 97% rename from _manual/06_working-with-markers/06_the-marker-context-menu.html rename to _manual/06_working-with-markers/06_marker-context-menu.html index e4b7f346..a6f3bd99 100644 --- a/_manual/06_working-with-markers/06_the-marker-context-menu.html +++ b/_manual/06_working-with-markers/06_marker-context-menu.html @@ -1,6 +1,6 @@ --- layout: default -title: The Marker Context Menu +title: Marker Context Menu --- diff --git a/_manual/06_working-with-markers/07_the-punch-range.html b/_manual/06_working-with-markers/07_punch-range.html similarity index 92% rename from _manual/06_working-with-markers/07_the-punch-range.html rename to _manual/06_working-with-markers/07_punch-range.html index c60f4214..4d343acf 100644 --- a/_manual/06_working-with-markers/07_the-punch-range.html +++ b/_manual/06_working-with-markers/07_punch-range.html @@ -1,6 +1,6 @@ --- layout: default -title: The Punch Range +title: Punch Range --- diff --git a/_manual/08_working-with-regions.html b/_manual/08_working-with-regions.html index d06c47f6..a5a2c4a9 100644 --- a/_manual/08_working-with-regions.html +++ b/_manual/08_working-with-regions.html @@ -21,10 +21,12 @@ title: Working With RegionsThere are other attributes as well, but they do not define the region. Things you should know about regions:
-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.
-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).
+ +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).
This chapter covers the following:
diff --git a/_manual/08_working-with-regions/01_region-naming.html b/_manual/08_working-with-regions/01_region-naming.html index df299d9c..9b202671 100644 --- a/_manual/08_working-with-regions/01_region-naming.html +++ b/_manual/08_working-with-regions/01_region-naming.html @@ -10,7 +10,7 @@ title: Region NamingWhen 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".
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.
+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.
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.
+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).
diff --git a/_manual/08_working-with-regions/02_region-selection-equivalence.html b/_manual/08_working-with-regions/02_region-selection-equivalence.html index d1da7e46..eea654b3 100644 --- a/_manual/08_working-with-regions/02_region-selection-equivalence.html +++ b/_manual/08_working-with-regions/02_region-selection-equivalence.html @@ -5,16 +5,18 @@ title: Region Selection Equivalence -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..
+Track Groups 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..
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.
-Regions in different tracks are considered to be equivalent for the purposes of sharing "selection" if they satisfy all the following criteria:
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.
+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.
In this case, enable Edit > Preferences > Editor > Use overlap equivalency for regions. 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.
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.
-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 Adjusting Region Layering for more details.
-Below these items is the rest of the Track Context Menu, 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:
+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.
+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 Adjusting Region Layering for more details.
+Below these items is the rest of the Track Context Menu, 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:
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:
+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:
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.
diff --git a/_manual/10_working-with-tracks/09_the-track-context-menu.html b/_manual/10_working-with-tracks/09_track-context-menu.html similarity index 98% rename from _manual/10_working-with-tracks/09_the-track-context-menu.html rename to _manual/10_working-with-tracks/09_track-context-menu.html index 64bb9ab6..ea59c1c9 100644 --- a/_manual/10_working-with-tracks/09_the-track-context-menu.html +++ b/_manual/10_working-with-tracks/09_track-context-menu.html @@ -1,6 +1,6 @@ --- layout: default -title: The Track Context Menu +title: Track Context Menu --- diff --git a/_manual/14_signal-routing/08_the-role-of-jack.html b/_manual/11_working-with-plugins/02_plugin-manager.html similarity index 70% rename from _manual/14_signal-routing/08_the-role-of-jack.html rename to _manual/11_working-with-plugins/02_plugin-manager.html index 7355bb2b..ff10ca06 100644 --- a/_manual/14_signal-routing/08_the-role-of-jack.html +++ b/_manual/11_working-with-plugins/02_plugin-manager.html @@ -1,6 +1,6 @@ --- layout: default -title: The Role of JACK +title: Plugin Manager --- diff --git a/_manual/11_working-with-plugins/03_the-processor-box.html b/_manual/11_working-with-plugins/03_processor-box.html similarity index 98% rename from _manual/11_working-with-plugins/03_the-processor-box.html rename to _manual/11_working-with-plugins/03_processor-box.html index 577aa329..9a98abdb 100644 --- a/_manual/11_working-with-plugins/03_the-processor-box.html +++ b/_manual/11_working-with-plugins/03_processor-box.html @@ -1,6 +1,6 @@ --- layout: default -title: The Processor Box +title: Processor Box --- diff --git a/_manual/12_adding-pre-existing-material/05_the-import-dialog.html b/_manual/12_adding-pre-existing-material/05_import-dialog.html similarity index 91% rename from _manual/12_adding-pre-existing-material/05_the-import-dialog.html rename to _manual/12_adding-pre-existing-material/05_import-dialog.html index 41155be6..09f88931 100644 --- a/_manual/12_adding-pre-existing-material/05_the-import-dialog.html +++ b/_manual/12_adding-pre-existing-material/05_import-dialog.html @@ -1,6 +1,6 @@ --- layout: default -title: The Import Dialog +title: Import Dialog --- diff --git a/_manual/14_signal-routing/07_the-patchbay.html b/_manual/14_signal-routing/07_Patchbay.html similarity index 99% rename from _manual/14_signal-routing/07_the-patchbay.html rename to _manual/14_signal-routing/07_Patchbay.html index d7b25c7a..afef05b9 100644 --- a/_manual/14_signal-routing/07_the-patchbay.html +++ b/_manual/14_signal-routing/07_Patchbay.html @@ -1,6 +1,6 @@ --- layout: default -title: The Patchbay +title: Patchbay --- diff --git a/_manual/11_working-with-plugins/02_the-plugin-manager.html b/_manual/14_signal-routing/08_role-of-jack.html similarity index 69% rename from _manual/11_working-with-plugins/02_the-plugin-manager.html rename to _manual/14_signal-routing/08_role-of-jack.html index 891a8059..34480953 100644 --- a/_manual/11_working-with-plugins/02_the-plugin-manager.html +++ b/_manual/14_signal-routing/08_role-of-jack.html @@ -1,6 +1,6 @@ --- layout: default -title: The Plugin Manager +title: Role of JACK --- diff --git a/_manual/15_editing-and-arranging/01_the-edit-point.html b/_manual/15_editing-and-arranging/01_edit-point.html similarity index 98% rename from _manual/15_editing-and-arranging/01_the-edit-point.html rename to _manual/15_editing-and-arranging/01_edit-point.html index 437b8691..1f0d32d8 100644 --- a/_manual/15_editing-and-arranging/01_the-edit-point.html +++ b/_manual/15_editing-and-arranging/01_edit-point.html @@ -1,6 +1,6 @@ --- layout: default -title: The Edit Point +title: Edit Point ---