diff --git a/_manual/02_introducing-ardour/03_basic-gui-operations/02_selection-techniques.html b/_manual/02_introducing-ardour/03_basic-gui-operations/02_selection-techniques.html new file mode 100644 index 0000000..cf569ed --- /dev/null +++ b/_manual/02_introducing-ardour/03_basic-gui-operations/02_selection-techniques.html @@ -0,0 +1,57 @@ +--- +layout: default +title: Selection Techniques +--- + +
+ Ardour follows the conventions used by most other computer software + (including other DAWs) for selecting objects in the + GUI. +
+ ++ Clicking on an object (sometimes on a particular part of its + on-screen representation) will select the object, and deselect other + similar objects. +
+ ++ A left click on an object toggles its + selected status, so using left + on a series of objects will select (or deselect) each one of them. You can + construct completely arbitrary selections with this technique. +
+ ++ In cases where the idea of "select all objects between this one and that + one" makes sense, you can select one object and then click + left on another to select both of them as + well as all objects in between. +
+ ++ To select a time range in the Editor, + click Left and drag the mouse. + A Left drag then lets you create other + ranges and a left click extends a range + to cover a wider area. +
+ ++ The set of objects (including time range) that are selected at any one + time is known as the selection. + Each time you select or deselect an object, the new selection is stored in an + undo/redo stack. + This stack is cleared each time the content of the timeline changes. + If you have built up a complex selection and then accidentally cleared it, + choosing Edit > Undo Selection Change will restore your + previous selection. + If you then decide that you had in fact made the correct change, choosing + Edit > Redo Selection Change will take you back + to where you were before you chose Edit > Undo Selection Change. +
diff --git a/_manual/02_introducing-ardour/03_basic-gui-operations/03_tooltips.html b/_manual/02_introducing-ardour/03_basic-gui-operations/03_tooltips.html new file mode 100644 index 0000000..45699cd --- /dev/null +++ b/_manual/02_introducing-ardour/03_basic-gui-operations/03_tooltips.html @@ -0,0 +1,19 @@ +--- +layout: default +title: Tooltips +--- + ++ By default, Ardour will show helpful tooltips about + the purpose and use of each GUI element if you position the pointer + over it and hover there for a short while. + These little pop-up messages can be a good way to discover the + purpose of many aspects of the GUI. +
++ Pop-ups can be distracting for experienced users, who may opt to + disable them via Edit > Preferences > GUI > + Show tooltip if mouse hovers over a control. +
+ diff --git a/_manual/02_introducing-ardour/03_basic-gui-operations/04_undoredo-for-editing-.html b/_manual/02_introducing-ardour/03_basic-gui-operations/04_undoredo-for-editing-.html new file mode 100644 index 0000000..4b03fdf --- /dev/null +++ b/_manual/02_introducing-ardour/03_basic-gui-operations/04_undoredo-for-editing-.html @@ -0,0 +1,36 @@ +--- +layout: default +title: Undo/Redo for Editing +--- + ++ While editing, it happens that you apply an unintended change, or make + a choice one that you later decide was wrong. All changes to the + arrangement of session components (regions, control points) along the + timeline can be undone (and redone if necessary). +
++ The default keybindings are Z for Undo and + R for Redo. These match the conventions of most + other applications that provide undo/redo. +
++ Changes are also saved to the session history file, so that + undo/redo is possible even if you close the session and reopen it later, + even if you quit Ardour in between. +
++ The maximum number of changes that can be undone can be configured under + Edit > Preferences > Misc > Undo. + The maximum number of changes stored in the history file is a separate + parameter, and can also be set in the same place. +
+ ++ In addition to the normal undo (which works only on actions that change + the timeline), there is a visual undo which will revert any + command that affects the display of the editor window. Its shortcut is + Z. + There is also an undo for selection. See + Selection Techniques for more information. +
diff --git a/_manual/02_introducing-ardour/03_basic-gui-operations/05_using-the-mouse.html b/_manual/02_introducing-ardour/03_basic-gui-operations/05_using-the-mouse.html new file mode 100644 index 0000000..10f1c25 --- /dev/null +++ b/_manual/02_introducing-ardour/03_basic-gui-operations/05_using-the-mouse.html @@ -0,0 +1,126 @@ +--- +layout: default +title: Using the Mouse +--- + +
+ Throughout this manual, the term click refers to the act of pressing
+ and releasing the Left mouse button. This action is used to select objects, activate
+ buttons, turn choices on and off, pop up menus and so forth.
+ On touch surfaces, it also corresponds to a single, one-finger tap on
+ the GUI.
+
+ The term right-click refers to the act of pressing and releasing + the Right mouse button. + 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 to delete objects within the editor + window. +
++ Some mice designed for use with Mac OS X may have only one button. By + convention, pressing and holding the Control key while clicking is + interpreted as a right-click by many application.. +
+ ++ A middle-click refers to the act of pressing and releasing the + Middle mouse button. Not all all mice have a middle click button + (see the Mouse chapter 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. +
++ Internally, your operating system may identify the mouse buttons as + Button1, Button2, and + Button3, respectively. It may be possible to + invert the order of buttons to accommodate left-handed users, or to re-assign + them arbitrarily. This manual assumes the canonical order. +
+ ++ A double click refers to two rapid press/release cycles on the + leftmost mouse button. The time interval between the two actions that + determines whether this is seen as two clicks or one double click is + controlled by your system preferences, not by Ardour. +
+ ++ A drag primarily refers to the act of pressing the leftmost + mouse button, moving the mouse with the button held down, and then + releasing the button. On touch surfaces, this term also corresponds to + a single one-finger touch-move-release action. +
++ Ardour also uses the middle mouse button for certain kinds of drags, + which will be referred to as middle-drag. +
+ ++ 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 Left, it means that you should first + press the key, carry out a left click + while is held down, and then finally release the key. +
++ Available modifiers depend on your platform: +
++ The following section is almost certainly wrong. Will need to be checked + and rewritten asap. +
++ Mod2 typically corresponds 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 generate vertical + scroll events, ⇑ (ScrollUp) and + ⇓ (ScrollDown). Some also emit 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, scroll wheel input is used to adjust + continuous controls such as faders and knobs, or to scroll + vertically or horizontally inside a window. +
+ diff --git a/_manual/02_introducing-ardour/03_basic-gui-operations/06_cut-and-paste-operations.html b/_manual/02_introducing-ardour/03_basic-gui-operations/06_cut-and-paste-operations.html new file mode 100644 index 0000000..01d8571 --- /dev/null +++ b/_manual/02_introducing-ardour/03_basic-gui-operations/06_cut-and-paste-operations.html @@ -0,0 +1,35 @@ +--- +layout: default +title: Cut and Paste Operations +--- + ++ The clipboard is a holder for various kinds of objects (regions, + control events, plugins) that is used during cut-and-paste + operations. +
+ +
+ A cut operation removes selected objects and places them in the
+ clipboard. The existing contents of the clipboard are overwriten.
+ The default key binding is x.
+
+ A copy of the selected objects are placed in clipboard. There is
+ no effect on the selected objects themselves. The existing contents of the
+ clipboard are overwritten.
+ The default key binding is c.
+
+ The current contents of the clipboard are pasted (inserted)
+ into the session, using the current edit point as the
+ destination. The contents of the clipboard remain unchanged — you
+ can paste the same item multiple times.
+ The default key binding is v.
+
+ Within the Editor window (and to some extent within the Mixer window too), + there are several techniques for deleting objects (regions, + control points, and more). +
+ ++ Select the object(s) and then press the Del key. + This does not put the deleted object(s) into the cut + buffer, so they cannot be pasted elsewhere. +
+ ++ Select the object(s) and then press x. This puts + the deleted object(s) into the cut buffer so that they could be pasted + elsewhere. +
+ ++ By default, Shift Right will delete the + clicked-upon object. Like the Del key, this does not + put the deleted object(s) into the cut buffer. +
++ The modifier and mouse button used for this can be controlled via + Edit > Preferences > User Interaction > + Delete using .... Any modifier and mouse button combination can + be used. +
+ diff --git a/_manual/05_ardours-interface/01_main-menu/02_Transport-menu.html b/_manual/05_ardours-interface/01_main-menu/02_Transport-menu.html index e82e7d4..0bdc935 100644 --- a/_manual/05_ardours-interface/01_main-menu/02_Transport-menu.html +++ b/_manual/05_ardours-interface/01_main-menu/02_Transport-menu.html @@ -12,7 +12,7 @@ title: The Transport Menu+ A mixer strip in Ardour is a vertical view of the track, from a mixing point of view. + This view is convenient to deal with I/O, effects, panning/muting, gain, etc... It has a general + "top to bottom" flow. +
++ The mixer strips breaks down into : +
++ At the top of the window, is the group tabs (here, recm...). + This allows to group tracks together for common controls. +
++ Bellow are 3 buttons : +
++ Right clicking on the color bar will bring up a context menu, which is exactly the same as clicking on the Track name button. +
+ ++ Clicking the Track name button will bring up a menu : +
++ The dropdown button shows the current input port(s), i.e. what's plugged to the "in" of the track. + By default, each audio track is connected to the system inputs, ready for recording, + as shown by the number(s). + Clicking the dropdown Inputs button will allow to change the inputs, through a menu: +
++ The Routing Grid can also be shown by right clicking the dropdown Inputs button. + It allows to make the connections through a matrix, and connect things that are not listed in the menu above, + or connect to multiple sources at once, reduce the number of inputs, etc... +
++ On audio tracks, is a Trim knob, as on traditional consoles. + It set the base input level for the track, avoiding any clipping. Notice that it + trims both any input, but (when playing back), also the level of the playlist as + displayed in the Editor. It makes sense as while playing, the input of the track is + the playlist, on which the mixer strip acts. +
++ On midi tracks, it is replaced by a MIDI Input button, that allows/disallows + MIDI input on the track. +
+ + ++ On audio tracks only, the Polarity button(s), 1 per input, allow to reverse + the signal, i.e. a negative value will be positive and vice-versa. This can + help deal with phasing issues. +
+ ++ The processor box is where the effects are added. By default, one effect is always + present : the Fader (see bellow). The effects can be added pre-fader and appear in brown, + or post-fader, where they will appear in dark green. The signal flow is represented by lines, + red for the MIDI and green for the audio. +
++ It is also where the Sends come from, wether external or auxiliary. +
++ To learn more about the processor box, see The Processor Box. +
+ ++ The Panner visually displays how the sound will be distributed between the different outputs. + They'll look and behave differently if the track is mono, stereo, or has multiple channels. +
++ Right clicking the Panner will show a menu: +
++ See Panning to learn more about how to control the panner, + and what kind of panners are available inside Ardour. +
+ ++ The most noticeable button here is the Record Enable one, with a red circle. When + enabled, next time the Global record will be armed and playback started, everything that + comes from the input of the track will be recorded. Right clicking a disabled record + button allows to enable Rec-Safe, thus protecting the track + against accidental recording. +
++ The buttons on the right, In and Disk, + show what the user is listening to by lighting up, between the Input and the + actual content of the playlist on Disk. +
++ They also allow to override the automatic switching by pressing them to lock one + source or the other to be what the user is hearing. +
+ ++ These buttons allow to Mute (or silence) the track, or Solo them, shutting down the + gain of the other tracks (totally by default, can be set to partially in the options). + See Muting and Soloing + for more information. +
++ Notice that by default, Solo overrides Mute, i.e. if a track is both Soloed and Muted, it will + play. That can be changed in the preferences. +
++ The two led button above are related to solo : +
++ On the right of this part is a Meter, displaying the level of the track's + output after the fader. In can be set to display the signal at any point, see below Metering Point. + Right clicking this meter shows a menu allowing to switch the meter type. +
++ The big Gain slider on the left allows to change the gain of the track. Its default O dB + value is reminded with a white horizontal line, and its precise value is shown + in a text field above it, that doubles as a way to type in a numeric value. +
++ The text field above the meter shows the "Peak", i.e. the mawimum value that has been + reached during playback. To avoid distortion, the value should stay bellow O dB, and + if it goes above this value, the text field will turn red. Clicking on this field + will reset the Peak value (for a new measurement or a new part of the track). +
+ ++ Notice that if any gain automation has been set and the automation state is set on "Play" + (see below), then the Gain fader is driven by the automation, and not by the user. The Gain fader will + turn grey to show it's inactive. +
+ ++ If at least one control master exists, this button will show up, allowing the user + to link this track to any control master. +
++ Clicking the button lists all the available control masters, and a menu option to + Unassign all. Notice that a track can have be a slave to as many + control masters as they are in the session, hence multiplying the number of C.M. buttons. + The displayed number is the number of the Control Master, not the count of C.M. linked + to the track. A track with no control master assigned will show a unique button with a + "-vca-" label instead of this number. +
+ ++ This button allows to choose the mode used regarding automation: +
++ This button displays the mix group information as does the tab in the header (see above). + It is convenient though, as it allows to quickly switch the track from one + group to another with a drop down menu, also allowing to affect the track to + a non-adjascent group (which the tab won't easily allow). +
+ ++ The metering displayed in the meter is by default is 'Post', i.e. Post fader. + It can be changed with this button to Any point of the signal flow : +
++ This button is exactly the same as the Input button, but applies to the output + of the track. +
+ + ++ This buttons open up a little text editor, that can be used to add some written notes to the track, + as e.g. a particular setting. The button's caption is replaced by the beginning of the text, so + it can be used as a "sub"name for the track. +
diff --git a/_manual/05_ardours-interface/05_the-mixer/04_the-master-strip.html b/_manual/05_ardours-interface/05_the-mixer/05_the-master-strip.html similarity index 100% rename from _manual/05_ardours-interface/05_the-mixer/04_the-master-strip.html rename to _manual/05_ardours-interface/05_the-mixer/05_the-master-strip.html diff --git a/_manual/05_ardours-interface/05_the-mixer/05_monitoring.html b/_manual/05_ardours-interface/05_the-mixer/06_monitoring.html similarity index 100% rename from _manual/05_ardours-interface/05_the-mixer/05_monitoring.html rename to _manual/05_ardours-interface/05_the-mixer/06_monitoring.html diff --git a/source/images/mixer-1-strip-numbered.png b/source/images/mixer-1-strip-numbered.png new file mode 100644 index 0000000..81b18f4 Binary files /dev/null and b/source/images/mixer-1-strip-numbered.png differ