API Audio 1608 Automation - Manual (Page 39)

5.0 Automation Concepts
To operate the automation system and make full use of its features, the engineer must first understand
some basic automation concepts and how the system components interact with one another. This
section will explore these concepts and how to prepare the system for use. It is important for new users
to read this entire section.
NOTE: This and subsequent manual sections assume that the automation package and console have
been properly set up and interfaced. For automation package setup, refer to section 16.0
System Configuration, Calibration, and Firmware.
5.1 Mix Pass and Mix Tree Concepts
The Automation Controller provides a suite of automation controls and a display. The 948B Fader
Modules and 548B Input Modules provide additional automation controls. Used as a system, the
console hardware and software components allow the creation and modification of an automated
mix.
The 940B Automation Controller (ACM) provides enough memory for one “mix pass” (also called
“mix file” or just “mix”). Only one “mix” can be stored in the volatile memory at a time. This mix
is known as the “current mix.”
The mix pass in memory can be modified at any time using hardware or software interfaces.
When changes are made, the altered mix pass becomes the current mix and is automatically
saved to the Mix Tree. The Mix Menu provides an additional suite of tools for editing and working
with mixes and mix data.
Performing additional moves and/or edits to an existing mix will add a new mix to the Mix Tree
without deleting the original. Because of this method, the manipulation of mixes can be
performed in a nondestructive manner and numerous levels of “undo” are provided among the
mix passes stored in the Mix Tree.
A project file must be open to work with the mix in memory and the mixes in the Mix Tree. The
project file (and therefore the Mix Tree) is stored to the memory card and is considered to be
non-volatile.
5.1.1 Mix Passes
A “mix pass” or “mix” is simply a file containing time-stamped fader, mute, and insert
changes throughout the entire length of the recording. Whenever timecode is played back
and changes are made, a new mix pass is created. When playback is stopped, the new
moves are processed, the new pass becomes the “current mix,” and the mix is added to the
Mix Tree.
The ACM can hold only one active pass at a time in its operational memory. This mix is
known as the “current” mix and it is the one that will be played back in READ mode. Any
recorded changes will be added to the data in the current mix and a new mix pass will be
generated. The resulting mix will become the new current mix.
Whenever a new mix pass is generated, it is added to the Mix Tree. A new “mix file” is also
created and added to the project folder for the current project as a .VMX file.
Any mix pass in the Mix Tree can be “made current” at any time.
Mix files can be exported for use in other projects. Accordingly, mixes can be imported into
the Mix Tree in an open project, adding it to the project folder as a .VMX file.
As an aside, group assignments are stored in mix passes. This means that when an existing
mix is loaded from the Mix Tree, all of the groups are exactly as they were when the mix
was saved. If you change to a different mix, those groups are restored. If groups were
created in later mixes, they will not be included in earlier mixes.