2 For cues, Ardour generally follows the design pattern of other applications
3 that support a grid-based non-linear workflow.
7 <img style="width:75%;" src="/images/cue-window-elements.png" alt="The Cue window elements">
9 The Cue window elements
13 <p>The main elements of the <dfn>Cue</dfn> window are:</p>
16 <li>Grid of tracks and cues, playback indicators</li>
17 <li>Mixer channel section</li>
18 <li>Clip and trigger slot options</li>
19 <li>Sidebar: Clips, Tracks, Sources, and Regions</li>
25 The trigger slots <dfn>grid</dfn> is comprised of tracks (stacked
26 horizontally) and cues (stacked vertically). Tracks group clips played
27 by roughly the same instrument (or set of instruments, in case of drums
28 and percussion). Cues group clips that will be played simultaneously.
32 Every <dfn>trigger slot</dfn> with a clip inside contains three elements:
33 launch button/indicator, clip title, and follow action selector/indicator.
37 The <dfn>playback indication area</dfn> displays four pieces of data for
42 <li>Clip playback progress</li>
43 <li>Which cue the playing clip belongs to</li>
44 <li>MIDI clip indication</li>
49 <a href="@@playing-back-the-cues">This chapter</a> provides more information
50 on playback in the <dfn>Cue</dfn> window.
53 <h2>Mixer channel section</h2>
56 The mixer channel section is very similar to what's available in the
57 <dfn>Mixer</dfn> window: there's the <a href="@@processor-box">processor
58 box</a>, the same <a href="@@panning">panner</a>, as well as the
59 <a href="@@muting-and-soloing">mute and the solo</a> buttons. Both the fader
60 and the meter are horizontal, there is no choice for a type of meter.
63 <h2>Clip and trigger slot options</h2>
66 The bottom section contains several groups of controls:
70 <li><a href="@@clip-properties">Clip Properties</a>: full name of a clip
71 in the selected trigger slot, loading a different clip, gain control</li>
72 <li><a href="@@clip-launch-options">Launch Options</a>: how the clips' playback is triggered and within what musical time unit it is quantized</li>
73 <li><a href="@@clip-follow-actions">Follow Actions</a>: how many times one
74 clip is played and what other clip's playback is triggered next</li>
75 <li><a href="@@clip-stretch-options">Stretch Options</a> (audio-only):
76 stretching the original audio data to match current session tempo, adjusting
77 assumed original tempo for creative purposes</li>
83 Ardour defaults to displaying the <a href="@@clips-overview">Clips</a> tab
84 as the clips browser is commonly used for pulling reusable clips into
89 In the Cue context, the <dfn>Tracks</dfn> tab is mostly useful for marking
90 a track as visible or not visible in the Cue window.
94 Both the <dfn>Sources</dfn> and the <dfn>Regions</dfn> tabs can work as
95 drag-and-drop sources for:
99 <li>Placing audio and MIDI data to trigger slots</li>
100 <li>Creating new tracks</li>
101 <li>Creating new reusable clips available from the Clips browser</li>