<dfn>Timecode Settings</dfn>
<ul>
<li>
- <dfn>Timecode frames-per-second:</dfn> defines how many frames of
+ <dfn>Timecode frames-per-second</dfn>: defines how many frames of
timecode are in one second. This can differ from the actual frame rate
depending on the standard used.
</li>
<li>
- <dfn>Pull-up / pull-down:</dfn> sets the speed correction to match one
+ <dfn>Pull-up / pull-down</dfn>: sets the speed correction to match one
actual second, e.g. a 4.1667 pull-up matches a 24fps cinema movie to a
25 fps PAL TV broadcast format.
</li>
<dfn>Ext Timecode Offsets</dfn>
<ul>
<li>
- <dfn>Slave Timecode offset:</dfn> when an external timecode source is used,
+ <dfn>Slave Timecode offset</dfn>: when an external timecode source is used,
adds or substracts the specified offset to the received timecode (MTC or LTC).
</li>
<li>
- <dfn>Timecode Generator offset:</dfn> adds the specified offset to
+ <dfn>Timecode Generator offset</dfn>: adds the specified offset to
the timecode generated by Ardour (so far only LTC) before sending it to
the external synchronized system.
</li>
<ul>
<li>
<dfn>Ardour is JACK Time Master (provides Bar|Beat|Tick and other information
- to JACK)</dfn> Aside from synchronizing any JACK slave, Ardour can also
+ to JACK)</dfn>: aside from synchronizing any JACK slave, Ardour can also
provide musical time information (Bar/Beat/Tick) for the current absolute
position for all the JACK-aware clients (N.B. the first jack client that
asks for this wins).
<ul>
<li>
<dfn>Use Video File's FPS Instead of Timecode Value for Timeline and Video
- Monitor</dfn> when checked, uses the timecode FPS value of the standard
+ Monitor</dfn>: when checked, uses the timecode FPS value of the standard
used by the video file instead of forcing the FPS set in the <a href="#properties-timecode">
Timecode tab</a>.
</li>
<li>
<dfn>Apply Pull-Up/Down to Video Timeline and Video Monitor (Unless using
- JACK-sync)</dfn> allows to apply the pull-up/down as set in the <a href="#properties-timecode">
+ JACK-sync)</dfn>
: allows to apply the pull-up/down as set in the <a href="#properties-timecode">
Timecode tab</a> to the <a href="@@video-timeline-and-monitoring">video
timeline</a> as displayed in the editor and to the Video Monitor, resulting
in a shorter/longer video in the editor and a speed-up/down in the Video
<dfn>Audio Fades</dfn>
<ul>
<li>
- <dfn>Destructive crossfade length:</dfn> sets the duration of the crossfade
- Ardour automatically creates when an operation on a region is destructive,
- such as when recording in a track in tape mode.<br>
- This does not change the length of the crossfade Ardour automatically creates
- at regions boundaries on non-destructive operations (recording, slicing etc...)
- which is set to 1 ms.
- </li>
- <li>
- <dfn>Declick when transport starts and stops</dfn> creates an artificial
+ <dfn>Declick when transport starts and stops</dfn>: creates an artificial
fade in/out when starting or stopping playback, to avoid the 'click' sound
resulting in starting it at a non zero value.
</li>
<li>
- <dfn>Declick when monitor state changes</dfn> also creates an artificial
+ <dfn>Declick when monitor state changes</dfn>: also creates an artificial
fade in/out to avoid clicks when a parameter in the monitor changes.
</li>
<li>
- <dfn>Region fades active</dfn> when checked, Ardour applies the region
+ <dfn>Region fades active</dfn>: when checked, Ardour applies the region
<a href="@@create-region-fades-and-crossfades">crossfades</a> to each
region's start and end. When unchecked, no fades are applied, and clicks
may be heard at regions boundaries.
</li>
<li>
- <dfn>Region fades visible</dfn> when checked, the region fades are visible
+ <dfn>Region fades visible</dfn>: when checked, the region fades are visible
in the the Editor. Unchecking may increase readability for sessions made
of a lot of tiny regions.
</li>
<dfn>Audio File Format</dfn>
<ul>
<li>
- <dfn>Sample format:</dfn> defaults to 32-bit floating point, the same as
+ <dfn>Sample format</dfn>: defaults to 32-bit floating point, the same as
the internal representation. 24 and 16-bit integer representation are
also available, for more lightweight sessions at the cost of a reduced
audio definition.
</li>
<li>
- <dfn>File type:</dfn> defines what format is used to store the audio
+ <dfn>File type</dfn>: defines what format is used to store the audio
files. The default is WAVE, and can be changed to Broadcast Wave to
store metadata and timecodes, <abbr title="Core Audio
Format">CAF</abbr> to overcome WAVE's limitation to 4Gb in size, RF64
<dfn>File Locations</dfn>
<ul>
<li>
- <dfn>Search for audio files in:</dfn> allows to add a location to look
+ <dfn>Search for audio files in</dfn>: allows to add a location to look
for audio files. Adding a location is done by navigating to the
directory where the files are stored, selecting it and clicking <kbd
class="menu">Open</kbd>. The directory will show up in the dialog. The
this way.
</li>
<li>
- <dfn>Search for MIDI files in:</dfn> is exactly the same, but for MIDI files.
+ <dfn>Search for MIDI files in</dfn>: is exactly the same, but for MIDI files.
</li>
</ul>
</li>
<dfn>File Naming</dfn>
<ul>
<li>
- <dfn>Prefix Track number</dfn> when checked, a unique number will
+ <dfn>Prefix Track number</dfn>: when checked, a unique number will
appear on each track in the Editor window and will prefix the region
name. If the track number is <samp>2</samp> and the region would have
been named <samp>Gtr-1.1</samp>, with track number prefix turned on the
href="@@region-naming">Region Naming</a>.
</li>
<li>
- <dfn>Prefix Take Name</dfn> when enabled, the first time a track is
+ <dfn>Prefix Take Name</dfn>: when enabled, the first time a track is
recorded it will have the specified take name. When recording is
stopped, any trailing number on the end of the take name will be
incremented by 1. If the specified track name doesn't have a number on
<ul>
<li>
<dfn>Track Input Monitoring automatically follows transport state
- ("auto-input")</dfn> affects how input monitoring is handling. See <a
+ ("auto-input")</dfn>
: affects how input monitoring is handling. See <a
href="@@monitor-setup-in-ardour">Monitor Setup in Ardour</a>
</li>
<li>
- <dfn>Use monitor section in this session</dfn> when enabled, displays
+ <dfn>Use monitor section in this session</dfn>: when enabled, displays
an extra section in the Mixer window that is modelled on the similarly
named section on large analog consoles. More information can be found
on the <a href="@@monitor-section">Monitor Section</a> page.
<ul>
<li>
- <dfn>Route Display</dfn>
+ <dfn>Display Options</dfn>
<ul>
<li>
- <dfn>Show Midi Tracks</dfn> displays/hides MIDI tracks (even when no
- synth, hence no audio output exists)
+ <dfn>Show Midi Tracks</dfn>: displays/hides MIDI tracks
+ (even when no synth, hence no audio output exists)
</li>
<li>
- <dfn>Show Busses</dfn> displays/hides <a
- href="@@track-types">Busses</a> tracks
+ <dfn>Show Busses</dfn>: displays/hides
+ <a href="@@track-types">Busses</a> tracks
</li>
<li>
- <dfn>Include Master Bus</dfn> displays/hides the <a
- href="@@master-bus-strip">Master Bus</a>
+ <dfn>Include Master Bus</dfn>: displays/hides the
+ <a href="@@master-bus-strip">Master Bus</a>
</li>
</ul>
</li>
<dfn>Button Area</dfn>
<ul>
<li>
- <dfn>Rec-enable Button</dfn> displays/hides the record arm button (for audio
+ <dfn>Rec-enable Button</dfn>: displays/hides the record arm button (for audio
and MIDI tracks only)
</li>
<li>
- <dfn>Mute Button</dfn> displays/hides the mute button (for all
+ <dfn>Mute Button</dfn>: displays/hides the mute button (for all
tracks/busses types)
</li>
<li>
- <dfn>Solo Button</dfn> same for solo
+ <dfn>Solo Button</dfn>: same for solo
</li>
<li>
- <dfn>Monitor Buttons</dfn> displays/hides the two (input and playback)<a
+ <dfn>Monitor Buttons</dfn>
: displays/hides the two (input and playback)<a
href="@@monitoring">monitoring</a> buttons, selecting what is played at
record and playback time.
</li>
<dfn>Name Labels</dfn>
<ul>
<li>
- <dfn>Track Name</dfn> adds the tracks' names bellow the buttons.
+ <dfn>Track Name</dfn>: adds the tracks' names below the buttons.
</li>
</ul>
</li>
<dfn>MIDI Options</dfn>
<ul>
<li>
- <dfn>MIDI region copies are independent</dfn> if selected, when a MIDI
+ <dfn>MIDI region copies are independent</dfn>: if selected, when a MIDI
region is copied or duplicated, the new region is not linked to the
region it was copied from. If it is not selected, the copied regions
are linked and any editing done on one of the linked regions changes
<dfn>Glue to Bars and Beats</dfn>
<ul>
<li>
- <dfn>Glue new markers to bars and beats</dfn> if checked, a newly
+ <dfn>Glue new markers to bars and beats</dfn>: if checked, a newly
created marker will always be placed at the nearest musical time
instead of right where the mouse pointer is.
</li>
<li>
- <dfn>Glue new regions to bars and beats</dfn> same as above, for regions.
+ <dfn>Glue new regions to bars and beats</dfn>: same as above, for regions.
</li>
</ul>
</li>
<dfn>Metronome</dfn>
<ul>
<li>
- <dfn>Always count-in when recording</dfn> when checked, waits for two
+ <dfn>Always count-in when recording</dfn>: when checked, waits for two
bars before the actual recording begins. The Metronome will tick (even if
disabled) during the count-in. Same as recording with <kbd
class="menu">Transport > Record w/Count-In</kbd>.
projects / ardour-manual / commitdiff