From: Shamus Hammons
- Almost every available function in Ardour can be executed via a
- key binding 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.
-
- Existing key bindings in menus are listed on the right side of the
- menu items.
-
- To create a custom key binding for a menu item quickly, navigate to
- the relevant (sub-) menu, hover over the item with the mouse and press
- the desired combination of modifiers and key.
-
- Ardour will silently re-assign the binding if you use a key
- combination that is already in use, possibly removing a standard
- keyboard shortcut without warning you. That might lead to confusion
- when you ask other users for help, and they explain something in terms
- of a standard key binding, which will then have a completely
- different effect on your system.
-
- For a complete overview of all existing keyboard bindings, go to
- Window > Key Bindings. This widget will let
- you view and edit even those functions that are not available in the menu,
- and even remove key bindings altogether.
-
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).
+ 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
@@ -21,7 +21,7 @@ title: Undo/Redo for Editing
The maximum number of changes that can be undone can be configured under
- Edit > Preferences > Misc > Undo.
+ 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.
Key bindings for menu items
-Key binding editor
-
- Ardour is designed to work best with a three button mouse + Ardour is designed to work best with a three button mouse equipped with a scroll wheel.
@@ -22,8 +22,8 @@ title: Mouse 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. + For more detailed instructions, see + Using the mouse.
diff --git a/_manual/03_setting-up-your-system/08_starting-ardour.html b/_manual/03_setting-up-your-system/08_starting-ardour.html index 6dcc728..a04323f 100644 --- a/_manual/03_setting-up-your-system/08_starting-ardour.html +++ b/_manual/03_setting-up-your-system/08_starting-ardour.html @@ -1,22 +1,20 @@ --- layout: default title: Starting Ardour ---- - +--- +There are several ways of starting Ardour, which may vary depending on which platform you are using it.
- When Ardour is run for the very first time, a special dialog is displayed + When Ardour is run for the very first time, a special dialog is displayed that will ask you several questions about your setup. You will not be asked these questions again, but you can always modify your choices via the Edit > Preferences dialog. @@ -28,11 +26,11 @@ title: Starting Ardour program, like QjackCtl or Cadence.
- If you open Ardour without specifying an existing session it will display + If you open Ardour without specifying an existing session it will display the Session > New... dialog and the Audio/MIDI Setup dialog. - See New/Open Session Dialog for a description of those dialogs. + See New/Open Session Dialog for a description of those dialogs.
- +@@ -53,5 +51,3 @@ title: Starting Ardour To start Ardour with a new, named session:
Ardour5 -N /path/to/session - - 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 7e836b8..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 MenuDragging and dropping tracks inside the Strips List allows to reorganise the tracks in the session, - both in the Mixer and the Editor. + both in the Mixer and the Editor. Clicking a track scrolls the Mixer to show this track.
diff --git a/_manual/05_ardours-interface/05_the-mixer/04_audio-midi-mixer-strips.html b/_manual/05_ardours-interface/05_the-mixer/04_audio-midi-mixer-strips.html new file mode 100644 index 0000000..59ae1e6 --- /dev/null +++ b/_manual/05_ardours-interface/05_the-mixer/04_audio-midi-mixer-strips.html @@ -0,0 +1,286 @@ +--- +title: Audio/MIDI Mixer Strips +--- + + + +
+ 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/04_the-master-strip.html deleted file mode 100644 index 2b183be..0000000 --- a/_manual/05_ardours-interface/05_the-mixer/04_the-master-strip.html +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: The Master Strip ---- - - - -add content
- - - - - diff --git a/_manual/05_ardours-interface/05_the-mixer/05_busses-mixer-strips.html b/_manual/05_ardours-interface/05_the-mixer/05_busses-mixer-strips.html new file mode 100644 index 0000000..848a46d --- /dev/null +++ b/_manual/05_ardours-interface/05_the-mixer/05_busses-mixer-strips.html @@ -0,0 +1,87 @@ +--- +title: Audio/MIDI Busses Mixer Strips +--- + + + ++ An Ardour bus can be considered a virtual track, as in a track that doesn't have a playlist (so, no regions). + Its use is to "group" some audio signals to be treated the same way. One simple use case is to group all the audio tracks containing the different drums of a drumkit. Routing all the drums tracks outputs to a bus allows, once the different levels amongst the drums have been set, to adjust the global level of the drumkit in the mix. +
++ Bus usage goes way beyond this simple example though : busses, as tracks, can receive plugins for common audio treatment, and be routed themselves as needed. This makes for a very useful tool that is very commonly used both for musical purposes and computing ones : instead of using e.g. 10 discrete delay plugins on 10 different tracks, busses are often used as receivers of sends, and only 1 delay plugin is used on this bus, reducing the processing power needed. +
+ ++ Ardour supports 2 types of busses : Audio and MIDI. A MIDI bus differs from an audio bus just by: +
+
+ MIDI busses provide a particularly efficient workflow for virtual drumkits where the arrangement uses different MIDI tracks. + Moreover, busses with both Audio and MIDI inputs are well suited for vocoders and similar plugins, + where a MIDI signal controls an audio one. +
++ Adding any audio input to a MIDI bus transforms it into an audio bus. +
+ ++ Busses look and behave exactly like tracks, so they share nearly all of their controls. + The differences are : +
++ Clicking the Aux button makes every track that sends a signal to this bus through Aux sends blink in turquoise. + Right clicking this button brings up a menu: +
++ Depending on the user's workflow and the way busses are used, 2 possibilities exists : +
+ ++ Connecting the output(s) of a track to the input(s) of the bus sends all the audio/MIDI to the bus. In the mixer strip, select (at the bottom) the OUTPUT button (often, by default, "Master"), and in the list, choose the input of a bus. Note that only the bus able to receive this output will show up, e.g. a mono bus wont be able to be connected to the output of a stereo track). +
++ Obviously, doing so will (by default) disconnect the output from the Master's input, which means all the audio/MIDI will be routed to the bus. For more complex routing, the OUTPUT button allows to show the Routing Grid that allows to plug the output of the track to multiple outputs at once, be it busses, tracks, Master... The button will then reflect these multiple connections by showing a *number*, number being the number of connections made in the routing grid. +
+ +
+ This allows not to interrupt the natural flow of the signal, i.e. the track will still output to what its connected to (e.g. Master). The signal is "tapped" at the point of insertion of the send, to be sent to the bus. Right click where in the signal flow you want the send to happen, and select
+ By left-clicking the send meter, it is possible to adjust the amount of signal sent to the bus. This is often the way tracks are connected to an effect bus, like a Delay bus. +
+ ++ Busses can be plugged to other busses, through outputs or sends. Both example workflows discussed previously, i.e. busses for grouping tracks and busses for effects, can both coexist, as e.g. a "grouping" drum bus can have a send to a reverb bus, and be connected to a compressor bus. +
diff --git a/_manual/05_ardours-interface/05_the-mixer/06_control-masters.html b/_manual/05_ardours-interface/05_the-mixer/06_control-masters.html new file mode 100644 index 0000000..b8b0384 --- /dev/null +++ b/_manual/05_ardours-interface/05_the-mixer/06_control-masters.html @@ -0,0 +1,63 @@ +--- +title: Control Masters Mixer Strips +--- + + + ++ Although track/bus groups offer a certain + kind of grouped-control over gain, solo, mute and more, traditional mixing consoles have long had + group master channels ("VCAs") which allows to combine + both a single fader to control the group level while also allowing you to easily adjust the relative + levels inside the group. For large projects, this can make mixing much easier to control. +
++ Ardour implements those VCAs as Control Masters, in a way that allows to use either or both + of the conventions used on different traditionnal consoles for combining multiple masters: +
++A Control Master strip is made of (from top to bottom in the screenshot) : +
+ +Right-clicking the name button shows a context menus comprised of :
++ Connecting a track/bus/VCA to a VCA is as simple as clicking the VCA button that appears on any mixer strip + under the main fader and choosing the VCA to connect to. +
+ +The VCA button only shows up in mixer strips when at least one Control Master exists, i.e., a + Control Master must be created before connecting tracks to it.
+ ++ Clicking the VCA button shows all the Control Masters in the session, and any or all of this vca can be checked + to link them to the track, making this track controlled by multiple Control Masters. The track will then show + multiple VCA buttons. Disconnecting a Control MAste from a track is done by unchecking this Control Master in + the list that pops up, or clicking Unassign All to disconnect from all Control Masters at once. +
diff --git a/_manual/05_ardours-interface/05_the-mixer/07_the-master-bus-strip.html b/_manual/05_ardours-interface/05_the-mixer/07_the-master-bus-strip.html new file mode 100644 index 0000000..d00e9ba --- /dev/null +++ b/_manual/05_ardours-interface/05_the-mixer/07_the-master-bus-strip.html @@ -0,0 +1,21 @@ +--- +title: The Master Bus Strip +--- + + + ++ The Master strip in Ardour is very similar to the other busses mixer strips. + The list of differences is (from top to bottom): +
+ ++ The Master bus strip is allways fixed, at the right end of the mixer, regardless of the scrolling position. +
diff --git a/_manual/05_ardours-interface/05_the-mixer/05_monitoring.html b/_manual/05_ardours-interface/05_the-mixer/08_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/08_monitoring.html diff --git a/_manual/06_controlling-playback.html b/_manual/06_controlling-playback.html index 0dbbca6..d2a65e3 100644 --- a/_manual/06_controlling-playback.html +++ b/_manual/06_controlling-playback.html @@ -1,18 +1,18 @@ --- layout: default title: Controlling Playback ---- +---- The playhead is a vertical line with two arrows at each end + The playhead is a vertical line with two arrows at each end that indicates the current position of playback.
- Pressing P will set the playhead to the current position of + Pressing P will set the playhead to the current position of the pointer, if it is within the editor track area.
@@ -24,36 +24,36 @@ title: Controlling Playback- Click on either the primary or secondary transport clock and - edit their value + Click on either the primary or secondary transport clock and + edit their value to move the playhead to a specific position.
- Click Right on the marker and select either + Click Right on the marker and select either Locate to here or Play from - here. + here.
- Alternatively, place the pointer on the marker and press + Alternatively, place the pointer on the marker and press P to set the playhead.
- +- When the loop transport button is pressed, the playhead will - jump the start of the loop range, and continue to the end of that range + When the loop transport button is pressed, the playhead will + jump the start of the loop range, and continue to the end of that range before returning to the start and repeating. - While looping, a light green area is displayed in the time ruler over + While looping, a light green area is displayed in the time ruler over the tracks to show the loop range.
By default, looping is bound to the l key.
- For more information on defining and altering the loop range see + For more information on defining and altering the loop range see Loop Range Markers.
diff --git a/_manual/07_working-with-markers/01_creating-location-markers.html b/_manual/07_working-with-markers/01_creating-location-markers.html index 210ab8e..c002d07 100644 --- a/_manual/07_working-with-markers/01_creating-location-markers.html +++ b/_manual/07_working-with-markers/01_creating-location-markers.html @@ -1,18 +1,18 @@ --- layout: default title: Creating Location Markers ---- +---Location Markers appear in the Locations ruler at the top - of the timeline. The begin and end markers appear - automatically, but you can create custom markers at any position in a + of the timeline. The begin and end markers appear + automatically, but you can create custom markers at any position in a session.
To add a marker at the current playhead position, press Num-↵ (the Enter key on the numeric keypad). - Alternatively, use Transport > Markers > Add + Alternatively, use Transport > Markers > Add Mark from Playhead.
@@ -23,9 +23,9 @@ title: Creating Location Markers Marker and use the clock widget to set its position.
- For details see - Ranges & Marks + For details see + Ranges & Marks List - and Using + and Using Ardour Clock Displays.
diff --git a/_manual/07_working-with-markers/04_loop-range.html b/_manual/07_working-with-markers/04_loop-range.html index 556fc65..fae3a0e 100644 --- a/_manual/07_working-with-markers/04_loop-range.html +++ b/_manual/07_working-with-markers/04_loop-range.html @@ -1,16 +1,14 @@ --- layout: default title: The Loop Range ---- - +--- +The loop range is a special range that defines the start and end points for loop play, which can be enabled in the transport bar.
It can be defined via the timeline or the Ranges & Marks + href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/">Ranges & Marks list.
- - diff --git a/_manual/07_working-with-markers/05_marker-context-menu.html b/_manual/07_working-with-markers/05_marker-context-menu.html index f4dbb19..f8a7608 100644 --- a/_manual/07_working-with-markers/05_marker-context-menu.html +++ b/_manual/07_working-with-markers/05_marker-context-menu.html @@ -1,10 +1,10 @@ --- layout: default title: Marker Context Menu ---- +---- Right-clicking a marker in the timeline opens the + Right-clicking a marker in the timeline opens the marker context menu. From this menu, you can:
There are also a few options in Transport > Active - Mark. These options apply to the currently selected location marker, - and move it to a nearby region boundary, region sync point, or to the + Mark. These options apply to the currently selected location marker, + and move it to a nearby region boundary, region sync point, or to the playhead or mouse.
- diff --git a/_manual/07_working-with-markers/06_punch-range.html b/_manual/07_working-with-markers/06_punch-range.html index 3a4b2d5..ddd2126 100644 --- a/_manual/07_working-with-markers/06_punch-range.html +++ b/_manual/07_working-with-markers/06_punch-range.html @@ -1,16 +1,14 @@ --- layout: default title: Punch Range ---- - +--- +- The punch range is a special range used to define where + The punch range is a special range used to define where recording will start and/or stop during a punch.
- It can be defined on the timeline or in the - Ranges & Marks + It can be defined on the timeline or in the + Ranges & Marks list.
- - diff --git a/_manual/08_working-with-sessions/08_snapshots.html b/_manual/08_working-with-sessions/08_snapshots.html index 3440a6a..e28e17b 100644 --- a/_manual/08_working-with-sessions/08_snapshots.html +++ b/_manual/08_working-with-sessions/08_snapshots.html @@ -1,39 +1,38 @@ --- layout: default title: Snapshots ---- - +--- +- Sometimes you will want to save a snapshot of the current state of a session for possible + Sometimes you will want to save a snapshot of the current state of a session for possible use in the future. For example, you may be about to change the entire - arrangement of a piece, or drastically alter the signal processing, and + arrangement of a piece, or drastically alter the signal processing, and want a reference to come back to, should that not work out.
This is easily accomplished using Session >
- Snapshot.
- A small dialog will appear, allowing you to enter a name for the snapshot.
+ Snapshot.
+ A small dialog will appear, allowing you to enter a name for the snapshot.
The default name is based on the current date and time.
You can create any number of snapshots.
- Creating a snapshot does not modify your session, - nor does it save your session. Instead, it saves an alternate version - of the session, within the session folder. The snapshot shares all data - present in the session. -
+ Creating a snapshot does not modify your session, + nor does it save your session. Instead, it saves an alternate version + of the session, within the session folder. The snapshot shares all data + present in the session. +- After creating a snapshot, you can continue working on the session and - save it normally using Session > Save and any + After creating a snapshot, you can continue working on the session and + save it normally using Session > Save and any existing snapshots will remain unchanged.
If you are already working on a session and want to to switch to an - existing snapshot, navigate the Snapshots tab of the - Editor List. - Find the name of the snapshot in the list and click it. Ardour will switch + existing snapshot, navigate the Snapshot List. + Find the name of the snapshot in the list and click it. Ardour will switch to the snapshot. If there are unsaved changes in the current session, Ardour will ask what you want to do.
@@ -41,22 +40,21 @@ title: SnapshotsSince a snapshot is just another session file stored within the session - folder, you can specify that "version" when loading an existing session. - The browser in the "Open Session" dialog will show an expander arrow for + folder, you can specify that "version" when loading an existing session. + The browser in the "Open Session" dialog will show an expander arrow for sessions that have more than 1 session file (i.e. snapshots) present - — click on it to see the list, and then click on the name of the + — click on it to see the list, and then click on the name of the snapshot you want to load.
- Sometimes you may want to create a snapshot and then have all future - edits and modifications saved to that snapshot rather than the main + Sometimes you may want to create a snapshot and then have all future + edits and modifications saved to that snapshot rather than the main session. This is easily done using Session > Save - As. This does not create a new session folder, but saves your - session as a new snapshot and then switches the "current snapshot" - to the newly created one. All subsequent saves of the session will - be stored in this new snapshot, and existing snapshots (and the main - session) will be left unaffected. + As. This does not create a new session folder, but saves your + session as a new snapshot and then switches the "current snapshot" + to the newly created one. All subsequent saves of the session will + be stored in this new snapshot, and existing snapshots (and the main + session) will be left unaffected.
- diff --git a/_manual/11_working-with-tracks/03_adding-tracks-and-busses.html b/_manual/11_working-with-tracks/02_adding-tracks-and-busses.html similarity index 100% rename from _manual/11_working-with-tracks/03_adding-tracks-and-busses.html rename to _manual/11_working-with-tracks/02_adding-tracks-and-busses.html diff --git a/_manual/11_working-with-tracks/02_busses-and-vcas.html b/_manual/11_working-with-tracks/02_busses-and-vcas.html deleted file mode 100644 index b293353..0000000 --- a/_manual/11_working-with-tracks/02_busses-and-vcas.html +++ /dev/null @@ -1,121 +0,0 @@ ---- -layout: default -title: Busses and VCAs ---- - -- In order to ease the process of mixing, Ardour offers two tools traditionally found on hardware mixing consoles : Busses and VCAs. -
- -- An Ardour bus can be considered a virtual track, as in a track that doesn't have a playlist (so, no regions). -
- -- Its use is to "group" some audio signals to be treated the same way. One simple use case is to group all the audio tracks containing the different drums of a drumkit. Routing all the drums tracks outputs to a bus allows, once the different levels amongst the drums have been set, to adjust the global level of the drumkit in the mix. -
- -- Bus usage goes way beyond this simple example though : busses, as tracks, can receive plugins for common audio treatment, and be routed themselves as needed. This makes for a very useful tool that is very commonly used both for musical purposes and computing ones : instead of using e.g. 10 discrete delay plugins on 10 different tracks, busses are often used as receivers of sends, and only 1 delay plugin is used on this bus, reducing the processing power needed. -
- -Note that the Master strip, which by default receives the output from all tracks, is a bus itself.
- -- Ardour supports 2 types of busses : Audio and MIDI. A MIDI bus differs from an audio bus just by its input (which is 1 midi input instead of n audio), the fact that you can put an instrument on it at creation time, whereas you can't easily add an instrument to an audio bus. -
- -- MIDI busses provide a particularly efficient workflow for virtual drumkits where the arrangement uses different MIDI tracks. Moreover, busses with both Audio and MIDI inputs are well suited for vocoders and similar plugins. -
- -- Depending on the user's workflow and the way busses are used, 2 possibilities exists : -
- -- Connecting the output(s) of a track to the input(s) of the bus sends all the audio/MIDI to the bus. In the mixer strip, select (at the bottom) the OUTPUT button (often, by default, "Master"), and in the list, choose the input of a bus. Note that only the bus able to receive this output will show up, e.g. a mono bus wont be able to be connected to the output of a stereo track). -
- -- Obviously, doing so will (by default) disconnect the output from the Master's input, which means all the audio/MIDI will be routed to the bus. For more complex routing, the OUTPUT button allows to show the Routing Grid that allows to plug the output of the track to multiple outputs at once, be it busses, tracks, Master... The button will then reflect these multiple connections by showing a *number*, number being the number of connections made in the routing grid. -
- -
- This allows not to interrupt the natural flow of the signal, i.e. the track will still output to what its connected to (e.g. Master). The signal is "tapped" at the point of insertion of the send, to be sent to the bus. Right click where in the signal flow you want the send to happen, and select
By left-clicking the send meter, it is possible to adjust the amount of signal sent to the bus. This is often the way tracks are connected to an effect bus, like a Delay bus. -
- -Busses can be plugged to other busses, through outputs or sends. Both example workflows discussed previously, i.e. busses for grouping tracks and busses for effects, can both coexist, as e.g. a "grouping" drum bus can have a send to a reverb bus, and be connected to a compressor bus. -
- - -- Reword this section to Control MAster, separate from Busses, Detail the fact a track can have multiple VCA attached -
- - - -- Although track/bus groups offer a certain kind of grouped-control over gain, solo, mute and more, traditional mixing consoles have long had group master channels ("VCAs") which allows to combine both a single fader to control the group level while also allowing you to easily adjust the relative levels inside the group. For large projects, this can make mixing much easier to control. -
- -- It allows to use either or both of the conventions for combining multiple masters: -
- --A VCA strip is made of (from top to bottom in the screenshot) : -
- -Right-clicking the name button shows a context menus comprised of :
- -- Connecting a track/bus/VCA to a VCA is as simple as clicking the VCA button on any mixer strip and choosing the VCA to connect to. -
- -The VCA button only shows up in mixer strips when at least 1 VCA exists, i.e., you have to first create a VCA before connecting it. -
diff --git a/_manual/11_working-with-tracks/04_selecting-tracks.html b/_manual/11_working-with-tracks/03_selecting-tracks.html similarity index 100% rename from _manual/11_working-with-tracks/04_selecting-tracks.html rename to _manual/11_working-with-tracks/03_selecting-tracks.html diff --git a/_manual/11_working-with-tracks/05_controlling-track-appearance.html b/_manual/11_working-with-tracks/04_controlling-track-appearance.html similarity index 100% rename from _manual/11_working-with-tracks/05_controlling-track-appearance.html rename to _manual/11_working-with-tracks/04_controlling-track-appearance.html diff --git a/_manual/11_working-with-tracks/06_controlling-track-ordering.html b/_manual/11_working-with-tracks/05_controlling-track-ordering.html similarity index 100% rename from _manual/11_working-with-tracks/06_controlling-track-ordering.html rename to _manual/11_working-with-tracks/05_controlling-track-ordering.html diff --git a/_manual/11_working-with-tracks/05_controlling-track-ordering/01_reordering-tracks.html b/_manual/11_working-with-tracks/05_controlling-track-ordering/01_reordering-tracks.html index 591ac9c..1d441ee 100644 --- a/_manual/11_working-with-tracks/05_controlling-track-ordering/01_reordering-tracks.html +++ b/_manual/11_working-with-tracks/05_controlling-track-ordering/01_reordering-tracks.html @@ -1,10 +1,10 @@ --- layout: default title: Reordering Tracks ---- +---- The track ordering of the Editor and Mixer is synchronized: if you + The track ordering of the Editor and Mixer is synchronized: if you reorder in one window, the ordering in the other window will follow.
@@ -17,10 +17,8 @@ title: Reordering Tracks (shortcut: ↓).- Alternatively, you can use the Tracks & Busses - panel of the - Editor - Lists, if visible. + Alternatively, you can use the Tracks & Busses + panel of the Editor Lists, if visible. Here, you can freely drag-and-drop tracks and busses into any order you prefer.
@@ -33,20 +31,19 @@ title: Reordering Tracks- Tracks and Busses that are members of a group can be reordered so that they - display contiguously within the Editor and Mixer windows. Context-click on + Tracks and Busses that are members of a group can be reordered so that they + display contiguously within the Editor and Mixer windows. Context-click on the group tab and choose Collect.
- When adding new tracks, the current selection determines their - placement. New tracks will be placed after the rightmost (in the mixer) or - bottom-most (in the editor) selected track. If no tracks are selected, new + When adding new tracks, the current selection determines their + placement. New tracks will be placed after the rightmost (in the mixer) or + bottom-most (in the editor) selected track. If no tracks are selected, new tracks will be added at the end.
- Because new tracks are automatically selected, you can quickly reorder them + Because new tracks are automatically selected, you can quickly reorder them in the editor window via the keyboard shortcuts after adding them (see above).
- diff --git a/_manual/11_working-with-tracks/07_bus-controls.html b/_manual/11_working-with-tracks/06_bus-controls.html similarity index 100% rename from _manual/11_working-with-tracks/07_bus-controls.html rename to _manual/11_working-with-tracks/06_bus-controls.html diff --git a/_manual/11_working-with-tracks/08_audio-track-controls.html b/_manual/11_working-with-tracks/07_audio-track-controls.html similarity index 100% rename from _manual/11_working-with-tracks/08_audio-track-controls.html rename to _manual/11_working-with-tracks/07_audio-track-controls.html diff --git a/_manual/11_working-with-tracks/09_midi-track-controls.html b/_manual/11_working-with-tracks/08_midi-track-controls.html similarity index 100% rename from _manual/11_working-with-tracks/09_midi-track-controls.html rename to _manual/11_working-with-tracks/08_midi-track-controls.html diff --git a/_manual/11_working-with-tracks/10_track-and-bus-groups.html b/_manual/11_working-with-tracks/09_track-and-bus-groups.html similarity index 78% rename from _manual/11_working-with-tracks/10_track-and-bus-groups.html rename to _manual/11_working-with-tracks/09_track-and-bus-groups.html index 9863de9..bcbced5 100644 --- a/_manual/11_working-with-tracks/10_track-and-bus-groups.html +++ b/_manual/11_working-with-tracks/09_track-and-bus-groups.html @@ -1,23 +1,23 @@ --- layout: default title: Track and Bus Groups ---- +---- Tracks and busses can be put into groups. Members of a group - can share various settings — useful for managing tracks that are closely - related to each other. Examples might include tracks that contain - multiple-microphone recordings of a single source (an acoustic guitar, + Tracks and busses can be put into groups. Members of a group + can share various settings — useful for managing tracks that are closely + related to each other. Examples might include tracks that contain + multiple-microphone recordings of a single source (an acoustic guitar, perhaps, or a drum-kit).
- You can group tracks and busses in various ways. In the editor window, + You can group tracks and busses in various ways. In the editor window, a track's controls might look like these:
-- The green tab to the left of the track header indicates that this track - is in a group called Fred. You can drag these tabs to add +
+ The green tab to the left of the track header indicates that this track + is in a group called Fred. You can drag these tabs to add adjacent tracks to a group.
@@ -27,54 +27,51 @@ title: Track and Bus GroupsContext-click on a group tab and select Remove - Group from the menu. Removing a group does not remove + Group from the menu. Removing a group does not remove the members of a group.
- You can also remove groups by selecting them in the Groups tab of the - Editor Lists - or Mixer Window and then pressing the minus (-) - button at the bottom of the list. + You can also remove groups by selecting them in the Groups list + and then pressing the minus (-) button at the bottom of the list.
- Click the g button to display a menu with a list - of the available groups. Select one of these groups to add the track or bus + Click the g button to display a menu with a list + of the available groups. Select one of these groups to add the track or bus to that group. Select No Group to remove it.
- Alternatively, you can also drag a group tab to add or remove tracks from + Alternatively, you can also drag a group tab to add or remove tracks from the group.
- Clicking on a group tab toggles the group between being active and inactive. - An inactive group has no effect when editing its members. An active group - will share its configured properties across its members. Tabs for disabled + Clicking on a group tab toggles the group between being active and inactive. + An inactive group has no effect when editing its members. An active group + will share its configured properties across its members. Tabs for disabled groups are coloured grey.
- To edit the properties of a group, context-click on its tab and choose - Edit Groupâ¦. This opens the track/bus group dialog, + To edit the properties of a group, context-click on its tab and choose + Edit Groupâ¦. This opens the track/bus group dialog, which is also used when creating new groups:
@@ -82,39 +79,39 @@ title: Track and Bus Groups- Click on the color selector button to change a group's colour. This affects - the colour of the group's tab in the editor and mixer windows. The color does - not affect the color of the group members unless you also enable the - shared Color property. + Click on the color selector button to change a group's colour. This affects + the colour of the group's tab in the editor and mixer windows. The color does + not affect the color of the group members unless you also enable the + shared Color property.
- Gain means that the track faders will be synced to - always have the same value; Relative means that the - gain changes are applied relative to each member's current value. If, for - example, there are two tracks in a group with relative gain sharing, and their - faders are set to -3 dB and -1 dB, a change of the first track to a + Gain means that the track faders will be synced to + always have the same value; Relative means that the + gain changes are applied relative to each member's current value. If, for + example, there are two tracks in a group with relative gain sharing, and their + faders are set to -3 dB and -1 dB, a change of the first track to a gain of -6 dB will result in the second track having a gain of -4 dB (the difference of the gains remains the same).
- Muting, - Soloing, - record enable, - active state, - colour and - monitoring - are all straightforward. They simply mean that all member tracks or busses will + Muting, + Soloing, + record enable, + active state, + colour and + monitoring + are all straightforward. They simply mean that all member tracks or busses will share the same settings in these respects.
- Selection means that if a region is selected or + Selection means that if a region is selected or deselected on one member track, corresponding - regions on other member tracks - will be similarly selected. Since region editing operations are applied to all - currently selected regions, this is the way to make edits apply across all tracks + regions on other member tracks + will be similarly selected. Since region editing operations are applied to all + currently selected regions, this is the way to make edits apply across all tracks in the group.
@@ -139,7 +136,7 @@ title: Track and Bus Groups- Within the editor window, context-click (right-click) on either a region - or empty space within a track to display the track context menu. + Within the editor window, context-click (right-click) on either a region + or empty space within a track to display the track context menu. The context menu provides easy access to many track-level operations.
- If you click on a region, the first item in the menu is the name of the - region. If you click on a - layered region, - the next item in the menu is Choose Top. If selected, - you will see a dialog that allows you to change the vertical order of layers + If you click on a region, the first item in the menu is the name of the + region. If you click on a + layered region, + the next item in the menu is Choose Top. If selected, + you will see a dialog that allows you to change the vertical order of layers at that point. See Layering Display for more details.
@@ -24,7 +24,7 @@ title: Track Context Menu
- Many sessions will require the use of existing material, - whether it consists of audio and/or MIDI data. Using existing samples, - loops and riffs from files stored on your system can be the basis for - a new session, or a way to deepen and improve one that is already - underway. + Many sessions will require the use of existing material, + whether it consists of audio and/or MIDI data. Using existing samples, + loops and riffs from files stored on your system can be the basis for + a new session, or a way to deepen and improve one that is already + underway.
- You can import audio and MIDI data into your session with the + You can import audio and MIDI data into your session with the Add Existing Media dialog.
@@ -47,13 +47,13 @@ title: Import DialogYou can import files into new, automatically created tracks, to the region - list (from where you can manually drag them into a track), or as new + list (from where you can manually drag them into a track), or as new Tape tracks with the - Add new files as... option. + Add new files as... option.
New files will be inserted at either the file timestamp (if available, - zero by default), at the edit point, at the + zero by default), at the edit point, at the playhead, or at the start of the session, as specified in Insert at....
@@ -69,7 +69,7 @@ title: Import DialogThe Conversion quality drop-down controls the quality of the resampling process, if the sampling rate of the source file - differs from the session rate. + differs from the session rate.
Finally, and most importantly, you can decide whether to - Many editing operations in Ardour require you to first select one or more - regions that you want to change in some way. You can select a single region, - or multiple regions, including regions in different tracks. When you select + Many editing operations in Ardour require you to first select one or more + regions that you want to change in some way. You can select a single region, + or multiple regions, including regions in different tracks. When you select a region, it will appear in a darker color than unselected regions.
Note that if a track is a member of a group that is active and has the - Select property enabled, then Ardour will attempt to - match whatever selections you make in one track across every other track of the - group. See + Select property enabled, then Ardour will attempt to + match whatever selections you make in one track across every other track of the + group. See Corresponding - Regions Selection for more information on precisely how selections will be + Regions Selection for more information on precisely how selections will be propagated to other tracks.
- Please read - Region & Track Selection + Please read + Region & Track Selection for more information on how selecting regions and selecting tracks interact.
- Confirm that you are using the - Object tool, - then click on a region to select it. If - smart mode + Confirm that you are using the + Grab Mode tool, + then click on a region to select it. If + Smart mode is enabled, click in the lower half of the region.
- Confirm you are using the - Object tool, - then Left-click the region. If - smart mode - is enabled, click in the lower half of the region. + Confirm you are using the + Grab Mode tool, + then Left-click the region. If + Smart mode + is enabled, click in the lower half of the region.
- Note that a left click simply toggles the + Note that a left click simply toggles the selected status of an object, so it can be used to select unselected regions too.
@@ -54,25 +54,25 @@ title: Select Regions- Context-click the track, and in the context menu, navigate to + Context-click the track, and in the context menu, navigate to Select > Select All In Track.
- See the Track Context Menu + See the Track Context Menu for more information on other per-track selection operations that are available.
@@ -84,9 +84,8 @@ title: Select Regions- Click the name of the region in the - Region List. - Note that this will do nothing for whole-file regions, since they do not exist + Click the name of the region in the + Region List. + Note that this will do nothing for whole-file regions, since they do not exist anywhere in a playlist or track.
- diff --git a/_manual/16_editing-and-arranging/03_common-region-edit-operations.html b/_manual/16_editing-and-arranging/03_common-region-edit-operations.html index d7eced2..3a3b28b 100644 --- a/_manual/16_editing-and-arranging/03_common-region-edit-operations.html +++ b/_manual/16_editing-and-arranging/03_common-region-edit-operations.html @@ -2,24 +2,24 @@ layout: default title: Common Region Edit Operations menu_title: Region Editing ---- +---This section covers a set of region editing operations - that you are likely to use often while working on a session. - Depending on your work habits (and experience of other - DAWs) you will find - some of these operations critical while others are used only rarely. + that you are likely to use often while working on a session. + Depending on your work habits (and experience of other + DAWs) you will find + some of these operations critical while others are used only rarely.
- You can carry out all of these operations from the keyboard (see - Default Keyboard Shortcuts - for a list). Equivalent operations can be performed with the mouse - in most cases. + You can carry out all of these operations from the keyboard (see + Default Keyboard Shortcuts + for a list). Equivalent operations can be performed with the mouse + in most cases.
- You may want to review your understanding of - the edit point/range and + You may want to review your understanding of + the edit point/range and which regions will be affected by region operations.
- Changing the length of a region is a very common editing - operation, often known as trimming. There are several ways - to accomplish this with Ardour, and some very useful specialized trimming + Changing the length of a region is a very common editing + operation, often known as trimming. There are several ways + to accomplish this with Ardour, and some very useful specialized trimming operations.
- In object mode, move the pointer near the beginning or end of the region. - The cursor will change to indicate that trimming is possible, and you then - Left-drag the edge of the region. + In object mode, move the pointer near the beginning or end of the region. + The cursor will change to indicate that trimming is possible, and you then + Left-drag the edge of the region.
- Trimming will obey Snap settings. + Trimming will obey Snap settings.
- Left-click in the colored bar at the bottom of a region. - If you are nearer to the start of a region, this will trim the start time to the - position of the pointer. If you are nearer to the end of a region, it will trim the + Left-click in the colored bar at the bottom of a region. + If you are nearer to the start of a region, this will trim the start time to the + position of the pointer. If you are nearer to the end of a region, it will trim the end time.
- There are several commands for region trimming. Some use the - edit point to determine where - to trim to. Some are not bound to any keys by default (but could be via the + There are several commands for region trimming. Some use the + edit point to determine where + to trim to. Some are not bound to any keys by default (but could be via the Keybindings Editor).
@@ -45,14 +45,14 @@ title: Trimming Regions- Sometimes you just want to extend the start or end of region so that it reaches - the end or start of an adjacent region. There is now an operation accessible + Sometimes you just want to extend the start or end of region so that it reaches + the end or start of an adjacent region. There is now an operation accessible from the region context menu, under Edit >Trim > Trim to - Next or Edit > Trim > Trim to Previous. This - will extend the selected regions so they directly adjoin their neighbours, unless - their source files are not long enough, in which case they will be extended to the - maximum possible. Trim to Next will extend the end of the selected regions to the - start of the next region; Trim to Previous will extend the start of the selected + Next or Edit > Trim > Trim to Previous. This + will extend the selected regions so they directly adjoin their neighbours, unless + their source files are not long enough, in which case they will be extended to the + maximum possible. Trim to Next will extend the end of the selected regions to the + start of the next region; Trim to Previous will extend the start of the selected regions to the end of the previous region.
- These are not bound to any keys by default, but could be via the Keybindings + These are not bound to any keys by default, but could be via the Keybindings Editor. They can also be sent via OSC or other control protocols.
Ardour has a global edit mode selector at the left of the @@ -25,13 +25,13 @@ title: Move Regions
- If Snap To Grid is enabled, then regions can - only move so that they align with locations determined by the current - snap settings (beats, or seconds, or other region boundaries, etc). - See Snap To the Grid + If Snap To Grid is enabled, then regions can + only move so that they align with locations determined by the current + snap settings (beats, or seconds, or other region boundaries, etc). + See Snap To the Grid for details.
- + {% children %} diff --git a/_manual/16_editing-and-arranging/06_move-regions/02_align-spotting-regions.html b/_manual/16_editing-and-arranging/06_move-regions/02_align-spotting-regions.html index f9b92cc..1f70363 100644 --- a/_manual/16_editing-and-arranging/06_move-regions/02_align-spotting-regions.html +++ b/_manual/16_editing-and-arranging/06_move-regions/02_align-spotting-regions.html @@ -1,13 +1,13 @@ --- layout: default title: Align (Spot) Regions ---- +---- Aligning regions (sometimes called "spotting") means moving one or more - regions based on a defined location, which in Ardour is always the - edit point. An - alignment operation moves the region(s) so that some part of the region + Aligning regions (sometimes called "spotting") means moving one or more + regions based on a defined location, which in Ardour is always the + edit point. An + alignment operation moves the region(s) so that some part of the region is positioned at the edit point. Available alignment commands include:
- A patch change is Ardour's description for a combination - of MIDI program change and bank select messages, that (typically) - instruct a synthesizer or sampler to select a different sound to use - on a particular channel. + A patch change is Ardour's description for a combination + of MIDI program change and bank select messages, that (typically) + instruct a synthesizer or sampler to select a different sound to use + on a particular channel.
- Patch changes are shown within MIDI regions as small rectangles or + Patch changes are shown within MIDI regions as small rectangles or flags, as shown below:
- Ensure that the - edit point is - located where you want the patch change to be (within an existing - MIDI region). Context click, and from the MIDI region's context menu, - select MIDI > Insert Patch Change. A - dialog will appear allowing you to set the bank and program values. + Ensure that the + edit point is + located where you want the patch change to be (within an existing + MIDI region). Context click, and from the MIDI region's context menu, + select MIDI > Insert Patch Change. A + dialog will appear allowing you to set the bank and program values.
- Context-clicking on a patch change will bring up the same dialog that - was used to create it, allowing you to modify the program and/or bank + Context-clicking on a patch change will bring up the same dialog that + was used to create it, allowing you to modify the program and/or bank numbers.
You can also use the mouse wheel: ⇑/⇓ on the patch change will alter the program - number, ⇑/⇓ on the patch change will alter the program + number, ⇑/⇓ will modify the bank number.
- Just Left-drag on the patch change to move it + Just Left-drag on the patch change to move it around.
- Put the mouse pointer into the rectangular area, and press Del - or use the delete mouse button operation. This will remove the patch change + Put the mouse pointer into the rectangular area, and press Del + or use the delete mouse button operation. This will remove the patch change (the operation can be undone).
diff --git a/_manual/19_exporting/02_edit-export-format-profile.html b/_manual/19_exporting/02_edit-export-format-profile.html index 342c41c..4a3288b 100644 --- a/_manual/19_exporting/02_edit-export-format-profile.html +++ b/_manual/19_exporting/02_edit-export-format-profile.html @@ -1,7 +1,7 @@ --- layout: default title: Export Format Profiles ---- +---As well as exporting an audio file, create a file (in CUE or TOC format respectively) containg CD track information, as defined in the -Ranges & Marks List. +Ranges & Marks List.
The 'Label' field lets you choose the name which will be shown for this format -in the drop-down list of export formats in the 'File Formats' tab of the +in the drop-down list of export formats in the 'File Formats' tab of the Export dialog.
Almost every available function in Ardour can be bound to a keyboard shortcut (and those few that cannot will usually respond to an OSC command). Ardour comes with a + title="Open Sound Control">OSC command). Ardour comes with a rich set of default key bindings for the most commonly used functions.
-These bindings strive to be mnemonic, that is, easy and intuitive - to remember, and follow widely accepted conventions. As a general rule, - the first letter of an operation will be used for as a shortcut, if - available. This does not necessarily lead to the best ergonomics for - rapid editing — there are alternative binding sets for that — - but it does make it simpler for newcomers to remember some of the most + +
These bindings strive to be mnemonic, that is, easy and intuitive
+ to remember, and follow widely accepted conventions. As a general rule,
+ the first letter of an operation will be used for as a shortcut, if
+ available. This does not necessarily lead to the best ergonomics for
+ rapid editing — there are alternative binding sets for that —
+ but it does make it simpler for newcomers to remember some of the most
useful ones, for example
S for Region > Edit > Split"
or
P for Transport > Playhead > Playhead to Mouse.
+ Existing key bindings in menus are listed on the right side of the + menu items. To create a custom key binding for a menu item quickly, navigate to + the relevant (sub-) menu, hover over the item with the mouse and press + the desired combination of modifiers and key. +
+ ++ Ardour will silently re-assign the binding if you use a key + combination that is already in use, possibly removing a standard + keyboard shortcut without warning you. That might lead to confusion + when you ask other users for help, and they explain something in terms + of a standard key binding, which will then have a completely + different effect on your system. +
+- Almost every key binding in Ardour can be changed in + Almost every key binding in Ardour can be looked for and/or changed in Window > Key Bindings.
+The conventions for using modifier keys ( , , etc.) differ among platforms, so we + class="mod2"> , etc.) differ among platforms, so we provide different default bindings for each.
+ {% children %} diff --git a/_manual/22_preferences-and-session-properties/01_preferences-dialog/01_misc.html b/_manual/22_preferences-and-session-properties/01_preferences-dialog/01_misc.html index 4817b3a..e013edb 100644 --- a/_manual/22_preferences-and-session-properties/01_preferences-dialog/01_misc.html +++ b/_manual/22_preferences-and-session-properties/01_preferences-dialog/01_misc.html @@ -103,7 +103,7 @@ misc tab"/>Click audio file: sets a user defined sound to be played when Ardour's metronome is enabled in the - + Transport Bar
diff --git a/_manual/22_preferences-and-session-properties/01_preferences-dialog/02_transport.html b/_manual/22_preferences-and-session-properties/01_preferences-dialog/02_transport.html index 15197ef..a000f9d 100644 --- a/_manual/22_preferences-and-session-properties/01_preferences-dialog/02_transport.html +++ b/_manual/22_preferences-and-session-properties/01_preferences-dialog/02_transport.html @@ -6,7 +6,7 @@ menu_title: Transport TabThis tab contains settings that relate to the behavior of the - Transport Bar + Transport Bar and Synchronization.
diff --git a/_manual/22_preferences-and-session-properties/01_preferences-dialog/07_interaction.html b/_manual/22_preferences-and-session-properties/01_preferences-dialog/07_interaction.html index e4c8e6f..51cfb4a 100644 --- a/_manual/22_preferences-and-session-properties/01_preferences-dialog/07_interaction.html +++ b/_manual/22_preferences-and-session-properties/01_preferences-dialog/07_interaction.html @@ -45,7 +45,7 @@ user interaction tab"/>Ignore snap using: This mouse and keyboard combination temporarily changes the - snap mode to + snap mode to No Grid.
diff --git a/_manual/22_preferences-and-session-properties/01_preferences-dialog/12_metering.html b/_manual/22_preferences-and-session-properties/01_preferences-dialog/12_metering.html index af1cd68..1d903fd 100644 --- a/_manual/22_preferences-and-session-properties/01_preferences-dialog/12_metering.html +++ b/_manual/22_preferences-and-session-properties/01_preferences-dialog/12_metering.html @@ -5,7 +5,7 @@ menu_title: Metering Tab ---- This tab contains settings that affect + This tab contains settings that affect Metering in Ardour.
diff --git a/master-doc.txt b/master-doc.txt index cb597bf..bb25ba8 100644 --- a/master-doc.txt +++ b/master-doc.txt @@ -90,45 +90,39 @@ include: _manual/02_introducing-ardour/03_basic-gui-operations/01_interface-elem part: subchapter --- ---- -title: Key Bindings -include: _manual/02_introducing-ardour/03_basic-gui-operations/02_key-bindings.html -part: subchapter ---- - --- title: Selection Techniques -include: _manual/02_introducing-ardour/03_basic-gui-operations/03_selection-techniques.html +include: _manual/02_introducing-ardour/03_basic-gui-operations/02_selection-techniques.html part: subchapter --- --- title: Tooltips -include: _manual/02_introducing-ardour/03_basic-gui-operations/04_tooltips.html +include: _manual/02_introducing-ardour/03_basic-gui-operations/03_tooltips.html part: subchapter --- --- title: Undo/Redo for Editing -include: _manual/02_introducing-ardour/03_basic-gui-operations/05_undoredo-for-editing-.html +include: _manual/02_introducing-ardour/03_basic-gui-operations/04_undoredo-for-editing-.html part: subchapter --- --- title: Using the Mouse -include: _manual/02_introducing-ardour/03_basic-gui-operations/06_using-the-mouse.html +include: _manual/02_introducing-ardour/03_basic-gui-operations/05_using-the-mouse.html part: subchapter --- --- title: Cut and Paste Operations -include: _manual/02_introducing-ardour/03_basic-gui-operations/07_cut-and-paste-operations.html +include: _manual/02_introducing-ardour/03_basic-gui-operations/06_cut-and-paste-operations.html part: subchapter --- --- title: Deleting Objects -include: _manual/02_introducing-ardour/03_basic-gui-operations/08_deleting-objects.html +include: _manual/02_introducing-ardour/03_basic-gui-operations/07_deleting-objects.html part: subchapter --- @@ -661,13 +655,31 @@ part: subchapter --- title: The Mixer - The Master Strip -include: _manual/05_ardours-interface/05_the-mixer/04_the-master-strip.html +include: _manual/05_ardours-interface/05_the-mixer/04_audio-midi-mixer-strips.htm +part: subchapter +--- + +--- +title: The Mixer - The Master Strip +include: _manual/05_ardours-interface/05_the-mixer/05_busses-mixer-strips.html +part: subchapter +--- + +--- +title: The Mixer - The Master Strip +include: _manual/05_ardours-interface/05_the-mixer/06_control-masters.html +part: subchapter +--- + +--- +title: The Mixer - The Master Strip +include: _manual/05_ardours-interface/05_the-mixer/07_the-master-bus-strip.html part: subchapter --- --- title: The Mixer - The Monitor Section -include: _manual/05_ardours-interface/05_the-mixer/05_monitoring.html +include: _manual/05_ardours-interface/05_the-mixer/08_monitoring.html part: subchapter --- @@ -813,19 +825,19 @@ part: subchapter --- title: Adding Tracks, Busses and VCAs -include: _manual/11_working-with-tracks/03_adding-tracks-and-busses.html +include: _manual/11_working-with-tracks/02_adding-tracks-and-busses.html part: subchapter --- --- title: Selecting Tracks -include: _manual/11_working-with-tracks/04_selecting-tracks.html +include: _manual/11_working-with-tracks/03_selecting-tracks.html part: subchapter --- --- title: Controlling Track Appearance -include: _manual/11_working-with-tracks/05_controlling-track-appearance.html +include: _manual/11_working-with-tracks/04_controlling-track-appearance.html part: subchapter --- @@ -855,7 +867,7 @@ part: subchapter --- title: Controlling Track Ordering -include: _manual/11_working-with-tracks/06_controlling-track-ordering.html +include: _manual/11_working-with-tracks/05_controlling-track-ordering.html part: subchapter --- @@ -873,25 +885,25 @@ part: subchapter --- title: Bus Controls -include: _manual/11_working-with-tracks/07_bus-controls.html +include: _manual/11_working-with-tracks/06_bus-controls.html part: subchapter --- --- title: Audio Track Controls -include: _manual/11_working-with-tracks/08_audio-track-controls.html +include: _manual/11_working-with-tracks/07_audio-track-controls.html part: subchapter --- --- title: MIDI Track Controls -include: _manual/11_working-with-tracks/09_midi-track-controls.html +include: _manual/11_working-with-tracks/08_midi-track-controls.html part: subchapter --- --- title: Track Context Menu -include: _manual/11_working-with-tracks/11_track-context-menu.html +include: _manual/11_working-with-tracks/10_track-context-menu.html part: subchapter --- @@ -903,7 +915,7 @@ part: chapter --- title: Track and Bus Groups -include: _manual/11_working-with-tracks/10_track-and-bus-groups.html +include: _manual/11_working-with-tracks/9_track-and-bus-groups.html part: subchapter --- @@ -1420,12 +1432,6 @@ include: _manual/15_signal-routing.html part: subchapter --- ---- -title: Busses and VCAs -include: _manual/11_working-with-tracks/02_busses-and-vcas.html -part: subchapter ---- - --- title: Aux Sends include: _manual/15_signal-routing/01_aux-sends.html diff --git a/source/images/bus-mixer-strip.png b/source/images/bus-mixer-strip.png new file mode 100644 index 0000000..1df36a9 Binary files /dev/null and b/source/images/bus-mixer-strip.png differ diff --git a/source/images/master-strip.png b/source/images/master-strip.png new file mode 100644 index 0000000..c93f77d Binary files /dev/null and b/source/images/master-strip.png differ 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 diff --git a/source/images/vca-numbered.png b/source/images/vca-numbered.png new file mode 100644 index 0000000..2ceedee Binary files /dev/null and b/source/images/vca-numbered.png differ