+ When the contents of one trigger slots has been played a user-defined number of times, Ardour can stop playing trigger slots or switch to a different trigger slot. This is defined by follow actions, i.e. actions follow the playback of a trigger slot.
+ ++ Here are the currently available follow actions: +
+ +FIXME THE ENTIRE TABLE
+ +| None | +Play the contents of the slot once and stop |
|---|---|
| Stop | +Stop after playing back the amount of times set with Follow Count or via Follow Length (see below) |
| Again | +Repeat the contents of the trigger slot over and over again |
| Reverse | +Play back and go to the previous trigger slot |
| Forward | +Play back and go to the next trigger slot |
| Jump | +Play back and jump to a particular scene. Selecting multi-jump and multiple trigger slots will result in randomly playing one of the selected slots. |
To help distinguishing between them, Ardour will display an icon next to the name of a clip in a slot:
+ +
+ Ardour can help you explore ideas by bringing an element of randomness. You can set two possible follow actions to randonly alternate between, then set the percentage of probability of the left or the right follow action to be triggered. 0% means the left follow action is always chosen, 100% means the right follow action is always chosen. Anything between 0% and 50% will skew the probability towards the left follow action, anything between 50% and 100% will do the same for the right follow action.
+ +Follow Count
+ +How many times to repeat a clip before triggering the Follow Action. FIXME
+ +Follow Length: [] beats
+ +When enabled, follow length is used instead of clip length. FIXME
+ diff --git a/include/clip-launch-options.html b/include/clip-launch-options.html new file mode 100644 index 00000000..b1ea3db7 --- /dev/null +++ b/include/clip-launch-options.html @@ -0,0 +1,51 @@ ++ This control defines how much the velocity coming off your MIDI device + affects clip's volume. At 0%, which is the default, it doesn't matter how + hard you press a key or a pad, the volume will be what you set it to. + At 100%, hitting a key as hard as you can produces maximum volume, and + pressing the key or a pad really softly produces a barely audible sound. +
+ +FIXME THE ENTIRE TABLE
+ +| Trigger | +You click and it starts playing until it stops; mouse up and note-off are ignored |
|---|---|
| Retrigger | +Mouse down or note-on starts or retriggers; mouse up and note-off FIXME |
| Gate | +plays only as long as you press the play button, quantization setting defines how soon it starts and ends after pressing the button down. Runs till mouse up/note off then to next quantization |
| Toggle | +Keeps looping until you click it again. runs till next mouse down/NoteOn |
| Repeat | +Keeps looping, but when you press and hold, it starts from the beginning and plays as far as quantization setting goes, e.g. 1/16 means it repeats the first 1/16 of a bar. plays only quantization extent until mouse up/note off |
+ From 4 bars down to 1/64 bar, and None. FIXME
+ +FIXME (also, doesn't work properly yet).
+ +FIXME, If selected, the slot will not respond to start/stop cue events (does it work?)
+ ++ FIXME. These options are where you define the transition from one slot to another. +
diff --git a/include/clip-stretch-options.html b/include/clip-stretch-options.html new file mode 100644 index 00000000..04753b95 --- /dev/null +++ b/include/clip-stretch-options.html @@ -0,0 +1,39 @@ +FIXME. Optional. What happens when disabled? Won’t match the current timeline +tempo: START THE SECTION WITH THIS: ARDOUR ALWAYS MATCHES CURRENT SESSION +TEMPO, SO TEMPO RAMPS WILL WORK FOR CLIPS
+ +Stretch modes:
+ +It’s a hint to help you counting. FIXME
+ +1) when a file is loaded, we infer its bpm either by minibpm's estimate, a flag in the filename, metadata (TBD) or other means
+ +2) we assume the clip must have an integer number of beats in it (simplest case is a one-bar loop with 4 beats in it)
+ +3) ...so we round to the nearest beat length, and set the tempo to *exactly* fit the sample-length into the assumed beat-length
+ +4) the user may recognize a problem: "this was a 3/4 beat, which was rounded to 4 beats but it should have been 3"
+ +5) if the user changes the beat-length, then the tempo is recalculated for use during stretching
+ +6) someday, we will also allow the sample start and length to be adjusted in a trimmer, and that will also adjust the tempo
+ +7) in all cases the user should be in final control; but our "internal" value for stretching are just sample-start and BPM, end of story
\ No newline at end of file diff --git a/include/cue-window-elements.html b/include/cue-window-elements.html new file mode 100644 index 00000000..13b66945 --- /dev/null +++ b/include/cue-window-elements.html @@ -0,0 +1,78 @@ ++ For cues, Ardour generally follows the design pattern of other applications + that support a grid-based non-linear workflow. Here are themain elements + of the Cue window. +
+ + + +Grid: tracks and cues. FIXME
+ +Slot: launch indicator, title, follow action indicator. FIXME + +
FIXME
+ ++ Similarly to the ordinary track, this is where you assign a virtual + instrument to a MIDI track and/or add effects to be applied to all clips + in a track regardless of what scene they belong to. +
+ ++ Again, similarly to ordinary tracks, this is where you tweak the fader + and panner positions, mute or solo an entire track. +
+ ++ Ardour defaults to displaying the Clips tab as the clips browser + is commonly used for pulling reusable clips into the project. +
+ ++ You can also access the list of tracks, which in the context of the Cue + window is mostly useful to mark a track as visible or not visible in the + Cue window. +
+ ++ Additionally, you can pick a source or a region in the Sources + or Regions tabs respectively and drop them in the Clips + tab to copy a reusable item to your custom library of clips. +
+ ++ The bottom bar contains three or four groups of controls depending on the + type of a clip, audio or MIDI. +
+ ++ You can combine the linear workflow, i.e. working with regions on the + timeline, and the non-linear workflow, i.e. launching clips from trigger + slots and setting up follow actions. +
+ +FIXME GENERAL ORDER OF ACTION:
+ ++ The Cue window allows working with music ideas in a non-linear fashion. + Instead of navigating the timeline and placing regions of audio and MIDI + data at a particular point in time, you deal with short clips that contain + rhythmic and melodic patterns and can be triggered to play a certain amount + of times, then automatically trigger another clip to be played. +
+ ++ The concept has been introduced and popularized by Ableton and since then + found its way into many other applications. Ardour draws many ideas from + Ableton Live, as well as from several other digital audio workstations, + and adapts them to Ardour's specifics. If you are familiar with Live, you + will find many aspects familiar, but you should not expect the Cue's feature + set to be a 100% copy of that from any other application. +
+ ++ Here are some basics concepts of the non-linear workflow shared by multiple + applications including Ardour. +
+ ++ All clips are organized in a kind of a grid. The grid provides an overview + of all the musical ideas, all the rhythmic patterns, short melodies, and sound + effects that you can use in a composition. +
++ One dimension of the grid, usually represented by a track, would accumulate + clips played with roughly the same kind of an instrument, e.g. all drum + patterns, or all basslines etc. +
++ The other dimension, usually called scenes (or cues, in Ardour) would + organize these clips so that you would be able to play multiple clips at + the same time by pressing just one button. So if you want a particular + bassline played along a particular drum sequence, you would place them in + the same scene. +
+ ++ Ardour specifics are explained in the + Cue window elements chapter. +
+ ++ Cells in a grid are usually called slots. They are a kind of a container + that can hold an audio or a MIDI clip. Typically, a clip can be loaded + into a slot from a disk by pointing the file selector to it, or loaded + from a pre-recorded library of reusable clips, or recorded in place. + You will find more information about that in the + Populating the cue grid chapter. +
+ ++ In a non-linear workflow, a clip can be triggered to play in multiple ways. + Most of the time it's either pressing a corresponding silicon pad on an + external grid controller attached via MIDI, or scrolling the mouse wheel + downwards over the slot that contains the clip, or just clicking a 'Play' + button next to clip's name. +
+ ++ Usually you can configure a slot to respond to some ways to trigger clip + playback and ignore others. We'll talk about it in the + Clip Launch Options chapter. +
+ ++ A clip can play in a loop until you stop it directly, or it can play + a user-defined amoutn of time and the trigger another clip in the track. + Say, you start a composition with one rhythmic pattern played four times + and you want the next rhythmic patterns to play eight times, then move + to a third one. +
+ ++ This is typically achieved through so called follow actions. In an example + above, for the first clip (or, rather, slot) you can set a follow count + (4 times), and use the follow action usually called "Next". This will get + the clip in that first slot to play 4 times then trigger the playback of + a clip in the second slot. +
+ ++ Every application has its own set of follow actions. Most common ones are + repeating the clip indefinitely, triggering the previous/next slot, + or jumping to a slot in a particular scene. +
+ ++ You can read more about follow actions in Ardour + here. +
+ ++ In a non-linear workflow, all work is happening in musical time: both audio + and MIDI clips are measured in bars and beats. +
+ ++ By default, an application that supports a non-linear workflow will attempt + to estimate beats per minute in an audio clip and then stretch or squeeze + the clip so that it would match the bpm of the session and wrap neatly around + bars. That way, a clip that originally has a different tempo that the one in + the session would stay in sync with other clips. +
+ ++ Stretch options in Ardour are explained + here. +
diff --git a/include/playing-back-the-cues.html b/include/playing-back-the-cues.html new file mode 100644 index 00000000..0574e6ab --- /dev/null +++ b/include/playing-back-the-cues.html @@ -0,0 +1,13 @@ +By clicking play button. FIXME
+ +By scrolling the mouse wheel. FIXME
+ +Stopping the slot playback. FIXME
+ +Launching a cue. FIXME
+ +Stopping a cue. FIXME
\ No newline at end of file diff --git a/include/populating-the-cue-grid.html b/include/populating-the-cue-grid.html new file mode 100644 index 00000000..24bc846c --- /dev/null +++ b/include/populating-the-cue-grid.html @@ -0,0 +1,19 @@ +Via right-click menu. FIXME
+ +Via Clip Properties box. FIXME
+ +From the Clips library. FIXME
+ +By bouncing from the timeline. FIXME
+ +General settings. FIXME
+ +Audio-specific settings. FIXME
+ +MIDI-specific settings. FIXME
\ No newline at end of file diff --git a/include/setting-up-cues.html b/include/setting-up-cues.html new file mode 100644 index 00000000..e69de29b diff --git a/master-doc.txt b/master-doc.txt index 15dd42fe..9263135c 100644 --- a/master-doc.txt +++ b/master-doc.txt @@ -1493,6 +1493,84 @@ include: managing-custom-clips.html part: chapter --- +--- +title: Cue +link: cue +part: part +--- + +--- +title: Non-Linear Workflow Principles +link: non-linear-workflow-principles +include: non-linear-workflow-principles.html +uri: cue/non-linear-workflow-principles +part: chapter +--- + +--- +title: Cue window elements +link: cue-window-elements +include: cue-window-elements.html +uri: cue/cue-window-elements +part: chapter +--- + +--- +title: Setting Up Cues +link: setting-up-cues +include: setting-up-cues.html +uri: cue/setting-up-cues +part: chapter +--- + +--- +title: Populating the Cue Grid +link: populating-the-cue-grid +include: populating-the-cue-grid.html +uri: cue/setting-up-cues/populating-the-cue-grid +part: subchapter +--- + +--- +title: Playing Back the Cues +link: playing-back-the-cues +include: playing-back-the-cues.html +uri: cue/setting-up-cues/playing-back-the-cues +part: subchapter +--- + +--- +title: Setting Up Launch Options +link: clip-launch-options +include: clip-launch-options.html +uri: cue/setting-up-cues/clip-launch-options +part: subchapter +--- + +--- +title: Setting Up Follow Actions +link: clip-follow-actions +include: clip-follow-actions.html +uri: cue/setting-up-cues/clip-follow-actions +part: subchapter +--- + +--- +title: Setting Up Stretch Options +link: clip-stretch-options +include: clip-stretch-options.html +uri: cue/setting-up-cues/clip-stretch-options +part: subchapter +--- + +--- +title: Mixing Linear and Non-Linear Workflows +link: mixing-linear-nonlinear-workflows +include: mixing-linear-nonlinear-workflows.html +uri: cue/mixing-linear-nonlinear-workflows +part: chapter +--- + --- title: Arranging part: part diff --git a/source/images/cue-follow-actions-all-icons.png b/source/images/cue-follow-actions-all-icons.png new file mode 100644 index 00000000..322faab9 Binary files /dev/null and b/source/images/cue-follow-actions-all-icons.png differ diff --git a/source/images/cue-launch-style-all-icons.png b/source/images/cue-launch-style-all-icons.png new file mode 100644 index 00000000..32910a2a Binary files /dev/null and b/source/images/cue-launch-style-all-icons.png differ