The Harmonizer
®
Programmer’s Manual
©
1999-2008 Eventide, Inc.
Page 11 of 97
Release 1.3
The Characteristics of Modules
There are several characteristics associated with any module. All modules have:
•
a module type
•
a module name
Modules use memory and processing resources that can be divided into the following groups:
•
audio memory
•
signal processing
•
user interface and control signal memory
•
control processing
Different types of modules use different amounts of these resources.
More complex modules have some or all of these items:
•
specifier
s
•
audio inputs (and/or mod inputs)
•
audio outputs (and/or mod outputs)
•
control inputs
•
control outputs
•
userobject
outputs
•
userobject
inputs
The following sections will discuss all of these attributes in depth. . .
M
ODULE
T
YPE
There are many kinds of modules at our disposal. The “module type” simply defines a module as being
a particular
kind
of module. When a module is added to a program, it is selected by module type. Once
added, the module type cannot be changed. If a different module type is needed, the “offending”
module must be deleted and then the correct module type must be added anew.
The
modules
are ordered by module type. When a module is mentioned in this document, it is referred
to by module type. For example, a module whose module type is “
samphold
” would be referred to as
a
samphold
module. The best place to find detailed information on each module is the Vsigfile Help
System (
Modules Section
), which is updated regularly.
M
ODULE
N
AME
The module name is a text string that is stored with a particular module. It is
helpful to change the module name immediately after adding a module so that
modules of the same type can be told apart. Choose a name that reflects both the
purpose of the module within the patch, and the module type. The name may be
up to 18 characters in length. To the right we see
gate
type module named
“Ch1 Hiss Gate."