2 Global <dfn>preferences</dfn> control general workflow and system
3 configuration, and should apply to all sessions. They are located in <kbd
4 class="menu">Edit > Preferences</kbd> and stored in Ardour's <dfn>user
5 configuration file</dfn> in the user's home directory.
8 <h2 id="general">General</h2>
12 <dfn>DSP CPU Utilization</dfn>
15 <dfn>Signal processing uses:</dfn> sets how many cpu processors can be
16 used to do signal processing. It can be set to use one up to all
22 <dfn>Memory Usage</dfn>
25 <dfn>Waveform image cache (megabytes):</dfn> sets the maximum amount of ram that
26 can be used to store the images representing the waveforms in the editor. Past
27 this amount, the images will be regenerated when needed, which can significantly
28 decrease the system's performance.
36 <dfn>Try to auto-launch audio/midi engine</dfn> allows Ardour to try to
37 automatically launch the audio and MIDI system, driver and device, thus not
38 showing the <a href="@@newopen-session-dialog">Audio/MIDI Setup</a> dialog. This
39 can save a little time if the system is always used the same way.
47 <strong>Thinning factor</strong> ranges from 0 to 1000 with larger
48 values sending fewer automation changes. Thinning is like lossy
49 audio compression, removing data that is less likely to be noticed,
50 although the more is removed, the more likely the loss will be noticed.
51 The advantage to thinning is reduced CPU usage.
54 <strong>Automation sampling interval</strong> ranges from 1 to
55 1000 ms. Determines how frequently the automation input is
56 sampled. The shorter the interval the higher the accuracy but also
57 the higher the CPU requirements.
65 <dfn>Allow non quarter-note pulse</dfn>: by default, Ardour understands the <a
66 href="@@tempo-and-meter">tempo</a> as the number of quarter notes in a minute.
67 Checking this option allows to set the tempo based on any division of the note,
68 from whole to 1/128th. This is reflected in the <kbd class="menu">Edit
69 Tempo</kbd> window (accessed by double clicking a tempo marker) that shows a
70 "Pulse" menu when this option is checked.
78 <dfn>Lock timeout (seconds):</dfn>locks the <abbr title="Graphical User
79 Interface">GUI</abbr> after this many idle seconds (zero being 'never lock').
80 The GUI can also be locked with <kbd class="menu">Session > Lock</kbd>. When
81 locked, a dialog will display a "Click to unlock" button.
87 <h3 id="session">Session</h3>
91 <dfn>Undo</dfn> defines the behaviour of the Undo operations:
94 <strong>Limit undo history</strong> sets how many commands can be
95 undone using <kbd class="mod1">Z</kbd> or <kbd class="menu">Edit > Undo</kbd>.
96 Unchecking will keep an endless memory of operations to undo, at the
100 <strong>Save undo history</strong> sets how many commands are saved so
101 they are available to be undone after reopening the session. This can
102 also be unchecked to keep all actions undoable, at the cost of bigger
106 <strong>Verify removal of last capture</strong> when enabled prompts to
107 verify removal the last recording capture when
108 <kbd class="menu">Edit > Remove Last Capture</kbd> is executed.
113 <dfn>Session Management</dfn>:
116 <strong>Make periodic backups of the session file</strong> will create
117 a backup session file after changes to the timeline. The backup file is
118 the session name followed by <em>.ardour.bak</em>. The backup can be
119 used to recover from crashes when the session had not been explicitly
123 <strong>Always copy imported files</strong> selects, and then disables
124 changes to, the <em>Copy files to session</em> option in the
125 <a href="@@import-dialog">Add Existing Media</a> dialog.
128 <strong>Default folder for new sessions:</strong> defaults the folder
129 where Ardour will create new session folders. This is used in the
130 <em>Session Setup</em> dialog displayed by
131 <kbd class="menu">Session > New</kbd>.
134 <strong>Maximum number of recent sessions:</strong> determines how many
135 of the last opened sessions shows in the
136 <em>Recent Sessions</em> dialog displayed by
137 <kbd class="menu">Session > Recent</kbd>.
143 <h3 id="translation">Translation</h3>
146 <dfn>Internationalization</dfn>
149 <dfn>Use translations</dfn> sets if Ardour should use a translated
150 version of all the messages. The default (unchecked) is English (US). When
151 checked, and if a language file exists for the system language, this file
152 will be used to translate Ardour.
158 <h2 id="editor">Editor</h2>
165 <dfn>Snap rubberband to grid</dfn> when
166 enabled uses the grid when <a href="@@select-regions">selecting regions</a>
167 with a rubberband rectangle.
170 <dfn>Prompt for new marker names</dfn> when enabled, popup a dialog
171 when a new <a href="@@working-with-markers">marker</a> is created. This allows
172 markers to be named as they are created.
175 <dfn>Allow dragging of the playhead</dfn>, when enabled, allows
176 dragging the playhead with the mouse in the <strong>Editor</strong> window.
179 <dfn>Playhead dragging speed (%):</dfn> chooses how fast the canvas
180 scrolls when dragging the playhead outside of the visible canvas.
183 <dfn>Limit zooming & summary view to X minutes beyond session extents</dfn>
184 prevents the zoom out both in the editor and the summary, to show anything past
185 the chosen time after the end marker, restraining the vision to only useful
189 <dfn>Zoom to mouse position when zooming with scroll wheel</dfn>: by default,
190 Ardour zooms to the <a href="@@edit-point-control">edit point</a>. When this
191 option is checked, and the zoom is done with <kbd class="mod1n"></kbd> + mousewheel,
192 the zoom will happen at the mouse cursor position regardless of the edit point
196 <dfn>Zoom with vertical drag in rulers</dfn> allows, when checked, to click
197 anywhere in an empty zone of the <a href="@@ruler">ruler</a> zone and drag
198 up to zoom in or down to zoom out.
201 <dfn>Double click zooms to selection</dfn> allows by double clicking, to zoom
202 on the selection, both on the time and tracks axes. If the selection has been
203 done with <kbd class="mod1n"></kbd> or <kbd class="mod3n"></kbd>, then this
204 key should still be pressed when double clicking for this to work, otherwise
205 the first click breaks the group selection.
208 <dfn>Update editor window during drags of the summary</dfn>: when
209 enabled the contents of the editor window will redraw the tracks area
210 as the selection rectangle in the <a href="@@summary">summary</a> area is
214 <dfn>Auto-scroll editor window when dragging near its edges</dfn>
215 when enabled will scroll the editor window automatically when dragging a
216 region. This can make it easier to see where to position the region.
219 <dfn>Show gain envelopes in audio regions:</dfn> sets in which
220 <a href="@@toolbox">modes</a> the gain envelope is displayed in audio regions.
221 The gain envelope is superimposed over the region in the selected modes, and
222 hidden otherwise for a better legibility.
228 <dfn>Editor Behaviour</dfn>
231 <dfn>Move relevant automation when audio regions are moved</dfn>,
232 when enabled, causes automation data to stay with a region when the
233 region is moved inside the playlist. When disabled, the automation is
234 not affected by movement of regions.
237 <dfn>Ignore Y-axis click position when adding new automation-points</dfn>
238 allows to create new automation points at the x-position of the mouse, without
239 using the Y-position as the value, hence creating a new automation point at
243 <dfn>Default fade shape:</dfn> sets which <a href="@@create-region-fades-and-crossfades">
244 fade shape</a> is the default.
247 <dfn>Regions in edit groups are edited together:</dfn> sets
248 the criteria to see if editing actions apply to tracks grouped together
252 <dfn>Layering model:</dfn> Ardour allows <a href="@@layering-display">layering</a>
253 multiple regions in the same track. This selector defines how these layers are
254 managed, either manually or by placing the latest on top.
257 <dfn>After splitting selected regions, select:</dfn> determines which,
258 if any, regions are selected after a split operation. The options are no
259 regions, the regions created by the split, and if more than one region
260 was selected to start with, the existing selection and the new regions.
266 <h3 id="modifiers">Modifiers</h3>
269 This page allows to choose how things are done in the editor. This is a very
270 flexible way for Ardour to match an existing workflow, or speed up the editing
271 process based on the user's most used actions.
274 The <kbd class="menu">Reset to recommended defaults</kbd> button at the bottom
275 provides a way to revert any user made change to its default value.
278 <h2 id="mixer">Mixer</h2>
282 <dfn>Solo</dfn> contains settings that affect the use of
283 <a href="@@muting-and-soloing">solo, muting</a>, and
284 <a href="@@panning">panning</a>.
287 <dfn>Solo controls are Listen controls</dfn>: when enabled, the
288 soloed track is soloed only on the monitor bus, the master fader mix
289 is not affected by the solo. This option can also be set by enabling
290 pre-fader listen or after-fader listen in the <strong>Mixer</strong>
294 <dfn>Exclusive solo</dfn> when enabled will only solo the last
295 track selected for solo. Previously soloed tracks will be un-soloed.
296 This setting is also available from the <strong>Mixer</strong> monitor
300 <dfn>Show solo muting</dfn> when enabled outlines the mute
301 button on tracks and busses when another track is soloed.
304 <dfn>Soloing overrides muting</dfn> when enabled allows a track
305 to be heard when it is soloed while muted. This setting is also
306 available from the <strong>Mixer</strong> monitor section.
309 <dfn>Solo-in-place mute cut (dB):</dfn> sets the attenuation of
310 the other tracks when another track is soloed in place. This setting
311 is also available from the <strong>Mixer</strong> monitor section. The
312 default is "−inf" for −∞, meaning the other tracks are
316 <dfn>Listen Position:</dfn> determines what is listened to when
317 the solo controls are used as listen controls. The options are
318 after-fader or pre-fader.
321 <dfn>PFL signals come from:</dfn> determines whether the
322 pre-fader listen position is before or after the pre-fader processors.
325 <dfn>AFL signals come from:</dfn> determines whether the
326 after-fader listen position is before or after the after-fader
333 <dfn>Default Track / Bus Muting Options</dfn> sets the muting options
334 for a newly created tracks or bus. The mute options for an existing track
335 or bus are changed by the right-click context menu on a mute button.
338 <dfn>Mute affects pre-fader sends</dfn> when enabled pre-fader
339 sends will be muted by default.
342 <dfn>Mute affects post-fader sends</dfn> when enabled post-fader
343 sends will be muted by default.
346 <dfn>Mute affects control outputs</dfn> when enabled control
347 outputs are muted by default.
350 <dfn>Mute affects main outputs</dfn> when enabled main outputs
351 are muted by default.
357 <dfn>Send Routing</dfn> affects <a href="@@aux-sends">aux and external sends</a>.
360 <dfn>Link panners of Aux and External Sends with main panner by default</dfn>
361 when enabled, sends follow the channel panner. When disabled, sends can panned
362 independently of the channel panner and fader. Double clicking the send in the
363 processor box toggles the main panner and fader between the aux send and the
371 <h2 id="signal_flow">Signal Flow</h2>
375 <dfn>Monitoring</dfn>
378 <dfn>Record monitoring handled by:</dfn> determines whether Ardour provides
379 monitoring of incoming audio or whether monitoring is provided by hardware.
380 See <a href="@@monitoring">Monitoring</a> for more information.
383 <dfn>Tape machine mode</dfn> when enabled defaults new audio tracks to
384 tape machine mode. See <a href="@@track-types">Track Types</a> for more
391 <dfn>Track and Bus Connections</dfn>
394 <dfn>Auto-connect main output (master or monitor) bus to physical ports</dfn>
395 auto-connects the outputs to the first N physical ports. In a session without a
396 <a href="@@monitor-section">monitor section</a>, the master-bus is
397 connected to the system's playback ports, and if a monitor section exists,
398 the monitor-bus' output are connected.
401 <dfn>Connect track inputs:</dfn> allows to choose when a new track is
402 created whether its inputs will be automatically connected to the physical
403 inputs of the system or not (hence the user has to manually connect it).
406 <dfn>Connect track and bus outputs:</dfn> allows to choose, for any new
407 track or bus created, whether its output will automatically be connected
408 to the master bus, directly to the physical outputs or to nothing (the
409 user has to manually connect it).
412 <dfn>Use 'Strict-I/O' for new tracks or busses</dfn> determines the default
413 choice for the <a href="@@trackbus-signal-flow">signal flow</a> of a newly created track or bus.
414 This can be overridden in the <a href="@@adding-tracks-busses-and-vcas">
415 Add Track/Bus/VCA</a> dialog
421 <h2 id="audio">Audio</h2>
425 <dfn>Buffering</dfn> settings determine how many seconds of audio off of disk
426 will be buffered in memory. Longer settings reduce the risk of buffer
427 under-runs but consume more memory.
430 <dfn>Preset:</dfn> will automatically choose the values for the playback
431 and recording buffer based on the chosen size of the session. The
432 <strong>Custom</strong> option allows to manually select the buffers with
433 the two sliders below.
436 <dfn>Playback (seconds of buffering):</dfn> sets how many seconds of
437 audio Ardour will buffer during playback.
440 <dfn>Recording (seconds of buffering):</dfn> sets how many seconds of
441 audio Ardour will buffer during recording.
447 <dfn>Denormals</dfn> are a specific type of very small numbers that
448 can cause issues with CPU consumption when using some plugins in some
450 Ardour provides two methods of handling the issue. Trying different
451 combinations of these settings may minimize CPU consumption.
454 <dfn>Use DC bias to protect against denormals</dfn> adds a small
455 constant value to numbers to move the numbers away from zero.
458 <dfn>Processor handling:</dfn>, if the computer's hardware
459 supports it, offers two methods that can be used individually or
460 combined. Flush to zero and denormals are zero.
469 <dfn>Enable automatic analysis of audio</dfn> generates the transient
470 values (used in e.g. the <a href="@@rhythm-ferret">Rhythm Ferret</a>)
471 automatically. When unchecked, the transient values will be generated
475 <dfn>Replicate missing region channels</dfn>: if a track is N-channel,
476 and the region has fewer channels, this option copies the existing
477 channel's data for this non-existent one. If left unchecked, the missing
478 channels will stay silent.
484 <h2 id="midi">MIDI</h2>
491 <dfn>MIDI read-ahead time (seconds):</dfn> defines how much time of MIDI data
492 must be read in advance by Ardour and put in the buffer. More time means more
493 stability while playing back, at the expense of more time to buffer the data.
494 This should be set to a low value for a reasonably capable machine.
503 <dfn>Initial program change:</dfn> Ardour will send a MIDI program
504 change message on the <code>ardour:MMC out</code> JACK port when a session
505 is loaded and whenever this field is changed. A value of -1 means don't
506 send any program change message.
515 <dfn>Sound MIDI notes as they are selected in the editor</dfn> will play
516 any selected or added MIDI note when in Draw or Internal Edit modes. The
517 note is sent as MIDI as if Ardour was playing it withe the session, so the
518 processors and signal routing will be applied.
521 <dfn>Midi Audition Synth (LV2):</dfn> allows to select in the list of LV2
522 instruments, which one will be used to audition MIDI when e.g. in the
523 <a href="@@import-dialog">import dialog</a>.
529 <h2 id="metronome">Metronome</h2>
533 <dfn>Metronome</dfn> handles the way Ardour's metronome is played when
534 enabled in the <a href="@@transport-bar">Transport Bar</a>.
537 <dfn>Emphasis on first beat</dfn> plays a different sound when the first
538 beat is played (e.g. 1/4 in 4/4, 1/3 in 3/4,…). When unchecked, all
539 the beats are indistinguishable.
542 <dfn>Use built-in default sounds</dfn> when checked, uses Ardour's own
543 sounds for the metronome click. Unchecking this allows to set some custom
547 <dfn>Audio file:</dfn> selects an audio file for the beats, in any
548 <a href="@@supported-file-formats">format</a> Ardour supports.
551 <dfn>Emphasis audio file:</dfn> in conjunction with
552 <kbd class="option">Emphasis on first beat</kbd>, selects an audio file
553 for the first beats of each bar.
556 <dfn>Gain level:</dfn> allows the metronome's click sounds to be boosted
566 <dfn>Enable Metronome only while recording</dfn>: when enabled, the
567 metronome will remain silent unless Ardour is recording.
573 <h2 id="metering">Metering</h2>
580 <dfn>Peak hold time:</dfn> allows the meter to keep displaying the highest
581 signal level for a period of time before reverting to showing the actual
582 instantaneous value (unless an even higher peak occurs). The longer this
583 time is, the easier it is to spot peaks, at the expense of instantaneous
587 <dfn>DPM fall-off:</dfn> describes how fast the Digital Peak Meters can
588 go from a high value to a lower one. Faster values are more accurate but
592 <dfn>Meter line-up level; 0 dBu:</dfn> chooses a standard for the
593 conversion between dBFS (Full Scale) which represent the numeric signal
594 level, and dBu which represents the analog signal level. This value is used
595 to configure meter-marks and color knee-points, or set the reference levels
596 for various meter-types.
599 <dfn>IEC1/DIN Meter line-up level; 0 dBu:</dfn> sets the reference
600 level for the IEC1/DIN Meter
603 <dfn>VU Meter standard:</dfn> selects which standard to use for the zero
604 value of the vu-meters, i.e. the analog dBu value that will show as 0 on the
608 <dfn>Peak indicator threshold [dBFS]:</dfn> at that value and over, the
609 signal will make the peak meter to turn red, indicating a level too high.
615 <dfn>Default Meter Types</dfn> sets the default meters when creating a session
616 or track. These meters can be changed afterwards by
617 <kbd class="mouse">right</kbd>-clicking a meter.
620 <dfn>Default Meter Type for Master Bus:</dfn> defines which kind of
621 <a href="@@metering-in-ardour">meter</a> will be used when creating a new
622 session (does not apply to the current session).
625 <dfn>Default Meter Type for busses:</dfn> defines which kind of
626 meter will be used when creating a new bus (applies to the bus created
627 after changing the value).
630 <dfn>Default Meter Type for tracks:</dfn> same as above, for tracks.
636 <dfn>Post Export Analysis</dfn>
639 <dfn>Save loudness analysis as image file</dfn> allows, when the
640 <kbd class="option">Analyze Exported Audio</kbd> is checked in the
641 <a href="@@export-dialog">Export dialog</a>, to save the analysis graph
642 as a file named <code>session.png</code> alongside the exported audio
643 file(s) (in the same folder).
649 <h2 id="transport">Transport</h2>
656 <dfn>Stop at the end of the session</dfn> causes the transport to
657 stop during playback when it reaches the end marker. Behavior during
658 recording is not changed.
661 <dfn>Keep record-enable engaged on stop</dfn> leaves the global
662 record-enable engaged after transport is stopped. Does not affect track
663 level record-enable which is never changed on stop.
666 <dfn>Disable per-track record disarm while rolling</dfn>, when
667 enabled, will not allow the any track's record-enable to be disarmed
668 during record, preventing accidentally stopping the recording of a take.
671 <dfn>12dB gain reduction during fast-forward and fast-rewind</dfn>
672 when enabled will reduce the unpleasant increase in perceived volume
673 that occurs when fast-forwarding or rewinding through some kinds of audio.
676 <dfn>Preroll:</dfn> sets the duration of the preroll for playing and
677 recording when using a preroll. Can be a musical duration (in bars) or a
687 <dfn>Play loop is a transport mode</dfn> changes the behavior of the
688 loop button, turning it into a toggle. When enabled, the loop button does
689 not start playback but forces playback to always play the loop. Looping
690 stays engaged when the transport is stopped. Playback continues where the
691 transport stopped and continues to loop. When disabled, the loop button
692 starts playing the loop but stop then cancels loop playback.
695 <dfn>Do seamless looping</dfn> removes any clicks that might
696 otherwise be audible when the transport moves from the end of the loop
697 range back to the beginning.
703 <dfn>Dropout (xrun) Handling</dfn>
706 <dfn>Stop recording when an xrun occurs</dfn> will stop the transport
707 when an xrun occurs during recording, ensuring no audible glitches are
711 <dfn>Create markers where xruns occur</dfn> will create a new
712 <a href="@@working-with-markers">marker</a> when an xrun occurs during
713 recording at the location of the xrun. This marks where possible xruns
714 might produce audible glitches.
720 <h2 id="sync">Sync</h2>
724 <dfn>External Synchronization</dfn>
727 <dfn>External timecode source</dfn> determines which external source to
728 use when Ardour is using an external
729 <a href="@@working-with-synchronization">synchronization</a> source.
730 Depending on the timecode source chosen, the additional preference options
734 <dfn>Match session video frame rate to external timecode</dfn>
735 controls the value of the video frame rate <em>while chasing</em>
736 an external timecode source. When enabled, the session video frame rate will be
737 changed to match that of the selected external timecode source. When disabled,
738 the session video frame rate will not be changed to match that of the selected
739 external timecode source. Instead, the frame rate indication in the main clock
740 will flash red and Ardour will convert between the external timecode standard
741 and the session standard.
744 <dfn>Sync-lock timecode to clock (disable drift compensation)</dfn>
745 When enabled, Ardour will never varispeed when slaved to external
746 timecode. Sync Lock indicates that the selected external timecode
747 source shares clock-sync (Black & Burst, Wordclock, etc) with
748 the audio interface. This options disables drift compensation.
749 The transport speed is fixed at 1.0. Vari-speed LTC will be ignored
750 and cause drift. When disabled, Ardour will compensate for potential
751 drift regardless if the timecode sources shares clock sync.
754 <dfn>Lock to 29.9700 fps instead of 30000/1001</dfn>, when
755 enabled, will force Ardour to assume the external timecode source
756 uses 29.97 fps instead of 30000/1001.
757 SMPTE 12M-1999 specifies 29.97 df as 30000/1001. The spec
758 further mentions that drop-frame timecode has an accumulated error
759 of -86 ms over a 24 hour period. Drop-frame timecode would
760 compensate exactly for an NTSC color frame rate of 30 × 0.9990 (i.e.
761 29.970000). That is not the actual rate. However, some vendors use
762 that rate—despite it being against the specs—because the
763 variant of using exactly 29.97 fps has zero timecode drift.
769 <h3 id="ltc">LTC</h3>
773 <dfn>Linear Timecode (LTC) Reader</dfn>
776 <dfn>LTC incoming port:</dfn> specifies which physical incoming port of
777 the system will provide the LTC signal.
783 <dfn>Linear Timecode (LTC) Generator</dfn>
786 <dfn>Enable LTC generator</dfn> when enabled Ardour will
787 output an LTC timecode signal on its <em>LTC-out</em> port.
788 If this option is checked, the two options below are active:
791 <dfn>Send LTC while stopped</dfn>, when enabled Ardour will
792 continue to send LTC information even while the transport (playhead) is
796 <dfn>LTC generator level [dBFS]:</dfn> specifies the peak volume of
797 the generated LTC signal in dbFS. A good value is 0dBu=−18dbFS
798 in an EBU calibrated system.
804 <h3 id="sync_midi">MIDI</h3>
808 <dfn>MIDI Beat Clock (Mclk) Generator</dfn>
811 <dfn>Enable Mclk generator</dfn> when enabled Ardour will generate a
812 (tempo dependant) beat clock at a rate of 24 pulses per quarter note on
813 the <code>ardour:MIDI clock out</code> JACK port.
819 <dfn>MIDI Time Code (MTC) Generator</dfn>
822 <dfn>Enable MTC Generator</dfn> when enabled Ardour will generate MIDI
823 time code on the <code>ardour:MTC out</code> JACK port.
826 <dfn>Percentage either side of normal transport speed to transmit MTC:</dfn>
827 MIDI time code generation will be disabled when the transport speed is
828 greater than normal speed plus this percentage or less than normal minus
835 <dfn>MIDI Machine Control (MMC)</dfn>
838 <dfn>Respond to MMC commands</dfn> when enabled Ardour will respond
839 to MIDI Machine Control commands received on the <code>ardour:MMC in</code>
843 <dfn>Send MMC commands</dfn> when enabled Ardour will send MIDI Machine
844 Control commands on the <code>ardour:MMC out</code>
848 <dfn>Inbound MMC device ID:</dfn> is the only device ID Ardour will
849 respond to when an MMC command is received on the <code>ardour:MMC in</code>
853 <dfn>Outbound MMC device ID:</dfn> is the MIDI device ID Ardour will
854 use when it sends MMC commands.
860 <h2 id="control_surfaces">Control Surfaces</h2>
863 This tab contains settings for <a href="@@control-surfaces">control surfaces</a>.
866 It lists all the Control Surface protocols Ardour knows. To enable a
867 <dfn>Control Surface Protocol</dfn>, the <kbd class="option">Enable</kbd> checkbox
868 next to its name should be ticked. Editing the settings related to this protocol
869 can be done by double-clicking its name or clicking the <kbd class="menu">Show
870 protocol settings</kbd> (only for Generic MIDI and Open Sound Control).
873 <h2 id="midi_ports">MIDI Ports</h2>
877 <dfn>MIDI Port Options</dfn>
880 <dfn>MIDI input follows MIDI track selection</dfn> allows Ardour to automatically
881 connect the MIDI input to the selected track. Selecting a different MIDI
882 track results in Ardour disconnecting the MIDI device from the former track
883 and connecting it to the newly selected one, so that the MIDI device is
884 always connected to the selected track. Which MIDI device will follow
885 selection can be chosen below.
891 <dfn>MIDI Inputs</dfn> This is a list of all the MIDI devices connected as
892 inputs (capture devices) to Ardour. For each devices, there are 3 checkboxes:
895 <dfn>Music Data</dfn> if checked, Ardour will consider this device as a source
896 for musical data input (notes, etc…)
899 <dfn>Control Data</dfn> if checked, Ardour will consider this device as a source
900 for control data input (play/stop, etc…)
903 <dfn>Follow selection</dfn> if the above
904 <kbd class="option">MIDI input follows MIDI track selection</kbd> is
905 checked, Ardour will make this device follow track selection.
911 <dfn>MIDI Outputs</dfn> This is a list of all the MIDI devices connected as
912 outputs (playback devices) to Ardour. For each devices, there are 2 checkboxes:
915 <dfn>Music Data</dfn> if checked, Ardour will consider this device as a target
916 for musical data output (notes, etc…)
919 <dfn>Control Data</dfn> if checked, Ardour will take this device as a target
920 for control data output (play/stop, etc…)
926 <h2 id="plugins">Plugins</h2>
929 The content of this preference page varies heavily between versions or Ardour:
930 both the platform and the build-time options can make Ardour support some types
931 of plugins and not others. While this documentation tries to show all possible
932 options, most systems will only show a subset of the options hereunder, e.g.
933 AudioUnits are macOS only…
938 <dfn>Scan/Discover</dfn>
941 <dfn>Scan for Plugins</dfn> will initiate an immediate scan of the system
942 for available plugins. Useful to get a newly installed plugin recognised
952 <dfn>Always Display Plugin Scan Progress</dfn> When enabled a
953 popup window showing plugin scan progress is displayed for indexing
954 (cache load) and discovery (detect new plugins).
957 <dfn>Silence plugins when the transport is stopped</dfn> when stopping
958 playback or recording, if this option is checked, the plugins that still
959 emit sound (reverbs, etc…) will be stopped. If unchecked, the plugins
960 will continue playing after the transport stop.
963 <dfn>Make new plugins active</dfn> when enabled, any plugin added to a track
964 will be in active mode. If unchecked, the plugins will be added in inactive
965 mode by default, hence have no processing effect on the track/bus.
968 <dfn>Limit automatable parameters per plugin</dfn>: as some plugins
969 (synthesizers, …) have a lot of parameters, and those parameters
970 can be automated by Ardour, checking this will limit the number of parameters
971 that are listed as automatable, hence making the lists shorter and the GUI
978 <dfn>Plugin GUI</dfn>
981 <dfn>Automatically open the plugin GUI when adding a new plugin</dfn>
982 shows the plugins GUI as soon as it is added to the processing box. If
983 unchecked, the plugin will be added in the processor box but the GUI will
984 only be shown when <kbd class="mouse">double clicking</kbd> it.
987 <dfn>Show Plugin Inline Display on Mixer strip by default</dfn> allows Ardour
988 to show, in the <a href="@@audiomidi-mixer-strips">mixer strips</a>, a
989 visual rendering of the effect. These Inline Display are a special feature
990 of Ardour, so not all plugins are able to show this display. Most of Ardour's
991 <a href="@@plugins-bundled-with-ardour">own plugins</a> have an Inline Display.
992 At any time, the plugin's Inline Display can be toggled on or off by
993 <kbd class="mod3n"></kbd>double-clicking it.
996 <dfn>Don't automatically open the plugin GUI when the plugin has an inline
997 display mode</dfn>: this option, available only if
998 <kbd class="option">Automatically open the plugin GUI when adding a new plugin</kbd>
999 is checked, supercedes it and hides the plugin GUI at creation if it has an
1000 Inline Display, like Ardour's own <code>a-*</code> plugins.
1006 <dfn>Instrument</dfn>
1009 <dfn>Ask to replace existing instrument plugin</dfn>: if a MIDI track already
1010 has an instrument (i.e. MIDI to audio converter of some sort) and this
1011 option is checked, Ardour will detect it and offer to replace the existing
1012 instrument with the newly added one, avoiding a possible conflict.
1015 <dfn>Interactively configure instrument plugins on insert</dfn>: when inserting
1016 a multichannel instrument plugin, if this option is checked, prompts the
1017 user for the channel configuration for this plugin.
1023 <h3 id="vst">VST</h3>
1030 <dfn>Enable Mac VST support (requires restart or re-scan)</dfn> makes a
1031 MacOs system able to run VST-Mac plugins. As stated, a new scan for plugins
1032 is required, be it manually or by restarting Ardour.
1035 <dfn>Scan for [new] VST Plugins on Application Start</dfn> When
1036 enabled new VST plugins are searched, tested and added to the cache
1037 index on application start. When disabled new plugins will only be
1038 available after triggering a 'Scan' manually.
1041 <dfn>Verbose Plugin Scan</dfn>: adds information about the plugin in the
1042 <a href="@@status-bar">Log window</a>.
1045 <dfn>Scan Time Out</dfn> Specifies the default timeout for plugin
1046 instantiation. Plugins that require more time to load will be
1047 blacklisted. A value of ∞ disables the timeout.
1050 <dfn>VST Cache:</dfn> Clicking the <kbd class="menu">Clear</kbd> button
1051 removes all VST plugins from the list of plugins available to be
1052 inserted into the processor box. A new VST plugin scan is then required.
1055 <dfn>VST Blacklist:</dfn> Clicking the <kbd class="menu">Clear</kbd>
1056 button makes blacklisted VST plugins available to be added to the processor
1060 <dfn>Linux VST Path:</dfn> Clicking the <kbd class="menu">Edit</kbd> button
1061 pops up a dialog to manage the directories that will be searched for Linux
1062 VST plugins. When modified, Ardour will offer to scan those paths for plugins.
1065 <dfn>Path:</dfn> are the paths chosen above.
1068 <dfn>Windows VST Path:</dfn> Clicking the <kbd class="menu">Edit</kbd> button
1069 pops up a dialog to manage the directories that will be searched for Windows
1070 VST plugins. When modified, Ardour will offer to scan those paths for plugins.
1073 <dfn>Path:</dfn> are the paths chosen above.
1079 <h3 id="audio_unit">Audio Unit</h3>
1083 <dfn>Audio Unit</dfn>
1086 <dfn>Scan for [new] AudioUnit Plugins on Application Start</dfn> When
1087 enabled, new AU plugins are searched, tested and added to the cache
1088 index on application start. When disabled, new plugins will only be
1089 available after triggering a 'Scan' manually.
1092 <dfn>AU Cache:</dfn> Clicking the <kbd class="menu">Clear</kbd> button
1093 removes all AU plugins from the list of plugins available to be
1094 inserted into the processor box. A new AU plugins scan is then required.
1097 <dfn>AU Blacklist:</dfn> Clicking the <kbd class="menu">Clear</kbd>
1098 button makes blacklisted AU plugins available to be added to the processor
1105 <h2 id="appearance">Appearance</h2>
1109 <dfn>Graphics Acceleration</dfn>
1112 <dfn>Possibly improve slow graphical performance (requires restart)</dfn>
1113 Ardour uses hardware accelerated gradient creation by default for speed.
1114 Sometimes though, a buggy driver can cause this to make the system slow or
1115 unstable. Checking this will make Ardour draw its own gradients without
1116 hardware acceleration, improving stability and responsiveness on those
1123 <dfn>Graphical User Interface</dfn>
1126 <dfn>Highlight widgets on mouseover</dfn>, when checked, makes Ardour's
1127 widgets (buttons, sliders, …) slightly change color when the mouse
1128 hovers them, visually indicating what a mouse action would interact with.
1131 <dfn>Show tooltips if mouse hovers over a control</dfn> when checked,
1132 displays a little help bubble about the control the mouse hovers. The mouse
1133 pointer needs to stay idle for about 1 sec for the tooltip to appear.
1136 <dfn>Update clocks at TC Frame rate</dfn>: Ardour updates its clocks every
1137 100 ms. Checking this will make the clock refresh at every TimeCode
1138 frame which is more responsive, at the cost of a bit more system stress.
1141 <dfn>Blink Rec-Arm buttons</dfn>: when enabled, the record-armed
1142 buttons on tracks will blink when they are armed but not currently recording.
1143 When disabled, the record-armed buttons on tracks will be outlined in red
1144 instead of blinking. The global record-arm button in the
1145 <a href="@@transport-bar">Transport bar</a> is unaffected.
1148 <dfn>Blink Alert indicators</dfn>: when enabled, the Alert indicators (like
1149 the <kbd class="menu">Error Log</kbd> or the <kbd class="menu">Feedback</kbd>
1150 button) will blink when they are active (when an error or feedback
1151 has been detected, respectively). When disabled, the indicators will turn red instead of
1155 <dfn>GUI and Font scaling:</dfn> allows the display size of most of the
1156 text and buttons in the user interface to be scaled up or down. May
1157 require a restart to take effect.
1163 <h3 id="appearance_editor">Editor</h3>
1170 <dfn>Use name highlight bars in region displays (requires a restart)</dfn>:
1171 when enabled, the region name is displayed, in the editor, in its own opaque bar
1172 at the bottom of the region. When disabled, the region name is overlaid
1173 at the top of the region, possibly over audio waveforms or MIDI notes.
1176 <dfn>Region color follows track color</dfn>: when enabled,
1177 the background color of regions in the editor will be displayed using
1178 the color assigned to the track. When disabled the default region
1179 background color will be used.
1185 <dfn>Waveforms</dfn>
1188 <dfn>Show waveforms in regions</dfn> when enabled shows a visual
1189 representation of the region's audio waveform.
1192 <dfn>Show waveform while recording</dfn> when
1193 enabled, will draw the audio waveform in regions being recorded, in near
1194 real time. When disabled, only a region block will be drawn while recording,
1195 reducing CPU requirements.
1198 <dfn>Show waveform clipping</dfn>: when enabled the waveform
1199 displayed will show peaks marked in red if they exceed the clip level.
1202 <dfn>Waveform Clip Level (dBFS):</dfn> sets the level at which the
1203 waveform shown in an audio region will be drawn in red to indicate
1204 clipping. Setting lower than 0.0 dBFS can be useful if any tool in
1205 the audio chain has problems near 0.0 dBFS.
1208 <dfn>Waveform scale:</dfn> when waveforms are shown in audio regions,
1209 they can be displayed using a <em>linear</em> or a <em>logarithmic</em>
1210 scale. See <a href="@@waveform-display">Waveform display</a>.
1213 <dfn>Waveform shape:</dfn> when waveforms are shown in audio regions,
1214 they can be displayed using a <em>traditional</em> or a <em>rectified</em>
1215 shape. See <a href="@@waveform-display">Waveform display</a>.
1221 <dfn>Editor Meters</dfn>
1224 <dfn>Show meters in track headers</dfn>, when enabled, shows
1225 a small meter in the Editor's <a href="@@audio-track-controls">track headers</a>.
1226 The meter is shown on the right side area of the header and provides an
1227 instant, if unprecise, view of the levels on this track/bus.
1230 <dfn>Limit track header meters to stereo</dfn>: if a track has more than
1231 two outputs (e.g. with a drum plugin), limits the number of meters in the
1232 track header to the first two ones. Only affects audio meters, not MIDI.
1238 <dfn>MIDI Regions</dfn>
1241 <dfn>Display first MIDI bank/program as 0</dfn>: when patches and bank changes
1242 are displayed in the editor, if this option is checked, the numbering will
1243 be zero-based instead of one-based, i.e. banks/programs will be numbered
1244 O, 1 ,2… instead of 1, 2, 3…
1247 <dfn>Don't display periodic (MTC, MMC) SysEx messages in MIDI Regions</dfn>:
1248 if checked, will hide these control messages from the MIDI regions for better
1255 <h3 id="appearance_mixer">Mixer</h3>
1259 <dfn>Mixer Strip</dfn>
1262 This table enables (checked) or disables (unchecked) the display of controls
1263 in the <a href="@@audiomidi-mixer-strips">mixer strip</a>. Controls whose
1264 display can be toggled are:
1265 <strong>Input</strong>, <strong>Phase Invert</strong>,
1266 <strong>Record & Monitor</strong>, <strong>Solo Iso/Lock</strong>,
1267 <strong>Output</strong>, <strong>Comments</strong> and VCA Assigns.
1270 <dfn>Use narrow strips in the mixer for new strips by default</dfn> When
1271 enabled, new mixer strips are created in narrow format. When disabled,
1272 they are created in wide format. Existing mixer strips width can be toggled
1273 with the width control at the top left of the mixer strip.
1279 <h3 id="toolbar">Toolbar</h3>
1283 <dfn>Main Transport Toolbar Items</dfn>: this section allows to toggle the
1284 visibility of some elements of the main toolbar:
1287 <dfn>Display Record/Punch Options</dfn> toggles the visibility of the
1288 <a href="@@selection-and-punch-clocks#punch_controls">punch and record</a> slice of
1292 <dfn>Display Monitor Options</dfn> toggles the visibility of the
1293 <a href="@@other-toolbar-items#monitor-options">monitor options</a> slice of
1297 <dfn>Display Selection Clock</dfn> toggles the visibility of the
1298 <a href="@@selection-and-punch-clocks#selection_clocks">selection clocks</a> slice of
1302 <dfn>Display Secondary Clock</dfn> toggles the visibility of the
1303 <a href="@@transport-clocks">secondary clocks</a> slice of
1307 <dfn>Display Navigation Timeline</dfn> toggles the visibility of the
1308 <a href="@@mini-timeline">navigation/mini timeline</a> slice of
1312 <dfn>Display Master Level Meter</dfn> toggles the visibility of the
1313 <a href="@@other-toolbar-items#mode_selector">selection clocks</a> slice of
1320 <dfn>Lua Action Script Button Visibility</dfn> enables or disables the visibility
1321 of the four columns of <a href="@@other-toolbar-items#mode_selector">Lua script buttons</a>.
1322 Each columns contains two user-assignable buttons.
1326 <h3 id="theme">Theme</h3>
1333 <dfn>Draw "flat" buttons</dfn>: when enabled, button controls
1334 in the user interface will be drawn with a flat look. When disabled button
1335 controls will have a slight 3D appearance.
1338 <dfn>LED meter style</dfn> if checked, the bar meters in the editor and
1339 mixer will be styled to look like if they were made of LEDs, with a dotted
1340 bar. Unchecking this option makes the bars flat and continuous.
1343 <dfn>Waveforms color gradient depth:</dfn> determines how much gradient
1344 effect is applied to the inner of audio waveforms displayed in the editor.
1345 Values range from 0.0, no gradient effect, to 1.0, maximum effect.
1348 <dfn>Timeline item gradient depth:</dfn> Determines how much
1349 gradient effect is applied to the backgrounds of regions displayed in the
1350 editor. Values range from 0.0, no gradient effect, to 1.0, maximum effect.
1353 <dfn>Icon Set:</dfn> Changes the mouse cursor icons used to indicate
1354 different tool modes in the editor. An example would be the icons used to
1355 indicate whether the cursor will select a region or change the length of a
1362 <h3 id="colors">Colors</h3>
1369 <dfn>Color Theme</dfn> allows to switch between some presets bundled with
1370 Ardour, changing both the palette and items colors, hence styling Ardour
1374 The table allows to change the color settings in Ardour by acting on three
1378 <dfn>Items</dfn> that allow to choose any color from the palette (see below)
1379 to color a UI element. Clicking on a color sample in the <strong>Color</strong>
1380 column bring up the Palette, to choose from.
1383 <dfn>Palette</dfn> that allows to create a set of colors that will be used
1384 in the UI. Using a palette allows for better consistency, instead of
1385 picking "free" colors for each UI element. Clicking on a color patch brings
1386 up a full color selector, to assign this color to this patch of the palette.
1389 <dfn>Transparency</dfn> where possible, allows to select, with a slider,
1390 the transparency of the UI element, with 0 (slider to the left) being
1396 <dfn>Restore Defaults</dfn> turns all the palette, item colors and transparency
1397 back to Ardour's default base setting, in case Ardour's appearance has turned
1398 into a toddler's toy.
1404 <h3 id="quirks">Quirks</h3>
1408 <dfn>Various Workarounds for Windowing Systems</dfn>: As Ardour is available
1409 on a number of platforms and windowing systems, some specific workarounds are
1410 sometimes required to provide a smooth experience to the user.
1413 <dfn>Use visibility information provided by your Window Manager/Desktop</dfn>
1414 allows the system window manager's rules for the windows visibility to
1418 <dfn>All floating windows are dialogs</dfn>: when enabled, Ardour will
1419 use type "Dialog" for all floating windows instead of using type
1420 "Utility" for some of them. This may help usability with some
1421 window managers. This setting requires a restart of Ardour to take effect.
1424 <dfn>Transient windows follow front window.</dfn>: when enabled,
1425 transient windows will follow the front window when toggling between the
1426 editor and mixer. This setting requires a restart of Ardour to take effect.
1429 <dfn>Float detached monitor-section window</dfn>: as the <a href="@@monitor-section">
1430 monitor section</a> can be detached from the mixer, this option makes it a
1431 floating window, which may be handled differently by the windowing system
1432 and easier to access.
1438 <h2 id="video">Video</h2>
1442 <dfn>Video Server</dfn>
1445 <dfn>Show Video Export Info before export</dfn> Shows a warning message
1446 when exporting a video about licensing and offers to open the
1447 <a href="@@workflow-amp-operations#export">export video</a> section of
1451 <dfn>Show Video Server Startup Dialog</dfn>: when using video inside Ardour,
1452 this video is accessed via Xjadeo from a source file through a Video Server.
1453 This options shows the server's startup dialog (useful for debugging a
1454 malfunctioning video).
1457 <dfn>Advanced Setup (remote video server)</dfn> can be used when the setup
1458 is more complex than opening a local file with Ardour. The tools used behind
1459 the scene by Ardour allow a lot of flexibility, so for a competent user,
1460 the options below are provided to access a distant file (i.e. on another
1461 machine). The default options for the two following fields ("http://localhost:1554"
1462 and "/") are suitable for local files.
1465 <dfn>Video Server URL:</dfn> Base URL of the video server delivering the video
1466 through the network (<code>http://IP-or-address:port</code>).
1469 <dfn>Video folder</dfn> is the server's local path to the document-root,
1470 i.e. the files that can be delivered by the server.
1476 <dfn>Video Monitor</dfn>
1479 <dfn>Custom Path to Video Monitor (xjadeo) - leave empty for default:</dfn>
1480 Ardour bundles offer xjadeo bundled, so it should run flawlessly. Though,
1481 for custom builds or if a newer version of xjadeo is available, one can
1482 specify a path to the wanted version of xjadeo.