From 1321d4a5f39bf9163b6776dddc24d8ce151fd4d3 Mon Sep 17 00:00:00 2001 From: =?utf8?q?J=C3=B6rn=20Nettingsmeier?= Date: Mon, 3 Feb 2014 00:09:23 +0100 Subject: [PATCH] next batch of XHTML validation fixes. somebody really hates markup languages here... --- ...anding-basic-concepts-and-terminology.html | 4 +- .../03_setting-up-your-system/02_mouse.html | 2 +- .../06_using_more_than_one_audio_device.html | 7 ++- .../01_ubuntu-linux.html | 8 +-- ...starting-ardour-from-the-command-line.html | 24 ++++----- .../01_ranges--marks-list.html | 2 +- .../04_track--bus-group-list.html | 2 +- .../05_tracks--busses-list.html | 2 +- .../05_using-ardour-clock-displays.html | 3 +- .../03_using-key-bindings.html | 6 +-- .../02_creating-range-markers.html | 12 ++++- .../03_using-aatranslator.html | 2 +- .../01_track-types.html | 3 +- .../02_adding-tracks-and-busses.html | 3 +- .../06_bus-controls.html | 3 +- .../07_audio-track-controls.html | 5 +- .../08_midi-track-controls.html | 3 +- .../06_getting-plugins.html | 3 +- _manual/14_signal-routing/07_Patchbay.html | 2 +- .../03_what-regions-are-affected.html | 49 +++++++++++++------ .../04_snap-to-the-grid.html | 3 +- .../12_edit-midi/04_add-new-notes.html | 1 - .../12_edit-midi/12_copy-midi-region.html | 2 +- _manual/17_mixing/01_muting-and-soloing.html | 2 +- _manual/17_mixing/02_panning.html | 8 +-- .../02_panning/01_stereo_panner.html | 8 ++- .../17_mixing/02_panning/03_vbap_panner.html | 9 ++-- .../03_timecode-generators-and-slaves.html | 24 +++++---- .../01_controlling-ardour-with-osc.html | 10 ++-- 29 files changed, 117 insertions(+), 95 deletions(-) diff --git a/_manual/02_introducing-ardour/02_understanding-basic-concepts-and-terminology.html b/_manual/02_introducing-ardour/02_understanding-basic-concepts-and-terminology.html index 0a3579d..bb23e6a 100644 --- a/_manual/02_introducing-ardour/02_understanding-basic-concepts-and-terminology.html +++ b/_manual/02_introducing-ardour/02_understanding-basic-concepts-and-terminology.html @@ -45,8 +45,6 @@ title: Understanding Basic Concepts and Terminology
Ardour supports VST plugins that have been compiled for Linux.
AudioUnit (AU)
Mac OS X versions of Ardour support AudioUnit (AU) plugins.
-
+

Ardour has some support for running Windows VST plugins on Linux, but this is rather complicated, extremely difficult for the Ardour developers to debug, and generally unreliable. If it is at all possible, you are strongly advised to use native LADSPA, LV2 or Linux VST plugins on Linux, or AU on Mac OS X.

More details can be found at Working With Plugins.

- - diff --git a/_manual/03_setting-up-your-system/02_mouse.html b/_manual/03_setting-up-your-system/02_mouse.html index dc72f1a..f56d66a 100644 --- a/_manual/03_setting-up-your-system/02_mouse.html +++ b/_manual/03_setting-up-your-system/02_mouse.html @@ -16,4 +16,4 @@ title: Mouse

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.

+

For more detailed instructions see Using the mouse.

diff --git a/_manual/03_setting-up-your-system/06_using_more_than_one_audio_device.html b/_manual/03_setting-up-your-system/06_using_more_than_one_audio_device.html index 3e23252..b84805a 100644 --- a/_manual/03_setting-up-your-system/06_using_more_than_one_audio_device.html +++ b/_manual/03_setting-up-your-system/06_using_more_than_one_audio_device.html @@ -6,7 +6,7 @@ title: Using More Than One Audio Device

