From 869e349668042b358579df95b0413af0f4c516f7 Mon Sep 17 00:00:00 2001 From: David Bolton Date: Wed, 3 Jul 2013 00:07:29 -0500 Subject: [PATCH] drop initial 'the' from pages and menu items --- .../03_setting-up-your-system/02_mouse.html | 19 +++++++++++++++++++ .../02_the-mouse.html | 19 ------------------- .../06_using-the-mouse.html | 10 +++++++++- ...rks-list.html => 03_rangesmarks-list.html} | 2 +- ...the-loop-range.html => 05_loop-range.html} | 2 +- ...-menu.html => 06_marker-context-menu.html} | 2 +- ...e-punch-range.html => 07_punch-range.html} | 2 +- _manual/08_working-with-regions.html | 8 +++++--- .../01_region-naming.html | 6 +++--- .../02_region-selection-equivalence.html | 8 +++++--- ...-menu.html => 03_region-context-menu.html} | 8 ++++---- .../01_playlist-operations.html | 12 ++++++------ ...t-menu.html => 09_track-context-menu.html} | 2 +- .../02_plugin-manager.html} | 2 +- ...ocessor-box.html => 03_processor-box.html} | 2 +- ...port-dialog.html => 05_import-dialog.html} | 2 +- ...{07_the-patchbay.html => 07_Patchbay.html} | 2 +- .../08_role-of-jack.html} | 2 +- ...the-edit-point.html => 01_edit-point.html} | 2 +- 19 files changed, 62 insertions(+), 50 deletions(-) create mode 100644 _manual/03_setting-up-your-system/02_mouse.html delete mode 100644 _manual/03_setting-up-your-system/02_the-mouse.html rename _manual/06_working-with-markers/{03_getting-to-know-the-rangesmarks-list.html => 03_rangesmarks-list.html} (98%) rename _manual/06_working-with-markers/{05_the-loop-range.html => 05_loop-range.html} (93%) rename _manual/06_working-with-markers/{06_the-marker-context-menu.html => 06_marker-context-menu.html} (97%) rename _manual/06_working-with-markers/{07_the-punch-range.html => 07_punch-range.html} (92%) rename _manual/08_working-with-regions/{03_the-region-context-menu.html => 03_region-context-menu.html} (78%) rename _manual/10_working-with-tracks/{09_the-track-context-menu.html => 09_track-context-menu.html} (98%) rename _manual/{14_signal-routing/08_the-role-of-jack.html => 11_working-with-plugins/02_plugin-manager.html} (70%) rename _manual/11_working-with-plugins/{03_the-processor-box.html => 03_processor-box.html} (98%) rename _manual/12_adding-pre-existing-material/{05_the-import-dialog.html => 05_import-dialog.html} (91%) rename _manual/14_signal-routing/{07_the-patchbay.html => 07_Patchbay.html} (99%) rename _manual/{11_working-with-plugins/02_the-plugin-manager.html => 14_signal-routing/08_role-of-jack.html} (69%) rename _manual/15_editing-and-arranging/{01_the-edit-point.html => 01_edit-point.html} (98%) diff --git a/_manual/03_setting-up-your-system/02_mouse.html b/_manual/03_setting-up-your-system/02_mouse.html new file mode 100644 index 00000000..dc72f1a9 --- /dev/null +++ b/_manual/03_setting-up-your-system/02_mouse.html @@ -0,0 +1,19 @@ +--- +layout: default +title: Mouse +--- + + + + +

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 Mouse

Clicking

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.

On touch surfaces, it also corresponds to a regular, single-finger tap on the GUI.

+

Right Clicking

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.

+

Middle 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

+

Double Clicking

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.

+

Drags

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.

+

Modifiers

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:

+

Linux Modifiers

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.

+

OS X Modifiers

+

Scroll Wheel

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 Regions
  • a layer

    • There are other attributes as well, but they do not define the region. Things you should know about regions:

    -

    Regions are Cheap

    + +

    Regions Are Cheap

    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.

    -

    Regions are not 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).

    + +

    Regions Are Not 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 Naming