In Ardour, you work in two main windows: the <dfn>Editor</dfn> and the
<dfn>Mixer</dfn>.
</p>
-<img class="right" src="/ardour/manual/html/diagrams/editor-summary.png"
+<img class="right" src="/diagrams/editor-summary.png"
alt="Ardour's editor window" />
<p>
The <dfn>Editor</dfn> window includes the editor track <dfn>canvas</dfn>
from left to right — the window really represents <dfn>time</dfn>
in a fairly literal way.
</p>
-<img class="right" src="/ardour/manual/html/diagrams/mixer-summary.png"
+<img class="right" src="/diagrams/mixer-summary.png"
alt="ardour's mixer window" />
<p>
The <dfn>Mixer</dfn> window on the other hand represents signal flow and
transport clock and the right one is the secondary transport clock.
They look like this:
</p>
-<img src="/files/manual/a3/images/new_main_clocks.png" alt="An image of the transport clocks in Ardour 3" />
+<img src="/images/new_main_clocks.png" alt="An image of the transport clocks in Ardour 3" />
<p>
Editing the time in the transport clocks will reposition the playhead in the same
way that various other editing operations will.
large big clock window filling a good part of the display, and on the right,
the same clock during active recording.
</p>
-<a href="/files/bigclock.png"><img src="/files/bigclock.png" height="100" alt="an image of the big clock filling a screen" /></a>Â <a href="/files/bigclock-recording.png"><img src="/files/bigclock-recording.png" height="100" alt="an image of the big clock while recording"
+<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>
<h3>The Special Role of the Secondary Transport Clock</h3>
selection range, so the selection clocks show an "off" state.
</p>
-<img src="/files/selectionpunchclocks.png" alt="An image of the the selection and punch clocks in Ardour 3" />
+<img src="/images/selectionpunchclocks.png" alt="An image of the the selection and punch clocks in Ardour 3" />
<h2>Clock Modes</h2>
<p>
appear in a different color, from right to left, overwriting the existing value.
Mid-edit, after typing <kbd class="input">3 2 2 2</kbd> the clock might look like this:
</p>
-<img src="/files/clockedit.png" alt="An image of a clock being edited in Ardour 3" />
+<img src="/images/clockedit.png" alt="An image of a clock being edited in Ardour 3" />
<p>
To finish the edit, press <kbd>↵</kbd> or <kbd>Tab</kbd>. To exit an
edit without changing the clock press <kbd>ESC</kbd>. If you mis-type an entry
<h2>Ardour Specifics</h2>
-<img class="right" src="/ardour/manual/html/screenshots/mixer-meter-context-menu.png" alt="mixer strip meter context menu" />
+<img class="right" src="/images/mixer-meter-context-menu.png" alt="mixer strip meter context menu" />
<p>
Meters are available in various places in ardour:
</p>
Strip</kbd> settings, the metering point is also accessible via a button in
each Mixer strip.
</p>
-<img class="right" src="/ardour/manual/html/screenshots/meter-preferences.png" alt="" />
+<img class="right" src="/images/meter-preferences.png" alt="" />
<p>
Regardless of meter type and standard the meter display will highlight red if
the signal on the given channel exceeds the configured peak threshold.
-18 dBFS 1 kHz sine wave.
</p>
-<img class="right" style="max-width:45%;height:400px;" src="/ardour/manual/html/screenshots/needle-meters-18.png"
+<img class="right" style="max-width:45%;height:400px;" src="/images/needle-meters-18.png"
alt="Needle-style meters as external LV2 plugins" />
-<img style="max-width:45%; height:400px" src="/ardour/manual/html/screenshots/meter-types-18.png"
+<img style="max-width:45%; height:400px" src="/images/meter-types-18.png"
alt="Bar-graph meters in Ardour" />
<p>
has full details on supported formats and DAWs. The list includes
ProTools, Live, Reaper, OMF, AAF and many more.
</p>
-<img src="/images/No problem.gif" alt="AATranslator Demo Animation"/>
+<img src="/images/No_problem.gif" alt="AATranslator Demo Animation"/>
</p>
<h2>Edit Session Metadata Dialog</h2>
-<img src="/ardour/manual/html/screenshots/edit-session-metadata.png" />
+<img src="/images/edit-session-metadata.png" />
useful for certain kinds of re-recording workflows, but it not suggested for normal
use.</dd>
</dl>
-<img class="right" src="/files/a3/a3_nonlayered_example.png" alt="normal and non-layered overdubbing comparision"
+<img class="right" src="/images/a3_nonlayered_example.png" alt="normal and non-layered overdubbing comparision"
/>
<p>
The screenshot on the right shows the subtle difference between an overdub
title: Adding Tracks and Busses
---
-<img class="right" src="/ardour/manual/html/screenshots/add-track-or-bus.png" alt="the add-track dialog" />
+<img class="right" src="/images/add-track-or-bus.png" alt="the add-track dialog" />
<p>A track or bus can be added to a session in various ways:</p>
<ul>
<li>Choose <kbd class="menu">Track > Add Track or Bus</kbd>.</li>
Here is an image of a track with a rather drastic overdub situation,
viewed in normal <dfn>overlaid mode</dfn>:
</p>
-<img src="/files/a3/a3_overlaps_layered.png" alt="overlapping regions in overlaid mode" />
+<img src="/images/a3_overlaps_layered.png" alt="overlapping regions in overlaid mode" />
<p>
To change this display, right click on the track header, and you'll see
the menu displayed above. There are two choices for layers. <kbd
class="menu">overlaid</kbd> is currently selected. Click on <kbd
class="menu">stacked</kbd> and the track display changes to this:
</p>
-<img src="/files/a3/a3_layers_stacked.png" alt="overlapping regions in stacked mode" />
+<img src="/images/a3_layers_stacked.png" alt="overlapping regions in stacked mode" />
<p>
You can still move regions around as usual, and in fact you can
even drag them so that they overlay each again, but when you
---
<p>A typical control area or <dfn>bus header<dfn> is shown below:</p>
-<img src="/ardour/manual/html/screenshots/typical-bus-controls.png" alt="bus controls" />
+<img src="/images/typical-bus-controls.png" alt="bus controls" />
<p>
At the top-left of the controls is the name of the bus, which can be
A typical control area or <dfn>track header</dfn> for an audio track is
shown below:
</p>
-<img src="/ardour/manual/html/screenshots/typical-audio-track-controls.png" alt="audio track controls"
+<img src="/images/typical-audio-track-controls.png" alt="audio track controls"
/>
<p>
An audio track has the same
---
<p>A typical <dfn>MIDI track header</dfn> looks like this:</p>
-<img src="/ardour/manual/html/diagrams/typical-midi-track-controls.png" alt="midi track controls"
+<img src="/diagrams/typical-midi-track-controls.png" alt="midi track controls"
/>
<p>
You can group tracks and busses in various ways. In the editor window,
a track's controls might look like these:
</p>
-<img class="left" src="/ardour/manual/html/screenshots/track-in-group.png" alt="track headers for a group" />
+<img class="left" src="/images/track-in-group.png" alt="track headers for a group" />
<p>
The green tab to the left of the track header indicates that this track
is in a group called <samp>Fred</samp>. You can drag these tabs to add
which is also used when creating new groups:
</p>
-<img class="right" src="/ardour/manual/html/screenshots/route-group-dialogue.png" alt="the track/bus group dialog" />
+<img class="right" src="/images/route-group-dialogue.png" alt="the track/bus group dialog" />
<h3>Group Color</h3>
<p>
connections. The plugins can be sorted by clicking on a column header.
</p>
-<img src="/files/a4/a4_plugin_manager.png" alt="Plugin Manager window"/>
+<img src="/images/a4_plugin_manager.png" alt="Plugin Manager window"/>
<h2>Plugin Display Status</h2>
and drag it down.
</p>
-<img src="/files/a4/a4_plugin_sidebar.png" alt="Plugin Sidebar"/>
+<img src="/images/a4_plugin_sidebar.png" alt="Plugin Sidebar"/>
<h2>Features</h2>
<p>
You can import audio and MIDI data into your session with the
<dfn>Add Existing Media</dfn> dialog.
</p>
-<img src="/files/reference/images/209-ARDOUR_1_2_1.png" />
+<img src="/images/209-ARDOUR_1_2_1.png" />
<h2>The Soundfile Information Box</h2>
<p>
dialog window.
</p>
<p>
- <img class="left" src="/files/reference/images/225-ARDOUR_1_2_1.png" />
+ <img class="left" src="/images/225-ARDOUR_1_2_1.png" />
← This file will be imported in the audio/MIDI folder of your session.
</p>
<p>
- <img class="left" src="/files/reference/images/226-ARDOUR_1_2_1.png" />
+ <img class="left" src="/images/226-ARDOUR_1_2_1.png" />
← This file won't be copied.
</p>
<p class="note">
<h3>External Monitoring</h3>
<img class="right"
-src="/ardour/manual/html/diagrams/external-monitoring.png" />
+src="/diagrams/external-monitoring.png" />
<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
settings are less flexible and not saved with the session.</p>
<h3>JACK-Based Hardware Monitoring</h3>
-<img class="right" src="/ardour/manual/html/diagrams/jack-monitoring.png" />
+<img class="right" src="/diagrams/jack-monitoring.png" />
<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>.
</p>
<h3>Software Monitoring</h3>
-<img class="right" src="/ardour/manual/html/diagrams/ardour-monitoring.png" />
+<img class="right" src="/diagrams/ardour-monitoring.png" />
<p>With the <dfn>software monitoring</dfn> approach, all monitoring is
performed by Ardour — it makes track inputs available at track
outputs, governed by various controls. This approach will almost always have
depends for the most part on the JACK buffer size that is being used.
</p>
-{% children %}
\ No newline at end of file
+{% children %}
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="/files/manual/a3/images/aux_routing.png" alt="aux signal routing" />
+<img width="300px" src="/images/aux_routing.png" alt="aux signal routing" />
<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="/files/manual/a3/images/subgroup_routes.png" alt="sub group signal routing" />
+<img width="300px" src="/images/subgroup_routes.png" alt="sub group signal routing" />
you are using one): these cannot be controlled from a patchbay, and are
basically not under manual control at all.
</p>
-<img class="right" src="/ardour/manual/html/screenshots/connection-manager.png" alt="an example patchbay" />
+<img class="right" src="/images/connection-manager.png" alt="an example patchbay" />
<p>
The patchbay presents two groups of ports; one set of <dfn>sources</dfn>
(which produce data), and one of <dfn>destinations</dfn> (which consume
difference in the results of a normal trim and push/pull trim. First,
the initial situation:
</p>
-<img src="/files/a3/a3_before_trim.png" alt="region arrangement before trim" />
+<img src="/images/a3_before_trim.png" alt="region arrangement before trim" />
<p>
Here is what happens after we trim the right hand (selected) region by
dragging its starting position earlier:
</p>
-<img src="/files/a3/a3_after_trim.png" alt="region arrangement after a trim" />
+<img src="/images/a3_after_trim.png" alt="region arrangement after a trim" />
<p>
You can see that it now overlaps the earlier region and a crossfade has
been created between them.
Lets look now at what happens if we do the same trim, but <kbd
class="mouse mod3">Left</kbd>-dragging to turn it into a push-pull trim instead:
</p>
-<img src="/files/a3/a3_after_push_trim.png" alt="region arrangement after a push trim" />
+<img src="/images/a3_after_push_trim.png" alt="region arrangement after a push trim" />
<p>
There is no overlap, and the end of the earlier region has been moved
along with the start of the later region, so that they still directly
Here is an example where we start with a short region placed so that it
overlaps a longer region:
</p>
-<img src="/files/a3/a3_before_separate_under.png" alt="region arrangement before separate under" />
+<img src="/images/a3_before_separate_under.png" alt="region arrangement before separate under" />
<p>
When we perform the <dfn>Separate Under</dfn> edit, the lower region splits
in two, with boundaries exactly positioned at the edges of the upper region:
</p>
-<img src="/files/a3/a3_after_separate_under.png" alt="region arrangement after separate under" />
+<img src="/images/a3_after_separate_under.png" alt="region arrangement after separate under" />
<p>
If the upper region covers only one end of the lower region, then this
operation is equivalent to
useful when editing very percussive material and just needing to
automatically trim the ends of a region. The dialog looks like this:
</p>
-<img src="/files/a3/a3_strip_silence.png" alt="strip silence dialog" />
+<img src="/images/a3_strip_silence.png" alt="strip silence dialog" />
<p>
The edit applies to all selected regions, allowing batch processing.
You can also see in the screenshot how the main editor window is used
---
-<p><img src="/files/a3/a3_quantize.png" alt="quantize dialog" /></p>
+<p><img src="/images/a3_quantize.png" alt="quantize dialog" /></p>
<p>Accessed via <kbd>q</kbd>, the dialog includes:</p>
<ul>
<li>Options for grid, legato amd groove quantize</li>
MIDI data. You cannot simultaneously step edit and record MIDI via the
track's MIDI port.
</p>
-<img src="/files/a3/a3_step_entry.png" />
+<img src="/images/a3_step_entry.png" />
<p>The dialog (quite closely modelled on Logic's) contains:</p>
<ul>
<li>
<p>
The solo-mute arrangement with a monitor bus is shown below:
</p>
-<img src="/ardour/manual/html/diagrams/solo-mute.png" alt="mute/solo signal flow" />
+<img src="/diagrams/solo-mute.png" alt="mute/solo signal flow" />
<p>
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
</p>
<h2>File Format</h2>
-<img src="/ardour/manual/html/screenshots/export-dialog-file-format.png" />
+<img src="/images/export-dialog-file-format.png" />
<p>
This tab contains controls for the format of the exported audio file.
You can enable more than one format here, in which case each will be exported in turn.
to enter in Soundcloud account details (email and password), and what should happen
to the uploaded files will become visible.
</p>
-<img src="/ardour/manual/html/screenshots/soundcloud-upload.png" />
+<img src="/images/soundcloud-upload.png" />
<p>
<dl>
<dt>Make files public</dt><dd>Choose whether to make uploaded files available to anyone via the Soundcloud web site.</dd>
<h2>Time Span</h2>
-<img src="/ardour/manual/html/screenshots/export-dialog-timespan.png" />
+<img src="/images/export-dialog-timespan.png" />
<p>
This tab allows you to select the range (or ranges) of the timeline to export. By default, "session" is
enabled - this will export the whole session from the start marker to the end marker.
<h2>Channels</h2>
-<img src="/ardour/manual/html/screenshots/export-dialog-channels.png" />
+<img src="/images/export-dialog-channels.png" />
<p>
Here you can choose which outputs (tracks or busses) should be sent to the exported file.
</p>
<h2>Stem Export</h2>
-<img src="/ardour/manual/html/screenshots/export-dialog-stem-export.png" />
+<img src="/images/export-dialog-stem-export.png" />
<p>
If you chose 'Stem Export', the 'Channels' tab appears slightly differently:
in this case each chosen channel (track or bus) is exported to its own file,
Export Format Profiles are edited via the 'Edit Export Format Profile' dialog.
</p>
-<img src="/ardour/manual/html/screenshots/edit-export-format-profile.png" />
+<img src="/images/edit-export-format-profile.png" />
<p>
<h3>Normalize</h3>
<p>
<h2>The Latency chain</h2>
-<img src="/ardour/manual/html/diagrams/latency-chain.png" title="Latency chain" alt="Latency chain" />
+<img src="/diagrams/latency-chain.png" title="Latency chain" alt="Latency chain" />
<p>
<em>Figure: Latency chain.</em>
The numbers are an example for a typical PC. With professional gear and an
In order to compensate for latency, JACK or JACK applications need to know
exactly how long a certain signal needs to be read-ahead or delayed:
</p>
-<img src="/ardour/manual/html/diagrams/jack-latency-excerpt.png" title="Jack Latency Compensation" alt="Jack Latency Compensation" />
+<img src="/diagrams/jack-latency-excerpt.png" title="Jack Latency Compensation" alt="Jack Latency Compensation" />
<p>
<em>Figure: Jack Latency Compensation.</em>
</p>
the video Frame boundaries.
</p>
-<img src="/ardour/manual/html/diagrams/ltc-transport-alignment.png" title="LTC frame alignment" alt="LTC frame alignment"/>
+<img src="/diagrams/ltc-transport-alignment.png" title="LTC frame alignment" alt="LTC frame alignment"/>
<p><em>Figure: LTC frame alignment for the 525/60 TV standard</em></p>
<p>
These preferences apply to all Ardour sessions.
</p>
-<img src="/files/a4/a4_preferences_misc.png" alt="ardour preferences
+<img src="/images/a4_preferences_misc.png" alt="ardour preferences
dialog"/>
{% children %}
This tab contains settings that do not belong on the other tabs.
</p>
-<img src="/files/a4/a4_preferences_misc.png" alt="preferences
+<img src="/images/a4_preferences_misc.png" alt="preferences
misc tab"/>
<ul>
and <a href="/synchronization/">Synchronization</a>.
</p>
-<img src="/files/a4/a4_preferences_transport.png" alt="preferences
+<img src="/images/a4_preferences_transport.png" alt="preferences
transport tab"/>
<ul>
window when <a href="/editing-and-arranging">Editing and Arranging</a>.
</p>
-<img src="/files/a4/a4_preferences_editor.png" alt="preferences
+<img src="/images/a4_preferences_editor.png" alt="preferences
editor tab"/>
<ul>
This tab contains settings for handling audio.
</p>
-<img src="/files/a4/a4_preferences_audio.png" alt="preferences
+<img src="/images/a4_preferences_audio.png" alt="preferences
audio tab"/>
<ul>
<a href="/mixing/panning/">panning</a>.
</p>
-<img src="/files/a4/a4_preferences_solomute.png" alt="preferences
+<img src="/images/a4_preferences_solomute.png" alt="preferences
solo/mute tab"/>
<ul>
This tab contains settings related to the use of MIDI inside Ardour.
</p>
-<img src="/files/a4/a4_preferences_midi.png" alt="preferences
+<img src="/images/a4_preferences_midi.png" alt="preferences
MIDI tab"/>
<ul>
<a href="/ardours-interface">Ardours interface</a>.
</p>
-<img src="/files/a4/a4_preferences_interaction.png" alt="preferences
+<img src="/images/a4_preferences_interaction.png" alt="preferences
user interaction tab"/>
<ul>
<a href="/using-control-surfaces/">Using Control Surfaces</a>.
</p>
-<img src="/files/a4/a4_preferences_control_surfaces.png" alt="preferences
+<img src="/images/a4_preferences_control_surfaces.png" alt="preferences
control surfaces tab"/>
<p>
This tab contains settings related to handling of Video.
</p>
-<img src="/files/a4/a4_preferences_video.png" alt="preferences
+<img src="/images/a4_preferences_video.png" alt="preferences
video tab"/>
<ul>
plugins.
</p>
-<img src="/files/a4/a4_preferences_plugins.png" alt="preferences
+<img src="/images/a4_preferences_plugins.png" alt="preferences
plugins tab"/>
<ul>
<a href="/ardours-interface/">Ardour's Interface</a>.
</p>
-<img src="/files/a4/a4_preferences_gui.png" alt="preferences
+<img src="/images/a4_preferences_gui.png" alt="preferences
gui tab"/>
<ul>
Metering</a> in Ardour.
</p>
-<img src="/files/a4/a4_preferences_metering.png" alt="preferences
+<img src="/images/a4_preferences_metering.png" alt="preferences
metering tab"/>
<ul>
This tab contains settings that change the visual appearence of Ardour.
</p>
-<img src="/files/a4/a4_preferences_theme.png" alt="preferences
+<img src="/images/a4_preferences_theme.png" alt="preferences
theme tab"/>
<ul>
menu_title: Session Properties
---
-<img src="/files/a4/a4_session_properties_timecode.png" alt="session properties dialog"/>
+<img src="/images/a4_session_properties_timecode.png" alt="session properties dialog"/>
<p>
This dialog allows you to change settings for the current session. These settings
menu_title: Timecode Tab
---
-<img src="/files/a4/a4_session_properties_timecode.png" alt="session properties timecode tab"/>
+<img src="/images/a4_session_properties_timecode.png" alt="session properties timecode tab"/>
<p>
This tab is used to change how Ardour interprets and manipulates timecode.
menu_title: Sync Tab
---
-<img src="/files/a4/a4_session_properties_sync.png" alt="session properties sync tab"/>
+<img src="/images/a4_session_properties_sync.png" alt="session properties sync tab"/>
<p>
This tab is used to modify the timecode settings when working with video to
menu_title: Fades Tab
---
-<img src="/files/a4/a4_session_properties_fades.png" alt="session properties fades tab"/>
+<img src="/images/a4_session_properties_fades.png" alt="session properties fades tab"/>
<p>
Change how Ardour works with region crossfades.
menu_title: Media Tab
---
-<img src="/files/a4/a4_session_properties_media.png" alt="session properties media tab"/>
+<img src="/images/a4_session_properties_media.png" alt="session properties media tab"/>
<p>
Change how sound is stored on disk. These options do not change how sound is handled
menu_title: Locations Tab
---
-<img src="/files/a4/a4_session_properties_locations.png" alt="session properties locations tab"/>
+<img src="/images/a4_session_properties_locations.png" alt="session properties locations tab"/>
<p>
These options add file locations that will be searched to find the audio and
menu_title: Filenames Tab
---
-<img src="/files/a4/a4_session_properties_filenames.png" alt="session properties filenames tab"/>
+<img src="/images/a4_session_properties_filenames.png" alt="session properties filenames tab"/>
<p>
This tab is used to change how Ardour names recorded regions.
Provides options affecting monitoring.
</p>
-<img src="/files/a4/a4_session_properties_monitoring.png" alt="session properties monitoring tab"/>
+<img src="/images/a4_session_properties_monitoring.png" alt="session properties monitoring tab"/>
<p>
The <strong>Track Input Monitoring automatically follows transport state</strong>
<a href="/recording/monitoring/monitor-setup-in-ardour/">Monitor Setup in Ardour</a>.
</p>
-<img class="left" src="/files/a4/a4_monitoring_section.png" alt="monitoring section"/>
+<img class="left" src="/images/a4_monitoring_section.png" alt="monitoring section"/>
<p>
The 'Use monitor section' displays an extra section in the <strong>Mixer</strong>
This tab changes what additional controls are also displayed.
</p>
-<img src="/files/a4/a4_session_properties_meterbridge.png" alt="session properties meterbridge tab"/>
+<img src="/images/a4_session_properties_meterbridge.png" alt="session properties meterbridge tab"/>
<ul>
<li>
</li>
</ul>
-<img src="/files/a4/a4_meterbridge_full.png" alt="image of meterbidge with all options on"/>
+<img src="/images/a4_meterbridge_full.png" alt="image of meterbidge with all options on"/>
This tab has several things that don't fit on the other tabs.
</p>
-<img src="/files/a4/a4_session_properties_misc.png" alt="session properties misc tab"/>
+<img src="/images/a4_session_properties_misc.png" alt="session properties misc tab"/>
<ul>
<li>
allows to seek through the video and displays basic file information.
It is also useful to check if the video format/codec is supported:
</p>
-<img src="/files/a3/a3_video_open.png" alt="video-open-dialog" width="300" />
+<img src="/images/a3_video_open.png" alt="video-open-dialog" width="300" />
<p>
The second step analyzes the video file in more detail and offers import options:
</p>
<dd>Useful for extracting audio only.</dd>
</dl>
-<img src="/files/a3/a3_video_import.png" alt="Video Import Dialog" width="300" />
+<img src="/images/a3_video_import.png" alt="Video Import Dialog" width="300" />
<p>
By default the video is imported using the original width/height.
<p>
Well now,..
</p>
-<img src="/files/a3/a3_videotimeline.png" alt="Video Timeline" width="600" />
+<img src="/images/a3_videotimeline.png" alt="Video Timeline" width="600" />
<h2 id="export">Exporting Video</h2>
<p>
presets.
</p>
-<img src="/files/a3/a3_video_export.png" alt="Video Export Dialog" width="300" />
+<img src="/images/a3_video_export.png" alt="Video Export Dialog" width="300" />
<p>
Ardour video export is not recommended for mastering! While ffmpeg
projects / ardour-manual-diverged / commitdiff
