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.
-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
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 063e9a2d..023f348c 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.
--
-
- type the following command in a terminal window
ardour3
-
- - to start Ardour with an existing session, type the following command in a terminal window
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, type the following command in a terminal
-window
ardour3 -N /path/to/new/session
-replacing /path/to/new/session with the name of the folder where you want the session stored. +
Starting Ardour on the command line (Linux)
+Like (almost) any other program on Linux, Ardour can be started on the command line. +Type the following command in a terminal window:
-
-
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 dfce41ec..e16d5470 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 12802af0..2ebc1bc3 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 53f683e2..1a33e8b9 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 007b653c..7dfb95fb 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 theWindows 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.
-
+
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 1c9935ff..c80d3f98 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 4939806f..d7c93c2f 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 -
- 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.
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 3ad819c4..59a06967 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 AATranslatorAATranslator 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.
-
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.
-
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 45be8c4f..7c2dc86e 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 BussesAny 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).
-
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 6c25084e..b0751be5 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
- 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 8a130b0b..10e0b0c7 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
- [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 7251f259..fd7342fd 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 or "bus header" is shown below:
-
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:
A typical control area or "track header" for an audio track is shown below:
-
An audio track has the same controls as a bus, with the addition of two extras. - +
A typical control area for a MIDI track is shown below:
-
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 af2eda28..f48a6633 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 contMost 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 b59e45b5..e02370b9 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.
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 21af5cd9..5e6e413a 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:
-
-
- 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. - -
- - 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. -
+ - 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
- 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. +
+ - 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 0b3591da..4e76c7b0 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
+
+
+