2013-01-29 19:26:36 -05:00
---
2017-01-13 05:32:49 -05:00
title: Times
---
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< dfn > Clocks< / dfn > in Ardour are used to display < dfn > time values< / dfn > precisely.
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
In many cases, they are also one way to edit (change) time values, and in a few
2017-01-13 05:32:49 -05:00
cases, the only way. All clocks share the same basic appearance and functionality,
2014-02-04 14:06:25 -05:00
which is described below, but a few clocks serve particularly important roles.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< h2 > Transport Clocks< / h2 >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
In the transport bar of the editor window there are two clocks (unless you
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
are on a very small screen), that display the current position of the playhead
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
and additional information related to transport control and the timeline. These
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
are called the < dfn > transport clocks< / dfn > ; the left one is the primary
2017-01-13 05:32:49 -05:00
transport clock and the right one is the secondary transport clock.
2014-02-04 14:06:25 -05:00
They look like this:
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2017-01-13 05:32:49 -05:00
2017-01-17 03:46:03 -05:00
< img src = "/images/new_main_clocks.png" alt = "An image of the transport clocks in Ardour" / >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
Editing the time in the transport clocks will reposition the playhead in the same
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
way that various other editing operations will.
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< / p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< h3 > The Big Clock< / h3 >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
To show the current playhead position in a big, resizable window, activate
2017-01-13 05:32:49 -05:00
< kbd class = "menu" > Window > Big Clock< / kbd > . The big clock is very useful
2014-02-04 14:06:25 -05:00
when you need to work away from the screen but still want to see the playhead
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
position clearly (such as when working with a remote control device across
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
a room). The big clock will change its visual appearance to indicate when active
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
recording is taking place. Below on the left is a screenshot showing a fairly
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
large big clock window filling a good part of the display, and on the right,
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
the same clock during active recording.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2017-01-13 05:32:49 -05:00
2017-01-03 08:05:11 -05:00
< 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"
2017-01-13 05:32:49 -05:00
2014-02-02 18:09:23 -05:00
/>< / a >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< h3 > The Special Role of the Secondary Transport Clock< / h3 >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
On a few occasions Ardour needs to display time values to the user, but there
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
is no obvious way to specify what units to use. The most common case is the big
2017-01-13 05:32:49 -05:00
cursor that appears when dragging regions. For this and other similar cases,
2014-02-04 14:06:25 -05:00
Ardour will display time using the same units as the secondary clock.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< h4 > Why are there two transport clocks?< / h4 >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
Having two transport clocks lets you see the playhead position in two different
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
time units without having to change any settings. For example, you can see the
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
playhead position in both timecode units and BBT time.
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< / p >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< h3 > Selection and Punch Clocks< / h3 >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
The transport bar also contains a set of 5 clocks that show the current
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< dfn > selection range< / dfn > and < dfn > punch ranges< / dfn > . Clicking on the punch
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
range clocks will locate to either the beginning or end of the punch range.
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
Similarly, clicking on the range clocks will locate to either the beginning
2017-01-13 05:32:49 -05:00
or end of the current selection. In this screen shot there is no current
2014-02-04 14:06:25 -05:00
selection range, so the selection clocks show an "off" state.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2017-01-03 08:05:11 -05:00
< img src = "/images/selectionpunchclocks.png" alt = "An image of the the selection and punch clocks in Ardour 3" / >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< h2 > Clock Modes< / h2 >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
Every clock in Ardour has four different, selectable < dfn > clock
2017-01-13 05:32:49 -05:00
modes< / dfn > . Each mode displays time using different units.
You can change the clock mode by < kbd class = "mouse" > Right< / kbd > -clicking
2014-02-04 14:06:25 -05:00
on the clock and selecting the desired mode from the menu. Some clocks are
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
entirely independent of any other clock's mode; others are linked so that
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
changing one changes all clocks in that group. The different modes are:
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< / p >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< dl >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< dt > Timecode< / dt >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< dd > Time is shown as < dfn > < abbr title = "Society of Motion Picture and Television
2017-01-13 05:32:49 -05:00
Engineers">SMPTE< / abbr > timecode< / dfn > in Hours:Minutes:Seconds:Frames,
measured from the timecode zero point on the timeline (which may not
2014-02-04 14:06:25 -05:00
correspond to the session start and/or absolute zero on the timeline,
2017-01-13 05:32:49 -05:00
depending on configurable timecode offsets).
2014-02-04 14:06:25 -05:00
The frames value is dictated by either the session < abbr title = "Frames Per
2017-01-13 05:32:49 -05:00
Second">FPS< / abbr > setting, or, if slaved to an external timecode master,
the master's setting. In the transport clocks, the FPS value is shown below
2014-02-04 14:06:25 -05:00
the time display, along with an indication of the current timecode source
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
(< samp > INT< / samp > means that Ardour is its own timecode source).< / dd >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< dt > BBT< / dt >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< dd > Time is shown as Bars:Beats:Ticks, indicating < dfn > musical time< / dfn > measured
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
from the start of the session. The transport clocks show the current tempo
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
in < abbr title = "Beats Per Minute" > bpm< / abbr > and meter below the time
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
display.< / dd >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< dt > Minutes:Seconds< / dt >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< dd > Time is shown as Hours:Minutes:Seconds.Milliseconds, measured from the
2017-01-13 05:32:49 -05:00
absolute start of the timeline (ignoring the session start and any timecode
2014-02-04 14:06:25 -05:00
offsets).< / dd >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< dt > Samples< / dt >
2017-01-13 05:32:49 -05:00
< dd > Time is shown as a < dfn > sample count< / dfn > from the absolute start of the timeline
2014-02-04 14:06:25 -05:00
(ignoring the session start and any timecode offsets). The number of
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
samples per second is given by the current sample rate, and in the transport
2017-01-13 05:32:49 -05:00
clocks, this rate is shown below the time display along with any
2014-02-04 14:06:25 -05:00
pullup/pulldown adjustment.< / dd >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / dl >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< h3 > Special Modes for the Transport Clocks< / h3 >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
In addition to the time-unit modes mentioned above, each of the two transport
2014-02-04 14:06:25 -05:00
clocks (if you work on a small screen, you may only have one) can be
2017-01-13 05:32:49 -05:00
independently set to display < dfn > Delta to Edit Point< / dfn > in whatever time
2014-02-04 14:06:25 -05:00
units its current mode indicates. This setting means that the clock shows the
2017-01-13 05:32:49 -05:00
distance between the playhead and the current edit point, and it may show a
positive or negative value depending on the temporal order of these two points.
2014-02-04 14:06:25 -05:00
The clocks will use a different color when in this mode to avoid confusion.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
To switch either (or both!) of the transport clocks into this mode, use
2014-02-04 14:06:25 -05:00
< kbd class = "menu" > Edit > Preferences > Transport< / kbd > and select
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
the relevant checkboxes.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
Note that when in < samp > Delta to Edit Point< / samp > mode, the transport clocks
2014-02-04 14:06:25 -05:00
cannot be edited.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< h2 > Changing clock values with the keyboard< / h2 >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
New values for the clock can be typed in after clicking on the relevant clock.
Clicking on the clock will show a thin vertical cursor bar just to the right
of the next character to be overwritten. Enter time in the same order as the
current clock mode— if the clock is in Timecode mode, you need to enter
hours, minutes, seconds, frames. So, to change to a time of 12:15:20:15 you
would type < kbd class = "input" > 1 2 1 5 2 0 1 5< / kbd > . Each number you type will
appear in a different color, from right to left, overwriting the existing value.
2014-02-04 14:06:25 -05:00
Mid-edit, after typing < kbd class = "input" > 3 2 2 2< / kbd > the clock might look like this:
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2017-01-13 05:32:49 -05:00
2017-01-03 08:05:11 -05:00
< img src = "/images/clockedit.png" alt = "An image of a clock being edited in Ardour 3" / >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
< p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
To finish the edit, press < kbd > ↵ < / kbd > or < kbd > Tab< / kbd > . To exit an
2017-01-13 05:32:49 -05:00
edit without changing the clock press < kbd > ESC< / kbd > . If you mis-type an entry
so that the new value would be illegal (for example, resulting in more than 30
frames when Timecode is set to 30 frames per second), the clock will reset at
2014-02-04 14:06:25 -05:00
the end of the edit, and move the cursor back to the start so that you can
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
start over.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< h3 > Avoiding the mouse entirely< / h3 >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
There is a shortcut available for those who wish to be able to edit the transport
clocks entirely without the mouse. It can be found in
2014-02-04 14:06:25 -05:00
< kbd class = "menu" > Window > Key Bindings > Transport > Focus On
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
Clock< / kbd > . If bound to a key (< kbd > ÷ < / kbd > on the numerical
2017-01-13 05:32:49 -05:00
keypad is the
default), then pressing that key is equivalent to clicking on the primary (left)
2014-02-04 14:06:25 -05:00
transport clock, and editing can begin immediately.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< h3 > Entering Partial Times< / h3 >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
One detail of the editing design that is not immediately obvious is that it is
2014-02-04 14:06:25 -05:00
possible to enter part of a full time value. Suppose that the clock is in BBT
2017-01-13 05:32:49 -05:00
mode, displaying < samp > 024|03|0029< / samp > , and you want to alter the value to
the first beat of the current bar. Click on the clock and type
< kbd class = "input" > 0 1 0 0 0 0< / kbd > . Similarly, if it is in Minutes:Seconds
mode, displaying < samp > 02:03:04.456< / samp > , and you want to get to exactly 2
hours, click on the clock and type < kbd class = "input" > 0 0 0 0 0 0 0< / kbd > to
2014-02-04 14:06:25 -05:00
reset the minutes, seconds and milliseconds fields.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< h3 > Entering Delta Times< / h3 >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
You can also type values into the clock that are intended as a relative change,
rather than a new absolute value. Simply end the edit by pressing
2014-02-04 14:06:25 -05:00
< kbd > +< / kbd > or < kbd > -< / kbd > (the ones on any keypad will also work). The plus
2017-01-13 05:32:49 -05:00
key will add the entered value to the current value of the clock, minus will
subtract it. For example, if the clock is in Samples mode and displays
< samp > 2917839< / samp > , you move it back 2000 samples by typing
2014-02-04 14:06:25 -05:00
< kbd class = "input" > 2 0 0 0< / kbd > and < kbd > -< / kbd > , rather than ending with
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
Enter or Tab. < / p >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< h2 > Changing clock values with the mouse< / h2 >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< h3 > Using a scroll wheel< / h3 >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
Position the mouse pointer over the clock, and move the scroll wheel. Moving
2017-01-13 05:32:49 -05:00
the scroll wheel up (< kbd class = "mouse" > ⇑ < / kbd > ) increases the value
2014-02-04 14:06:25 -05:00
shown on the clock, moving it down (< kbd class = "mouse" > ⇑ < / kbd > )
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
decreases it. The step size is equal to the unit of the field
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
you are hovering over (seconds, hours, etc.).
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >
2014-02-04 14:06:25 -05:00
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< h3 > Dragging the mouse< / h3 >
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< p >
2017-01-13 05:32:49 -05:00
Position the mouse pointer over the clock, press the left mouse button and drag.
2014-02-04 14:06:25 -05:00
Dragging upwards increases the value shown on the clock, dragging downwards
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
decreases it, again with a step size equal to the unit of the field you
2017-01-13 05:32:49 -05:00
2014-02-04 14:06:25 -05:00
began the drag on.
2017-01-13 05:32:49 -05:00
2013-01-29 19:26:36 -05:00
< / p >