What is the difference between Audio time and Beat time?
Audio time ( or “real” time ) is the length and tempo of a performance as executed and recorded. Whereas “beat” time is a series of arranging data (notes and rests) that can be executed very quickly, or very slowly, and still be considered the same.
In “beat” time, a quarter-note is a quarter note, regardless of tempo. MIDI consists only of arrangement data, and so it is possible to arrange a MIDI sequence and later increase or decrease the tempo. Just like musicians playing from a score, the arrangement’s tempo will increase, but the musical expression and timbre will remain largely unchanged.
When recording audio, the performers are recorded in real-time subject to the players’ own tempo and interpretation of the music. And once recorded, you cannot easily change the tempo of the recording. Once audio is recorded, it requires quite extensive processing and manipulation to change the tempo … and even more so if you don’t want the pitch to change as well ( i.e. the “chipmunk” effect )
The problem is that Mixbus (and other DAWs) are expected to show both MIDI and Audio data on the same timeline. And there’s some ambiguity: one can imagine audio data (such as a single drum hit) that has no inherent tempo, and can be considered arrangement data, and subject to tempo changes in the musical timeline; or one can imagine a MIDI event that is related to the audio timeline and should not move if (for example) the tempo is changed.
Why is this so hard?
Attempting to shorten or lengthen an audio performance, after it is recorded, requires the sound to be digitally manipulated which will incur some loss of quality. Because Mixbus is intended for high-quality editing, mixing, and mastering tasks, we have chosen to give priority to the “audio” timeline. But there are equally valid reasons why a user might be more interested in the “music” time, and so both music and audio-timelines must coexist.
Consider these examples:
- A live performance is recorded, and the musicians have varied widely in tempo and meter. The user would like to develop a “grid” which follows the varying tempo, and allows editing to the “grid”, just as if the performance were recorded strictly to a metronome. Or perhaps the user would like to add MIDI arrangement using a musical score editor, and these notes must somehow be synced to the performance’s tempo.
- A MIDI performance is generated with a fixed tempo. Later, a vocal and instrumental tracks are added to the MIDI arrangement, and these tracks are edited with crossfades to assemble the best-sounding mix. Now the arranger would like to gradually decrease the tempo at the end of the song ( i.e. ritardando ). The MIDI events, being tied to the Music timeline, will stretch farther apart, but will stay in tune. But what will become of the audio regions?
- A session which mixes spoken-word sections with musical sections. During a musical portion (implemented with MIDI), the tempo is increased, so the musical portion finishes faster than it did, when the audio was recorded. Should the audio voiceover move left to accommodate the shorter musical segment?
Mixbus has some mechanisms to accommodate these situations. But it can get quite complicated.
How do you use Audio Time and Beat Time?
Every item on the timeline ( regions, markers, and automation control points ) must be either connected to the “audio” timeline, or the music timeline. If an item is attached to the musical timeline, then any changes to the BBT (bar-beat-tick) timeline will be moved along with the musical timeline. For example, if you increase the tempo then the regions will move to occur earlier.
What are the default settings for each item on the timeline?
By default, audio regions use the audio timeline. Changes to the tempo will not move or stretch audio regions.
By default, MIDI regions use the “beat” or “music” timeline. Changes to the tempo will move midi regions and the notes inside …. UNLESS you are using the Grid Tool. When using the Grid Tool to adjust the grid, nothing moves, including the midi notes inside a region.
Tempo markers are glued to the BBT timeline, by definition. Tempo markers will move to accommodate prior tempo changes. UNLESS you are using the Grid Tool … when using the Grid Tool, then changes to a tempo marker are not propagated to later tempo markers.
Plugin-Automation control points are attached to the audio timeline.
Markers (like Loop, Punch, Arrangement and Cue) can be either Audio or Music Time. This change is made globally during the creation of the session:
Choosing the time domain for your session:
If you choose “Beat” Time, then:
- the new session will show tempo rulers, arrangement rulers, and cue rulers
- any changes to the tempo map will move the rulers to match. This means: if your punch-range starts on bar 8, then it will always start on bar 8, even if you change the tempo and move the position of bar 8.
If you choose “Audio” Time, then;
- the new session will show minutes:seconds rulers, CD markers. It will hide the tempo markers, arrangement ruler, and cue ruler.
- rulers will not move when you change the tempo. If your punch-range starts at 5:00 minutes, then it will start at 5:00 minutes regardless of any changes to the session’s tempo map
…however, you can later change your mind, and change the session’s default timebase, in Session->Properties->Misc
So what is the preferred workflow for managing a project that mixes Audio events, and Beat (MIDI) events?
Generally speaking, Mixbus is optimized to work in one of these 2 ways:
1) Record a live performance on the audio timeline, (optionally) map the tempo, and then record MIDI instruments. You can later tweak the tempo map, and the MIDI events can follow, if desired.
2) Arrange your song in MIDI, and adjust tempos/timeline as needed. Then record audio, and never again move the tempo/BBT-map after you’ve started recording audio.
This is complicated stuff. Investigating other DAW manuals and videos will reveal that there is no easy, high-quality, non-destructive way to solve these issues.
Post your comment on this topic.