Ardour will only use a single interface. If you want to use more than one interface you have two choices: - +

  1. If you want to use Ardour to start JACK (which handles all @@ -18,7 +18,6 @@ title: Using More Than One Audio Device Use a different tool to start JACK and manage all the devices.
-

Ardour is fundamentally designed to be a component in a @@ -42,7 +41,7 @@ that some people might not care about them.

Of course, a lot of people don't live in an ideal world, and believe that software should make up for this.

-

OS X

+

OS X

Aggregate devices provide a method to use multiple soundcards as a single device. For example, you can "aggregate" 2 different @@ -84,7 +83,7 @@ a single device. For example, you can "aggregate" 2 different -

Linux

+

Linux

Please see the instructions at +

Installing Ardour

There may be unintended differences, and even bugs in Ubuntu native @@ -74,12 +74,12 @@ title: Ubuntu Linux

The specific issues known at this time for all flavors of Ubuntu 12.04 and 12.10 are: +

 -

Symptoms
@@ -91,11 +91,11 @@ title: Ubuntu Linux

How to fix
+

These bugs do not affect the upcoming 13.04 release, and earlier releases (12.04 and 12.10) are in the process of being fixed.

-
@@ -136,7 +136,7 @@ title: Ubuntu Linux

Reporting Issues

Given the difficulties in supporting Ubuntu and the limited time/resources of the Ardour team, the Ubuntu Studio Project has requested that issues and bug reports related to Ubuntu, Ubuntu Studio and other derivitives be directed to them.

-

Contact Information for Ubuntu Studio

+

Contact Information for Ubuntu Studio

The Ubuntu Studio Homepage

The Ubuntu Studio Forums.

Information on the Ubuntu Studio Mailing Lists.

diff --git a/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html b/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html index 063e9a2..023f348 100644 --- a/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html +++ b/_manual/04_ardours-interface/01_starting-ardour/01_starting-ardour-from-the-command-line.html @@ -5,19 +5,15 @@ title: Starting Ardour From the Command Line -

Starting Ardour on the command line (Linux)

-

Like (almost) any other program on Linux, Ardour can be started on the command line.

- +ardour3 +

To start Ardour with an existing session:

+ardour3 /path/to/session +

replacing /path/to/session with the actual path to your session. You can specify either the session folder or any session file inside the folder (including snapshots).

+

To start Ardour with a new, named session:

+ardour3 -N /path/to/new/session +

Other Command Line Options

diff --git a/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/01_ranges--marks-list.html b/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/01_ranges--marks-list.html index dfce41e..e16d547 100644 --- a/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/01_ranges--marks-list.html +++ b/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/01_ranges--marks-list.html @@ -1,6 +1,6 @@ --- layout: default -title: Ranges & Marks List +title: Ranges & Marks List --- diff --git a/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/04_track--bus-group-list.html b/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/04_track--bus-group-list.html index 12802af..2ebc1bc 100644 --- a/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/04_track--bus-group-list.html +++ b/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/04_track--bus-group-list.html @@ -1,6 +1,6 @@ --- layout: default -title: Track & Bus Group List +title: Track & Bus Group List --- diff --git a/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/05_tracks--busses-list.html b/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/05_tracks--busses-list.html index 53f683e..1a33e8b 100644 --- a/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/05_tracks--busses-list.html +++ b/_manual/04_ardours-interface/03_introducing-the-editor-window/01_editor-lists/05_tracks--busses-list.html @@ -1,6 +1,6 @@ --- layout: default -title: Tracks & Busses List +title: Tracks & Busses List --- diff --git a/_manual/04_ardours-interface/05_using-ardour-clock-displays.html b/_manual/04_ardours-interface/05_using-ardour-clock-displays.html index 007b653..7dfb95f 100644 --- a/_manual/04_ardours-interface/05_using-ardour-clock-displays.html +++ b/_manual/04_ardours-interface/05_using-ardour-clock-displays.html @@ -22,7 +22,8 @@ Editing the time in the transport clocks will reposition the playhead in the sam Under the Windows item in the main menu you will find the "Big Clock" window, which also shows the playhead position in a big, fully resizable window. The big clock is very useful when you need to work away from the screen but still want to see the playhead position clearly (such as when working with a remote control device across, or in another, room). The big clock will also change its visual appearance to indicate when active recording is taking place. Below on the left is a screenshot showing a fairly large big clock window filling a good part of the display, and on the right, the same clock during active recording.

-an image of the big clock filling a screen an image of the big clock while recording +an image of the big clock filling a screen an image of the big clock while recording

The Special Role of the Secondary Transport Clock

diff --git a/_manual/05_controlling-playback/03_using-key-bindings.html b/_manual/05_controlling-playback/03_using-key-bindings.html index 1c9935f..c80d3f9 100644 --- a/_manual/05_controlling-playback/03_using-key-bindings.html +++ b/_manual/05_controlling-playback/03_using-key-bindings.html @@ -5,16 +5,14 @@ title: Using Key Bindings -

Ardour has many available commands for playback control that can be bound to keys. Many of them have default bindings, some do not, so the list below shows both the default bindings and command names.

+

Ardour has many available commands for playback control that can be bound to keys. Many of them have default bindings, some do not, so the list below shows both the default bindings and command names.

Space
switch between playback and stop.
Home
Move playhead to session start marker
End
-
Move playhead to session end marker
-
- +
Move playhead to session end marker
Right Arrow
Left Arrow
diff --git a/_manual/06_working-with-markers/02_creating-range-markers.html b/_manual/06_working-with-markers/02_creating-range-markers.html index 4939806..d7c93c2 100644 --- a/_manual/06_working-with-markers/02_creating-range-markers.html +++ b/_manual/06_working-with-markers/02_creating-range-markers.html @@ -5,9 +5,17 @@ title: Creating Range Markers -

Rages are essentially two Location Markers the are grouped together to mark the beginning and end of a section in the timeline. +

+ Rages are essentially two Location Markers the are grouped + together to mark the beginning and end of a section in the timeline. +

Creating a Range on the timeline

-

To create a Range on the timeline, right click on the Range Markers Ruler at the top of the Timeline then select New Range. Two markers with the same name will appear along the ruler. Both marks can be moved along the timeline by clicking and dragging them to the desired location. +

+ To create a Range on the timeline, right click on the + Range Markers Ruler at the top of the + Timeline then select New Range. + Two markers with the same name will appear along the ruler. + Both marks can be moved along the timeline by clicking and dragging them to the desired location.

Creating a Range from the Ranges & Marks List

diff --git a/_manual/07_working-with-sessions/05_interchange-with-other-daws/03_using-aatranslator.html b/_manual/07_working-with-sessions/05_interchange-with-other-daws/03_using-aatranslator.html index 3ad819c..59a0696 100644 --- a/_manual/07_working-with-sessions/05_interchange-with-other-daws/03_using-aatranslator.html +++ b/_manual/07_working-with-sessions/05_interchange-with-other-daws/03_using-aatranslator.html @@ -9,5 +9,5 @@ title: Using AATranslator

AATranslator is a Windows application that can convert sessions/projects from many diffferent DAWs into other formats. At the present time (December 2012), it can read and write Ardour 2.X sessions, and can read Ardour 3 sessions.

The program runs very well on Linux using Wine (a Windows environment for Linux). There are equivalent solutions for running Windows applications on OS X, but we have no experience with them at this time. Ardour users have reported great results using AATranslator on Ardour 2.X sessions.

The AATranslator website has full details on which formats/DAWs it supports, but they include ProTools, Live, Reaper, OMF, AAF and many more.

-

+

AATranslator Demo Animation

diff --git a/_manual/10_working-with-tracks/01_track-types.html b/_manual/10_working-with-tracks/01_track-types.html index 1ff760a..00807d9 100644 --- a/_manual/10_working-with-tracks/01_track-types.html +++ b/_manual/10_working-with-tracks/01_track-types.html @@ -30,7 +30,8 @@ title: Track Types
Tracks using this mode do destructive recording: all data is recorded to a single file and if you overdub a section of existing data, the existing data is destroyed (irrevocably - there is no undo). Fixed crossfades are added at every punch in and out point. This mode can be useful for certain kinds of dubbing workflows, but it not suggested for normal use.

The screenshot below shows a subtle difference between results of an overdub in normal mode (upper track) and non-layered mode (lower track). Both tracks were created using identical audio data. The upper track shows an overdub (the middle shorter region) in normal mode. In normal mode Ardour created a new region which if you look carefully has been layered on top of the the existing (longer) region. The lower track is in non-layered mode, and rather than overlay the overdub region, it split the existing region and inserted the new overdub region in between.

-

normal and non-layered overdubbing comparision

+

normal and non-layered overdubbing comparision

Channel Configuration

Ardour tracks can have any number of inputs and any number of outputs, and the number of either can be changed at any time (subject to restrictions caused by any plugins in a track). However it is useful to not have to configure this sort of thing for the most common cases, and so the Add Tracks dialog allows you to select "Mono", "Stereo" and few other typical configurations.

diff --git a/_manual/10_working-with-tracks/02_adding-tracks-and-busses.html b/_manual/10_working-with-tracks/02_adding-tracks-and-busses.html index 45be8c4..7c2dc86 100644 --- a/_manual/10_working-with-tracks/02_adding-tracks-and-busses.html +++ b/_manual/10_working-with-tracks/02_adding-tracks-and-busses.html @@ -16,7 +16,8 @@ title: Adding Tracks and Busses

Any of these actions will open the Add Track or Bus dialog. Note that any new tracks from this dialog will appear after the last currently selected track (if any).

-

the add-track dialog

+

the add-track dialog

From here, you can select firstly the number of tracks or busses to add, and the type; audio track, MIDI track or bus. There are also some options, which vary depending on the type of thing you are creating.

These options are:

diff --git a/_manual/10_working-with-tracks/06_bus-controls.html b/_manual/10_working-with-tracks/06_bus-controls.html index 6c25084..b0751be 100644 --- a/_manual/10_working-with-tracks/06_bus-controls.html +++ b/_manual/10_working-with-tracks/06_bus-controls.html @@ -6,7 +6,8 @@ title: Bus Controls

A typical control area or "bus header" is shown below:

-

bus controls

+

bus controls

At the top-left of the controls is the name of the bus. You can double click to edit the name, but the name must be unique within the session. Underneath the name is a copy of the bus' main level fader. The control buttons to the right-hand side are:

m
diff --git a/_manual/10_working-with-tracks/07_audio-track-controls.html b/_manual/10_working-with-tracks/07_audio-track-controls.html index 8a130b0..10e0b0c 100644 --- a/_manual/10_working-with-tracks/07_audio-track-controls.html +++ b/_manual/10_working-with-tracks/07_audio-track-controls.html @@ -6,9 +6,10 @@ title: Audio Track Controls

A typical control area or "track header" for an audio track is shown below:

-

audio track controls

+

audio track controls

An audio track has the same controls as a bus, with the addition of two extras. - +

[pink circle]
Record - The red button with the pink circle enables recording to the track. When this is clicked it will gain a bright red outline, and the track will then be recorded onto when the main session record enable is turned on with the transport rolling.
diff --git a/_manual/10_working-with-tracks/08_midi-track-controls.html b/_manual/10_working-with-tracks/08_midi-track-controls.html index 7251f25..fd7342f 100644 --- a/_manual/10_working-with-tracks/08_midi-track-controls.html +++ b/_manual/10_working-with-tracks/08_midi-track-controls.html @@ -6,7 +6,8 @@ title: MIDI Track Controls

A typical control area for a MIDI track is shown below:

-

midi track controls

+

midi track controls

To see the full set of MIDI track controls, as shown above, you need to increase the track height beyond the default. MIDI tracks show only a few of the control elements when when there is insufficient vertical space.

A MIDI track has the same basic controls as an audio track, with the addition of two extra elements. The set of buttons below the main track controls controls the MIDI channels that should be visible in the editor. A MIDI track's data may span any number of the 16 available MIDI channels, and sometimes it is useful to view only a subset of those channels; different instruments may, for example, be put on different MIDI channels. Clicking on a channel number toggles its visibility.

To the right of the MIDI track controls is a representation of a piano keyboard called the ‘scroomer’. This performs a couple of functions. Firstly, the scrollbar controls the range of pitches that are visible on the track. Drag the body of the scrollbar up and down to display higher or lower pitches. Drag the scrollbar ‘handles’ to zooms in and out and increase and decrease the range of visible pitches. The piano keyboard gives a reference for the pitches visible on the track. In addition, clicking on the piano plays the corresponding MIDI note for reference.

diff --git a/_manual/11_working-with-plugins/06_getting-plugins.html b/_manual/11_working-with-plugins/06_getting-plugins.html index af2eda2..f48a663 100644 --- a/_manual/11_working-with-plugins/06_getting-plugins.html +++ b/_manual/11_working-with-plugins/06_getting-plugins.html @@ -46,7 +46,7 @@ The following list shows plugin packages. In some cases, a package cont
  • Vocoder http://www.sirlab.de/linux/download_vocoder.html
    • -
  • WASP http://linux01.gwdg.de/~nlissne/wasp/index.html (mar wanted!) +
  • WASP http://linux01.gwdg.de/~nlissne/wasp/index.html (mar wanted!)
  • Nova https://tim.klingt.org/nova/download/nova_filters-0.2.tar.bz2
    • @@ -136,6 +136,7 @@ The following list shows plugin packages. In some cases, a package cont something worth planning on. Ardour releases for OS X ship with a collection of many LADSPA plugins, some of which are very useful and some of which are outright buggy. +

    Most of the plugins you are likely to use on OS X will be in Apple's AudioUnit format. These have their own installation process that tends to diff --git a/_manual/14_signal-routing/07_Patchbay.html b/_manual/14_signal-routing/07_Patchbay.html index b59e45b..e02370b 100644 --- a/_manual/14_signal-routing/07_Patchbay.html +++ b/_manual/14_signal-routing/07_Patchbay.html @@ -9,7 +9,7 @@ title: Patchbay

    Notable exceptions are aux sends and connections to the monitor bus (if you are using one): these cannot be controlled from a patchbay, and are basically not under manual control at all.

    -

    an example patchbay

    +

    an example patchbay

    The patchbay presents two groups of ports; one set of sources (which produce data), and one of destinations (which consume data). Depending on the relative number of each, the sources will be placed on the left or the top of the dialogue, and the destinations on the right or the bottom. Thus, in general, signal flow is from top or left to right or bottom.

    Both sources and destinations are divided up into groups, with each group being given a tab. Click on the appropriate tab to show the ports in each group (‘Ardour Busses’, ‘Ardour Tracks’ and so on).

    The groups that are used are as follows:

    diff --git a/_manual/15_editing-and-arranging/03_what-regions-are-affected.html b/_manual/15_editing-and-arranging/03_what-regions-are-affected.html index 21af5cd..5e6e413 100644 --- a/_manual/15_editing-and-arranging/03_what-regions-are-affected.html +++ b/_manual/15_editing-and-arranging/03_what-regions-are-affected.html @@ -6,23 +6,40 @@ title: What Regions Are Affected? -

    This section explains the rules used to decide what regions are affected by editing operations. You don't really have to understand them - hopefully things will Just Work - but it may be useful to understand the rules some of the time.

    -

    Ardour divides operations up into those that operate on a single point in time (Split being the obvious example) and those that operate on two points (which can also be considered to be a range of sorts), Separate is a good example of this.

    -

    Most operations will operate on the currently selected region(s), but if no regions are selected, the region that the mouse is in will be used instead. Single-point operations will generally pick a set of regions to use based on the following rules:

    +

    + This section explains the rules used to decide what regions are affected + by editing operations. You don't really have to understand them - hopefully + things will Just Work - but it may be useful to understand the rules some + of the time. +

    +

    + Ardour divides operations up into those that operate on a single point + in time (Split being the obvious example) and those that operate on two + points (which can also be considered to be a range of sorts), Separate + is a good example of this. +

    +

    + Most operations will operate on the currently selected region(s), but if + no regions are selected, the region that the mouse is in will be used + instead. Single-point operations will generally pick a set of regions to + use based on the following rules:

      -
    1. If the edit point is `mouse': -
        -
      • if the mouse is over a selected region, or no region, use all selected regions. -
        • -
      • if the mouse is over an unselected region, use just that region. -
        • -
      -
      2. -
    2. For all other edit points -
      • use the selected regions and those that are both under the edit position and on a selected track, or on a track which is in the same active edit-enabled route group
        - as a selected region. -
      -
      3. +
    3. If the edit point is `mouse': +
        +
      • if the mouse is over a selected region, or no region, use all selected regions.
        • +
      • if the mouse is over an unselected region, use just that region.
        • +
      +
      4. +
    4. For all other edit points +
        +
      • + use the selected regions and those that are both + under the edit position and on a selected track, + or on a track which is in the same active edit-enabled route group + as a selected region. +
        • +
      +

    The rationale here for the two different rules is that the mouse edit point is special in that its position indicates both a time and a track; the other edit points (Playhead,Marker) indicates only a time.

    diff --git a/_manual/15_editing-and-arranging/04_snap-to-the-grid.html b/_manual/15_editing-and-arranging/04_snap-to-the-grid.html index 0b3591d..4e76c7b 100644 --- a/_manual/15_editing-and-arranging/04_snap-to-the-grid.html +++ b/_manual/15_editing-and-arranging/04_snap-to-the-grid.html @@ -48,7 +48,8 @@ title: Snap to the Grid
    Region Bounds
    Snaps positions to the nearest region start or end
    -

    To use Region starts/ends/syncs/bounds as snap choices, you must have either +

    To use Region starts/ends/syncs/bounds as snap choices, you must have +either

    • No tracks selected, which means that Ardour snaps to regions on any track, or
    • Several tracks selected, which means that Ardour only snaps to regions on those selected tracks.
      • diff --git a/_manual/15_editing-and-arranging/12_edit-midi/04_add-new-notes.html b/_manual/15_editing-and-arranging/12_edit-midi/04_add-new-notes.html index 25b2d46..c7f9d33 100644 --- a/_manual/15_editing-and-arranging/12_edit-midi/04_add-new-notes.html +++ b/_manual/15_editing-and-arranging/12_edit-midi/04_add-new-notes.html @@ -12,7 +12,6 @@ title: Add New Notes
      Selecting, moving, copying, trimming, deleting regions
      -
      leave "Note Level Editing" disabled, use object, range or other mouse modes
      Selecting, moving, copying trimming, deleting notes diff --git a/_manual/15_editing-and-arranging/12_edit-midi/12_copy-midi-region.html b/_manual/15_editing-and-arranging/12_edit-midi/12_copy-midi-region.html index 8f7a3f1..3a48eba 100644 --- a/_manual/15_editing-and-arranging/12_edit-midi/12_copy-midi-region.html +++ b/_manual/15_editing-and-arranging/12_edit-midi/12_copy-midi-region.html @@ -35,7 +35,7 @@ of them.

      Making an existing copy of a MIDI region independent

      -Context-click on the MIDI region you want to be +Context-click on the MIDI region you want to be independent. From the context menu, select MIDI > Unlink From Other Copies. The copy is now using an independent version of the data, and edits to the copy will affect only the copy. Other diff --git a/_manual/17_mixing/01_muting-and-soloing.html b/_manual/17_mixing/01_muting-and-soloing.html index d67dbe7..46519f5 100644 --- a/_manual/17_mixing/01_muting-and-soloing.html +++ b/_manual/17_mixing/01_muting-and-soloing.html @@ -27,7 +27,7 @@ title: Muting and Soloing

    There are further options with when solo controls are listen controls: the part of the track or bus from which the listen signal is obtained can be configured. Underneath the ‘Solo controls are Listen controls’ option in ‘Ardour Preferences’ is an option for ‘listen position’, which can be either After-Fade Listen (AFL) or Pre-Fade Listen (PFL). AFL, as its name suggests, obtains its signal from some point after the track or bus’ fader, and PFL from before it. The precise point to get the signal from can further be configured using the ‘PFL signals come from’ and ‘AFL signals come from’ options.

    The solo-mute arrangement with a monitor bus is shown below:

    -

    mute/solo signal flow

    +

    mute/solo signal flow

    Here we have a number of tracks or busses (in orange). Each one has an output which feeds the master bus. In addition, each has PFL and AFL outputs; we have a choice of which to use. PFL/AFL from each track or bus are mixed. Then, whenever anything is set to AFL/PFL, the monitor out becomes just those AFL/PFL feeds; the rest of the time, the monitor out is fed from the master bus.

    In this scheme Solo has no effect other than to mute other non-soloed tracks; with solo (rather then listen), the monitor out is fed from the master bus.

    Other solo options

    diff --git a/_manual/17_mixing/02_panning.html b/_manual/17_mixing/02_panning.html index a3407f8..9936a29 100644 --- a/_manual/17_mixing/02_panning.html +++ b/_manual/17_mixing/02_panning.html @@ -15,7 +15,7 @@ title: Panning make them move within the space over time.

    -

    Types of Panners

    +

    Types of Panners

    The way a panner works depends a great deal on how many signals it @@ -29,19 +29,19 @@ title: Panning number of signals to any number of ouputs. In reality, Ardour does not have specific panners for each different situation. Currently, it has dedicated panners for the following situations: - +

    • 1 signal distributed to 2 outputs (the "mono" panner)
    • 2 signals distributed to 2 outputs (the "stereo" panner)
    • N signals distributed to N outputs (the "vbap" panner)
    - +

    Even for each of these cases, there are many different ways to implement panning. Ardour currently offers just one solution to each of these situations, but in the future will offer more.

    -

    Panning is not Balance

    +

    Panning is not Balance

    If you are used to the "balance" control found on most home music diff --git a/_manual/17_mixing/02_panning/01_stereo_panner.html b/_manual/17_mixing/02_panning/01_stereo_panner.html index ebb0d04..afc553d 100644 --- a/_manual/17_mixing/02_panning/01_stereo_panner.html +++ b/_manual/17_mixing/02_panning/01_stereo_panner.html @@ -16,11 +16,9 @@ title: Stereo Panner sound stage that has been created with pan pots.*

    -

    With the default values it is not possible to alter the position, since the width is already spread entirely across both outputs. To alter the position, you must first reduce the width. -

    Stereo Panner User Interface

    @@ -32,7 +30,7 @@ title: Stereo Panner the top and bottom half. Click and/or drag in the top half to control position; click and/or drag in the bottom half to control width (see below for details). -

    +

    In the top half is the position indicator, which shows where the center of the stereo image is relative to the left and right @@ -79,7 +77,7 @@ title: Stereo Panner USA is not Kansas, but "Los Angeles: 50% New York: 50%".

    -

    Examples In Use

    +

    Examples In Use

    @@ -94,7 +92,7 @@ title: Stereo Panner L=0 R=100
    AppearanceSettings
    -

    Using the mouse

    +

    Using the mouse

    Mouse operations in the upper half of the panner adjust the position diff --git a/_manual/17_mixing/02_panning/03_vbap_panner.html b/_manual/17_mixing/02_panning/03_vbap_panner.html index 00fb28b..f37754e 100644 --- a/_manual/17_mixing/02_panning/03_vbap_panner.html +++ b/_manual/17_mixing/02_panning/03_vbap_panner.html @@ -59,7 +59,8 @@ title: VBAP Panner implementation must therefore include the possibility to define this layout.

    - +The VBAP +panner with 5 outputs

    Ardour currently uses a simplified approach: if a track or bus has more than two output channels (which implies stereo), it assumes that you @@ -69,7 +70,8 @@ title: VBAP Panner any desired spatialisation.

    Experimental 3D VBAP

    - +The VBAP +panner with 10 outputs, in experimental 3D mode

    For tracks with 10 outputs, Ardour will currently assume a 3-dimensional speaker layout corresponding to Auro-3D 10.1, which is a horizontal 5.1 @@ -78,7 +80,8 @@ title: VBAP Panner

    N:M panning

    - +The VBAP +panner in 4 in, 5 out mode

    For tracks and busses with more than one input, Ardour will (for now) assume that you wish to distribute the inputs symmetrically along the latitude around diff --git a/_manual/19_synchronization/03_timecode-generators-and-slaves.html b/_manual/19_synchronization/03_timecode-generators-and-slaves.html index 5c3abae..babca14 100644 --- a/_manual/19_synchronization/03_timecode-generators-and-slaves.html +++ b/_manual/19_synchronization/03_timecode-generators-and-slaves.html @@ -9,16 +9,16 @@ title: Timecode Generators and Slaves There are three common timecode formats:

      -
    • LTC – Linear/Longitudinal Time Code
      • -
    • MTC – MIDI Time Code
      • -
    • MIDI-Clock – tempo based time
      • +
    • LTC – Linear/Longitudinal Time Code
      • +
    • MTC – MIDI Time Code
      • +
    • MIDI-Clock – tempo based time

    As well as a JACK specific timecode implementation:

      -
    • JACK-transport
      • +
    • JACK-transport

    @@ -85,7 +85,7 @@ There are no options. Ardour sends full MTC frames whenever the transport is rel

    LTC Generator

    -The volume of the LTC signal can be conigured in in the Preferences > Transport dialog. By default it is set to -18dBFS which corresponds to 0dBu in an EBU calibrated system. +The volume of the LTC signal can be configured in in the Preferences > Transport dialog. By default it is set to -18dBFS which corresponds to 0dBu in an EBU calibrated system.

    @@ -94,6 +94,7 @@ The LTC generator has an additional option to keep sending timecode even when th

    LTC is send regardless of Ardour's transport-speed. It is accurately generated even for very slow speeds (<5%) and only limited by the soundcard's sampling-rate and filter (see Gibbs phenomenon) for high speeds. +

    Ardour Slave Configuration

    @@ -106,16 +107,13 @@ Switching the timecode-source can be done via the button just right of Ardour� When Ardour is chasing an external timecode source the following cases need to be distinguished:

      -
    1. the timecode source shares the clock
      2. -
    2. the timecode source is independent (no wordclock sync)
      3. +
    3. the timecode source shares the clock
      4. +
    4. the timecode source is independent (no wordclock sync)
    - -

    -and -

    +

    and

      -
    1. the timecode source uses the same FPS setting as Ardour
      2. -
    2. the timecode source runs at different frames-per-second
      3. +
    3. the timecode source uses the same FPS setting as Ardour
      4. +
    4. the timecode source runs at different frames-per-second

    diff --git a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html index 169f6ad..a5a2c37 100644 --- a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html +++ b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html @@ -77,20 +77,20 @@ For each of the following, [remote_id] is the remote_id or the track

    /ardour/routes/gaindB [remote_id] [gain_db]
    -
    where [gain_db] is a float ranging from -400 to 6 representing the desired gain of the track in dB.
    +
    where [gain_db] is a float ranging from -400 to 6 representing the desired gain of the track in dB.

    Menu actions

    -Every single menu item in Ardour's GUI is accessible via OSC. There is
    -a single common syntax to trigger the action as if it was selected
    +Every single menu item in Ardour's GUI is accessible via OSC. There is +a single common syntax to trigger the action as if it was selected with the mouse (or keyboard):

     /ardour/access_action [action_name]
    -

    The list below shows all available values of [action-name] as of
    -mid-March 2010 for Ardour 2.X. You can get the current list at any
    +

    The list below shows all available values of [action-name] as of +mid-March 2010 for Ardour 2.X. You can get the current list at any time by running Ardour with the -b flag.