ardour
/
manual
13
0
Fork 0
Code Pull Requests Releases Activity

Converts <img> to <figure> where it makes sense

This commit is contained in:
Ed Ward 2019-01-24 12:00:52 +01:00
parent 0f647acbba
commit 1bc084d882
43 changed files with 401 additions and 124 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
include/audiomidi-busses-mixer-strips.html
View File

@ -1,6 +1,9 @@
<figure class="right">
<img src="/images/bus-mixer-strip.png" alt="A bus mixer strip">
<img src="/images/bus-mixer-strip.png" alt="">
<figcaption>
A bus mixer strip
</figcaption>
</figure>
<p>
@ -76,7 +79,13 @@
<h3>Connecting a track to a bus via its outputs</h3>
<img class="left" src="/images/connecting_bus_output.png" alt="Connecting a bus through a track's outputs">
<figure class="left">
<img src="/images/connecting_bus_output.png" alt="Connecting a bus through a track's outputs">
<figcaption>
Connecting a bus through a track's outputs
</figcaption>
</figure>
<p>
Connecting the output(s) of a track to the input(s) of the bus sends
<em>all</em> the audio/MIDI to the bus. In the mixer strip, select (at the
@ -97,7 +106,13 @@
<h3>Connecting a track to a bus via Sends</h3>
<img class="left" src="/images/connecting_bus_send.png" alt="Connecting a bus through a send">
<figure class="left">
<img src="/images/connecting_bus_send.png" alt="Connecting a bus through a send">
<figcaption>
Connecting a bus through a send
</figcaption>
</figure>
<p>
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

8
include/audiomidi-mixer-strips.html
View File

@ -1,6 +1,10 @@
<img class="right" src="/images/mixer-1-strip-numbered.png" alt="A mixer strip">
<figure class="right">
<img src="/images/mixer-1-strip-numbered.png" alt="A mixer strip">
<figcaption>
A mixer strip
</figcaption>
</figure>
<p>
A <dfn>mixer strip</dfn> 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,

5
include/automation-nomenclature.html
View File

@ -1,7 +1,8 @@
<figure class=right>
<img src="/images/automation-fader1.png">
<figcaption class=center>An example of a fader automation lane (below) with its associated track (above).</figcaption>
<img src="/images/automation-fader1.png" alt="An example of a fader automation lane (below) with its associated track (above).">
<figcaption class=center>An example of a fader automation lane (below) with its associated track (above).
</figcaption>
</figure>
<p>

8
include/behringer-devices-in-mackielogic-control-mode.html
View File

@ -329,7 +329,13 @@ The surface can be broken into 8 groups of controls:
"Behringer X-Touch Mini" map included with Ardour. The control layout in Mackie Control
mode is shown below.
</p>
<img alt="X-Touch Mini MC mode layout" src="/images/xtouch-mini-mcp.png">
<figure>
<img alt="X-Touch Mini MC mode layout" src="/images/xtouch-mini-mcp.png">
<figcaption>
X-Touch Mini MC mode layout
</figcaption>
</figure>
<p class=fixme>Missing content</p>

17
include/comparing-aux-sends-and-subgroups.html
View File

@ -9,11 +9,24 @@
and are typically used to create a separate mix to send to (for example)
monitors or headphones (for performer monitor mixes):
</p>
<img width="300px" src="/images/aux_routing.png" alt="aux signal routing" />
<figure>
<img width="300px" src="/images/aux_routing.png" alt="Aux signal routing">
<figcaption>
Aux signal routing
</figcaption>
</figure>
<p>
<dfn>Subgroups</dfn> usually remove the original signal routing to the main mix and
replace it with a new one that delivers the output of the subgroup bus to
the main mix instead.
</p>
<img width="300px" src="/images/subgroup_routes.png" alt="sub group signal routing" />
<figure>
<img width="300px" src="/images/subgroup_routes.png" alt="sub group signal routing">
<figcaption>
Sub group signal routing
</figcaption>
</figure>

4
include/copying-versus-linking.html
View File

@ -38,11 +38,11 @@
</p>
<table>
<tr>
<td><img src="/images/225-ARDOUR_1_2_1.png"></td>
<td><kbd class="option">Copy file to session</kbd></td>
<td>This file will be imported in the audio/MIDI folder of the session.</td>
</tr>
<tr>
<td><img src="/images/226-ARDOUR_1_2_1.png"></td>
<td><kbd class="optoff">Copy file to session</kbd></td>
<td>This file won't be copied.</td>
</tr>
</table>

3
include/edit-point-control.html
View File

@ -1,6 +1,9 @@
<figure class="left">
<img src="/images/toolbar-editpoint.png" alt="Editor toolbar's Edit Point">
<figcaption>
Editor toolbar's Edit Point
</figcaption>
</figure>
<p>

7
include/fades-tab.html
View File

@ -1,5 +1,10 @@
<img src="/images/a4_session_properties_fades.png" alt="session properties fades tab"/>
<figure>
<img src="/images/a4_session_properties_fades.png" alt="Session properties fades tab">
<figcaption>
Session properties fades tab
</figcaption>
</figure>
<p>
Change how Ardour works with region crossfades.

7
include/filenames-tab.html
View File

@ -1,5 +1,10 @@
<img src="/images/a4_session_properties_filenames.png" alt="session properties filenames tab"/>
<figure>
<img src="/images/a4_session_properties_filenames.png" alt="Session properties filenames tab">
<figcaption>
Session properties filenames tab
</figcaption>
</figure>
<p>
This tab is used to change how Ardour names recorded regions.

7
include/grid-controls.html
View File

@ -1,5 +1,10 @@
<img class="left" src="/images/toolbar-grid.png" alt="Editor toolbar's grid">
<figure class="left">
<img src="/images/toolbar-grid.png" alt="Editor toolbar's grid">
<figcaption>
Editor toolbar's grid.
</figcaption>
</figure>
<p>
Ardour's editor utilizes a <dfn>grid</dfn> to assist in the placement of regions

7
include/import-dialog.html
View File

@ -1,5 +1,10 @@
<img class="right" src="/images/import-window.png" alt="The import window">
<figure class="right">
<img src="/images/import-window.png" alt="The import window">
<figcaption>
The import window.
</figcaption>
</figure>
<p>
Many sessions will require the use of <dfn>existing material</dfn>,

7
include/locations-tab.html
View File

@ -1,5 +1,10 @@
<img src="/images/a4_session_properties_locations.png" alt="session properties locations tab"/>
<figure>
<img src="/images/a4_session_properties_locations.png" alt="Session properties locations tab">
<figcaption>
Session properties locations tab
</figcaption>
</figure>
<p>
These options add file locations that will be searched to find the audio and

3
include/master-bus-strip.html
View File

@ -1,5 +1,8 @@
<figure class="right">
<img src="/images/master-strip.png" alt="The Master strip in the mixer">
<figcaption>
The Master strip in the mixer
</figcaption>
</figure>
<p>

7
include/media-tab.html
View File

@ -1,5 +1,10 @@
<img src="/images/a4_session_properties_media.png" alt="session properties media tab"/>
<figure class="right">
<img src="/images/a4_session_properties_media.png" alt="Session properties media tab">
<figcaption>
Session properties media tab
</figcaption>
</figure>
<p>
Change how sound is stored on disk. These options do not change how sound is handled

7
include/metadata.html
View File

@ -5,7 +5,12 @@
<h2>Edit Session Metadata Dialog</h2>
<img src="/images/edit-session-metadata.png" />
<figure>
<img src="/images/edit-session-metadata.png" alt="The session metadata editor">
<figcaption>
The session metadata editor
</figcaption>
</figure>
<p class=fixme>Add content</p>

15
include/meterbridge-tab.html
View File

@ -4,7 +4,12 @@
This tab changes what additional controls are also displayed.
</p>
<img src="/images/a4_session_properties_meterbridge.png" alt="session properties meterbridge tab"/>
<figure>
<img src="/images/a4_session_properties_meterbridge.png" alt="Session properties meterbridge tab">
<figcaption>
Session properties meterbridge tab
</figcaption>
</figure>
<ul>
<li>
@ -18,5 +23,9 @@
</li>
</ul>
<img src="/images/a4_meterbridge_full.png" alt="image of meterbidge with all options on"/>
<figure>
<img src="/images/a4_meterbridge_full.png" alt="Meterbidge with all options on">
<figcaption>
Meterbidge with all options on
</figcaption>
</figure>

7
include/monitor-section.html
View File

@ -1,5 +1,10 @@
<img class="right" src="/images/monitoring-strip.png" alt="The Monitoring strip">
<figure class="right">
<img src="/images/monitoring-strip.png" alt="The Monitoring strip">
<figcaption>
The Monitoring strip
</figcaption>
</figure>
<p>
The <dfn>Monitor section</dfn> is an optional feature that provides Control Room/Monitor Speaker outputs. It can be activated for the current session in the

34
include/monitor-signal-flow.html
View File

@ -2,8 +2,14 @@
<p>There are three basic ways to approach monitoring: </p>
<h3>External Monitoring</h3>
<img class="right"
src="/images/external-monitoring.png" />
<figure class="right">
<img src="/images/external-monitoring.png" alt="External monitoring">
<figcaption class="center">
External monitoring
</figcaption>
</figure>
<p>When using <dfn>external monitoring</dfn>, Ardour plays no role in
monitoring at all. Perhaps the recording set-up has an external mixer which
can be used to set up monitor mixes, or perhaps the sound-card being used
@ -11,19 +17,33 @@ src="/images/external-monitoring.png" />
latency. On the other hand it requires external hardware, and the monitoring
settings are less flexible and not saved with the session.</p>
<h3>JACK-Based Hardware Monitoring</h3>
<img class="right" src="/images/jack-monitoring.png" />
<h3 class="clear">JACK-Based Hardware Monitoring</h3>
<figure class="right">
<img src="/images/jack-monitoring.png" alt="Hardware Monitoring">
<figcaption class="center">
Hardware Monitoring
</figcaption>
</figure>
<p>Some sound cards have the ability
to mix signals from their inputs to their outputs with very low or even zero
latency, a feature called <dfn>hardware monitoring</dfn>.
Furthermore, on some cards this function can be controlled by JACK. This is a nice arrangement,
Furthermore, on some cards this function can be controlled by JACK. This is a nice arrangement,
if the sound card supports it, as it combines the convenience of having the
monitoring controlled by Ardour with the low latency operation of doing it
externally.
</p>
<h3>Software Monitoring</h3>
<img class="right" src="/images/ardour-monitoring.png" />
<h3 class="clear">Software Monitoring</h3>
<figure class="right">
<img src="/images/ardour-monitoring.png" alt="Software Monitoring">
<figcaption class="center">
Software Monitoring
</figcaption>
</figure>
<p>With the <dfn>software monitoring</dfn> approach, all monitoring is
performed by Ardour&mdash;it makes track inputs available at track
outputs, governed by various controls. This approach will almost always have

7
include/nudge-controls.html
View File

@ -1,5 +1,10 @@
<img class="left" src="/images/toolbar-nudge.png" alt="Editor toolbar's Nudge">
<figure class="left">
<img src="/images/toolbar-nudge.png" alt="Editor toolbar's Nudge">
<figcaption>
Editor toolbar's Nudge
</figcaption>
</figure>
<p>
The <dfn>nudge controls</dfn> will move the selected region(s) by a fixed amount of time. The left and right buttons move either backward or forward in time, and the small clock to the left of these buttons sets the amount of time to nudge by. As with all other clocks, you can right-click on the clock to choose the time representation you want to use.

84
include/osc58-using-the-setup-dialog.html
View File

@ -24,10 +24,14 @@
</p>
<h2>Dialog settings</h2>
<h3>OSC setup tab</h3>
<p>
<img alt="the OSC configuration dialog"
src="/images/osc-dialog.png">
</p>
<figure>
<img alt="The OSC configuration dialog" src="/images/osc-dialog.png">
<figcaption>
The OSC configuration dialog
</figcaption>
</figure>
<h4>Connection:</h4>
<p>
This field is informational only. It shows where Ardour will receive
@ -37,10 +41,14 @@
port up and will keep trying up to 10 ports up.
</p>
<h4>Port Mode:</h4>
<p>
<img alt="Port Mode Dropdown"
src="/images/osc-portmode.png">
</p>
<figure>
<img alt="Port Mode Dropdown" src="/images/osc-portmode.png">
<figcaption>
Port Mode Dropdown
</figcaption>
</figure>
<p>
This drop down allows the choice of Auto or Manual outbound port
setting. The Auto port mode, will send OSC messages back to
@ -82,10 +90,14 @@
controllable.
</p>
<h4>Gain Mode:</h4>
<p>
<img alt="Gain Mode Dropdown"
src="/images/osc-gainmode.png">
</p>
<figure>
<img alt="Gain Mode Dropdown" src="/images/osc-gainmode.png">
<figcaption>
Gain Mode Dropdown
</figcaption>
</figure>
<p>
Sets the faders (and sends faders) feedback math to position where a
value between 0 and 1 represents the fader position of the same fader
@ -95,19 +107,27 @@
fader is being adjusted and then return the name text.
</p>
<h4>Debug:</h4>
<p>
<img alt="Debug Mode Dropdown"
src="/images/osc-debug.png">
</p>
<figure>
<img alt="Debug Mode Dropdown" src="/images/osc-debug.png">
<figcaption>
Debug Mode Dropdown
</figcaption>
</figure>
<p>
For debugging purposes this allows logging either all OSC messages
Ardour receives or invalid messages received or none.
</p>
<h4>Preset:</h4>
<p>
<img alt="Preset Loader"
src="/images/osc-preset.png">
</p>
<figure>
<img alt="Preset Loader" src="/images/osc-preset.png">
<figcaption>
Preset Loader
</figcaption>
</figure>
<p>
Ardour now allows the use of preset settings. The default settings
used are the settings from the last session or the factory defaults
@ -134,10 +154,14 @@
so having correct defaults allows one "Connect" button rather than 4.
</p>
<h3>Default Strip Types tab</h3>
<p>
<img alt="the Default Strip Types tab"
src="/images/osc-strip-types.png">
</p>
<figure>
<img alt="The Default Strip Types tab" src="/images/osc-strip-types.png">
<figcaption>
The Default Strip Types tab
</figcaption>
</figure>
<p>
This allows selecting which of Ardour's mixer strips will be available
for control. The Factory default is all strips except master, monitor
@ -150,10 +174,14 @@
controlled by a VCA are hidden, but one of those tracks needs a tweak.
</p>
<h3>Default Feedback tab</h3>
<p>
<img alt="the Default Feedback tab"
src="/images/osc-feedbackdefault.png">
</p>
<figure>
<img alt="The Default Feedback tab" src="/images/osc-feedbackdefault.png">
<figcaption>
The Default Feedback tab
</figcaption>
</figure>
<p>
This allows setting up which controls provide feedback. The Factory
default is none. If the controller is unable to receive feedback, this

28
include/other-toolbar-items.html
View File

@ -1,6 +1,11 @@
<h2 id="monitor-options">The Monitor Options</h2>
<img src="/images/input-mode-buttons.png" alt="The Monitor options">
<figure>
<img alt="The Monitor options" src="/images/input-mode-buttons.png">
<figcaption>
The Monitor options
</figcaption>
</figure>
<p>
These buttons allow switching the monitoring mode globally, for all the tracks at once.
@ -23,7 +28,12 @@
<h2 id="playhead_options">The Playhead Options</h2>
<img src="/images/playhead-options.png" alt="The playhead options">
<figure>
<img alt="The playhead options" src="/images/playhead-options.png">
<figcaption>
The playhead options
</figcaption>
</figure>
<p>
Those 2 buttons control the behaviour of the playhead:
@ -35,7 +45,12 @@
<h2 id="status_indicators">The Status indicators</h2>
<img src="/images/status_buttons.png" alt="The Status buttons">
<figure>
<img alt="The Status buttons" src="/images/status_buttons.png">
<figcaption>
The Status buttons
</figcaption>
</figure>
<p>
The <dfn>Status</dfn> buttons show the current session state:
@ -49,7 +64,12 @@
<h2 id="mode_selector">The Mode Selector</h2>
<img src="/images/mode-selector_scripts_meter.png" alt="The Status buttons">
<figure>
<img alt="The Mode Selector" src="/images/mode-selector_scripts_meter.png">
<figcaption>
The Mode Selector
</figcaption>
</figure>
<p>
The Mode Selector allows switching between the Editor and Mixer windows.

8
include/processor-box.html
View File

@ -1,7 +1,9 @@
<figure class=right>
<img src="/images/processor-box.png" alt="the Processor Box" />
<figcaption class=center>Processor Box.</figcaption>
<figure class="right">
<img src="/images/processor-box.png" alt="the Processor Box">
<figcaption class="center">
Processor Box.
</figcaption>
</figure>
<p>

6
include/pushpull-trimming.html
View File

@ -15,9 +15,9 @@
</p>
<figure>
<img src="/images/before-trim.png" alt="region arrangement before trim" />
<img src="/images/after-trim.png" alt="region arrangement after a trim" />
<img src="/images/after-push-trim.png" alt="region arrangement after a push trim" />
<img src="/images/before-trim.png" alt="region arrangement before trim">
<img src="/images/after-trim.png" alt="region arrangement after a trim">
<img src="/images/after-push-trim.png" alt="region arrangement after a push trim">
<figcaption>
Trimming vs. push/pull trimming. Before trimming, After a simple trim, After a push/pull trim
</figcaption>

7
include/selection-and-punch-clocks.html
View File

@ -1,6 +1,11 @@
<h2 id="selection_clocks">The Selection Clocks</h2>
<img src="/images/selection-clocks.png" alt="The range clocks">
<figure>
<img src="/images/selection-clocks.png" alt="The range clocks">
<figcaption>
The range clocks
</figcaption>
</figure>
<p>
The current <dfn>selection range</dfn>, as set with the <a href="@@toolbox">Range Mode tool</a>,

7
include/session-misc-tab.html
View File

@ -3,7 +3,12 @@
This tab has several things that don't fit on the other tabs.
</p>
<img src="/images/a4_session_properties_misc.png" alt="session properties misc tab"/>
<figure>
<img src="/images/a4_session_properties_misc.png" alt="Session properties misc tab">
<figcaption>
Session properties misc tab
</figcaption>
</figure>
<ul>
<li>

7
include/status-bar.html
View File

@ -1,5 +1,10 @@
<img src="/images/status-bar.png" alt="The Status Bar">
<figure>
<img src="/images/status-bar.png" alt="The Status Bar">
<figcaption>
The Status Bar
</figcaption>
</figure>
<p>The status bar is an informative bar at the top of the window, showing:</p>

7
include/summary.html
View File

@ -1,5 +1,10 @@
<img src="/images/summary.png" alt="Ardour's Summary">
<figure>
<img src="/images/summary.png" alt="Ardour's Summary">
<figcaption>
Ardour's Summary
</figcaption>
</figure>
<p>
The <dfn>Summary</dfn> is a global overview of the session, allowing for a good "bird's eye" view of where in time and tracks the work happens.

7
include/sync-tab.html
View File

@ -1,5 +1,10 @@
<img src="/images/a4_session_properties_sync.png" alt="session properties sync tab"/>
<figure>
<img src="/images/a4_session_properties_sync.png" alt="Session properties sync tab">
<figcaption>
Session properties sync tab
</figcaption>
</figure>
<p>
This tab is used to modify the timecode settings when working with video to

2
include/timecode-generators-and-slaves.html
View File

@ -230,7 +230,7 @@
</p>
<figure class="center">
<img src="/images/ltc-transport-alignment.png" alt="LTC frame alignment"/>
<img src="/images/ltc-transport-alignment.png" alt="LTC frame alignment">
<figcaption>
LTC frame alignment for the 525/60 TV standard
</figcaption>

7
include/timecode-tab.html
View File

@ -1,5 +1,10 @@
<img src="/images/a4_session_properties_timecode.png" alt="session properties timecode tab"/>
<figure>
<img src="/images/a4_session_properties_timecode.png" alt="Session properties timecode tab">
<figcaption>
Session properties timecode tab
</figcaption>
</figure>
<p>
This tab is used to change how Ardour interprets and manipulates timecode.

7
include/toolbox.html
View File

@ -1,5 +1,10 @@
<img src="/images/toolbar-tools.png" alt="Editor toolbar's tools, aka toolbox">
<figure>
<img src="/images/toolbar-tools.png" alt="Editor toolbar's tools, aka toolbox">
<figcaption>
Editor toolbar's tools, aka toolbox
</figcaption>
</figure>
<h2>Global Edit mode</h2>

10
include/track-types.html
View File

@ -75,8 +75,14 @@
suggested for normal
use.</td></tr>
</table>
<img class="right" src="/images/a3_nonlayered_example.png" alt="normal and non-layered overdubbing comparision"
/>
<figure class="right">
<img src="/images/a3_nonlayered_example.png" alt="Normal and non-layered overdubbing comparision">
<figcaption>
Normal and non-layered overdubbing comparision
</figcaption>
</figure>
<p>
The screenshot on the right shows the subtle difference between an overdub
in <dfn>normal mode</dfn> (upper track) and one in <dfn>non-layered mode</dfn>

7
include/transport-bar.html
View File

@ -5,7 +5,12 @@
playback and recording.
</p>
<img src="/images/transport.png" alt="The transport controls">
<figure>
<img src="/images/transport.png" alt="The transport controls">
<figcaption>
The transport controls
</figcaption>
</figure>
<p>
This bar is made of (from left to right):

16
include/transport-clocks.html
View File

@ -1,5 +1,10 @@
<img src="/images/new_main_clocks.png" alt="An image of the transport clocks in Ardour" />
<figure>
<img src="/images/new_main_clocks.png" alt="The transport clocks in Ardour">
<figcaption>
The transport clocks in Ardour
</figcaption>
</figure>
<p>
<dfn>Clocks</dfn> in Ardour are used to display <dfn>time values</dfn> precisely.
@ -77,6 +82,11 @@
the same clock during active recording.
</p>
<a href="/images/bigclock.png"><img src="/images/bigclock.png" height="100" alt="an image of the big clock filling a screen"></a>
<a href="/images/bigclock-recording.png"><img src="/images/bigclock-recording.png" height="100" alt="an image of the big clock while recording"></a>
<figure>
<a href="/images/bigclock.png"><img src="/images/bigclock.png" height="100" alt="The big clock filling a screen"></a>
<a href="/images/bigclock-recording.png"><img src="/images/bigclock-recording.png" height="100" alt="The big clock while recording"></a>
<figcaption>
The Big Clock, with no transport rolling (left) and recording (right).
</figcaption>
</figure>

5
include/using-more-than-one-audio-device.html
View File

@ -25,7 +25,10 @@
</p>
<p>
Thus, in an ideal world, a single device with a single clock and all the inputs, outputs and other features needed should be used. Of course, there are those who like to point out that this is not an ideal world, and believe that software should make up for this.
Thus, in an ideal world, a single device with a single clock and all the inputs,
outputs and other features needed should be used. Of course, there are those
who like to point out that this is not an ideal world, and believe that software
should make up for this.
</p>
<h2>OS X</h2>

44
include/using-the-ableton-push-2.html
View File

@ -1,7 +1,11 @@
<p>
<img alt="the Ableton Push 2 surface" src="/images/push2-main.jpg">
</p>
<figure>
<img src="/images/push2-main.jpg" alt="The Ableton Push 2 surface">
<figcaption>
The Ableton Push 2 surface
</figcaption>
</figure>
<p>
Since version 5.4, Ardour has had extensive support for the Ableton
Push2. This is an expensive but beautifully engineered control
@ -44,11 +48,15 @@
aftertouch or polyphonic pressure messages. You can alter this
setting via the Push 2 GUI, accessed by double-clicking on the "Push
2" entry in the control surfaces list.
<p>
<img alt="the Push 2 configuration dialog"
src="/images/push2-gui.png">
</p>
<figure>
<img src="/images/push2-gui.png" alt="The Push 2 configuration dialog">
<figcaption>
The Push 2 configuration dialog
</figcaption>
</figure>
<h2>Basic Concepts</h2>
<p>
With the Push 2 support in Ardour 5.4, you can do the following
@ -99,10 +107,14 @@
them, the video display and the 8 buttons below that are combined to
provide a global view of the session mix.
</p>
<p>
<img alt="global mix mode on Push2 screen"
src="/images/push2-globalmix.png">
</p>
<figure>
<img src="/images/push2-globalmix.png" alt="Global mix mode on Push2 screen">
<figcaption>
Global mix mode on Push2 screen
</figcaption>
</figure>
<p>
The upper buttons are labelled by text in the video display just
below them. Pressing one of the buttons changes the function of the
@ -231,10 +243,14 @@
Press the Scale button to enter Scale mode. The display will look
like this:
</p>
<p>
<img alt="track mix mode on Push2 screen"
src="/images/push2-scale.png">
</p>
<figure>
<img src="/images/push2-scale.png" alt="Track mix mode on Push2 screen">
<figcaption>
Track mix mode on Push2 screen
</figcaption>
</figure>
<p>
In the center, 37 scales are presented. Scroll through them by
either using the cursor/arrow keys to the lower right of the

11
include/using-the-presonus-faderport.html
View File

@ -39,9 +39,14 @@
ports where your Faderport is connected.
</p>
<p>
<img alt="the Faderport configuration dialog"
src="/images/faderport_dialog.png">
</p>
<figure>
<img src="/images/faderport_dialog.png" alt="The Faderport configuration dialog">
<figcaption>
The Faderport configuration dialog
</figcaption>
</figure>
<p>
Once you select the input and output port, Ardour will initialize
the Faderport and it will be ready to use. You only need do this

56
include/using-the-presonus-faderport8.html
View File

@ -49,8 +49,10 @@
future sessions.
<p>
<figure class="center">
<img alt="FaderPort8 Control Surface Settings Dialog"
src="/images/fp8_settings.png"/>
<img alt="FaderPort8 Control Surface Settings Dialog" src="/images/fp8_settings.png">
<figcaption>
FaderPort8 Control Surface Settings Dialog
</figcaption>
</figure>
<h2>Using the FaderPort 8</h2>
@ -78,8 +80,10 @@
<h3>Transport Buttons</h3>
<figure class="left">
<img alt="FaderPort8 Transport Buttons"
src="/images/fp8_transport.png"/>
<img alt="FaderPort8 Transport Buttons" src="/images/fp8_transport.png">
<figcaption>
FaderPort8 Transport Buttons
</figcaption>
</figure>
<ol class="inside">
<li><kbd class="def">Stop</kbd>: Stops the transport. Press twice to return to
@ -108,8 +112,10 @@
With exception of <kbd>Click</kbd> the seven modes are exclusive (radio buttons).
</p>
<figure class="left">
<img alt="FaderPort8 Navigation Buttons"
src="/images/fp8_navigation.png"/>
<img alt="FaderPort8 Navigation Buttons" src="/images/fp8_navigation.png">
<figcaption>
FaderPort8 Navigation Buttons
</figcaption>
</figure>
<ol class="inside">
<li><kbd class="def">Channel</kbd>: The <kbd>Prev</kbd> / <kbd>Next</kbd>
@ -171,8 +177,10 @@
<h3>Shift Button</h3>
<figure class="left">
<img alt="the FaderPort8 Shift Button"
src="/images/fp8_shift_large.png"/>
<img alt="The FaderPort8 Shift Button" src="/images/fp8_shift_large.png">
<figcaption>
The FaderPort8 Shift Button
</figcaption>
</figure>
<p>
The two <kbd>Shift</kbd> buttons are identical, they're copied to provide
@ -197,8 +205,10 @@
(Note: with the 1.01 firmware these buttons always act on press.)
</p>
<figure class="left">
<img alt="FaderPort8 Fader Mode Buttons"
src="/images/fp8_fadermode.png"/>
<img alt="FaderPort8 Fader Mode Buttons" src="/images/fp8_fadermode.png">
<figcaption>
FaderPort8 Fader Mode Buttons
</figcaption>
</figure>
<ol class="inside">
<li><kbd class="def">Track</kbd>: In Track-mode, the motorized faders display
@ -258,8 +268,10 @@
<h3>Channel Strip</h3>
<figure class="left">
<img alt="The FaderPort8 Channel Strip"
src="/images/fp8_strip.png"/>
<img alt="The FaderPort8 Channel Strip" src="/images/fp8_strip.png">
<figcaption>
The FaderPort8 Channel Strip
</figcaption>
</figure>
<ul class="inside">
<li><strong>Touch-Sensitive Fader</strong>: The fader can be used to control
@ -324,8 +336,10 @@
channel-strips.
</p>
<figure class="left">
<img alt="FaderPort8 Mix Management Buttons"
src="/images/fp8_mixmanage.png"/>
<img alt="FaderPort8 Mix Management Buttons" src="/images/fp8_mixmanage.png">
<figcaption>
FaderPort8 Mix Management Buttons
</figcaption>
</figure>
<ol class="inside">
<li><kbd class="def">Audio</kbd>: View Audio Tracks only.</li>
@ -364,8 +378,10 @@
and pan automation modes respectively.
</p>
<figure class="left">
<img alt="FaderPort8 Automation Buttons"
src="/images/fp8_automation.png"/>
<img alt="FaderPort8 Automation Buttons" src="/images/fp8_automation.png">
<figcaption>
FaderPort8 Automation Buttons
</figcaption>
</figure>
<ol class="inside">
<li><kbd class="def">Latch</kbd>: Currently not available in Ardour.</li>
@ -400,8 +416,10 @@
<h3>Miscellaneous</h3>
<figure class="left">
<img alt="FaderPort8 Misc Buttons"
src="/images/fp8_misc.png"/>
<img alt="FaderPort8 Misc Buttons" src="/images/fp8_misc.png">
<figcaption>
FaderPort8 Misc Buttons
</figcaption>
</figure>
<ul class="inside">
<li><kbd class="def">Solo Clear</kbd>: Reset all solo controls in the
@ -479,6 +497,6 @@ The above also applies to Ardour-derivatives Harrison-Mixbus and Mixbus 32C with
When editing those processors, the parameters follows track selection (for other plugins this is not possible since they may not be present).
</li>
<li>
Fader mode <strong>Sends</strong> shows mixbus-assigns first (before any optional aux-sends). The master-bus-assign is available on the "S"olo button of the right-most strip.
Fader mode <strong>Sends</strong> shows mixbus-assigns first (before any optional aux-sends). The master-bus-assign is available on the "S"olo button of the right-most strip.
</li>
</ul>

1
include/vbap-panner.html
View File

@ -82,7 +82,6 @@
</figcaption>
</figure>
<!--<a href="/images/VBAP-panner-10.png"><img src="/images/VBAP-panner-10.png" class="right" style="width:150px;" alt="The VBAP panner with 10 outputs, in experimental 3D mode"></a>-->
<p>
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

10
include/working-with-extenders.html
View File

@ -49,8 +49,14 @@
and the bottom is the rightmost. The GUI shows explicitly the position
of the main or master surface within the group of surfaces.
</p>
<p><img alt="the Mackie Control Device Dialog"
src="/images/mcp-extender-position.png"></p>
<figure>
<img src="/images/mcp-extender-position.png" alt="The Mackie Control Device Dialog">
<figcaption>
The Mackie Control Device Dialog
</figcaption>
</figure>
<p>
The <code>MasterPosition</code> value is the position the master unit
(with the master fader) is located at within the group of surfaces.

7
include/zoom-controls.html
View File

@ -1,5 +1,10 @@
<img class="left" src="/images/toolbar-zoom.png" alt="Editor toolbar's zoom">
<figure class="left">
<img src="/images/toolbar-zoom.png" alt="Editor toolbar's zoom">
<figcaption>
Editor toolbar's zoom
</figcaption>
</figure>
<p>The zoom controls allow to navigate the session along both the time and track axes.</p>

BIN
source/images/225-ARDOUR_1_2_1.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 5.0 KiB

BIN
source/images/226-ARDOUR_1_2_1.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 4.9 KiB