Lake Controller Operation Manual

Table Of Contents
Lake Controller Operation Manual Rev 1.5.8
Module File Types & Lake LoadLibrary™
167
9. Module File Types & Lake LoadLibrary
Lake devices provide two categories of Modules; Contour Modules and Mesa Modules. Contour Modules
are suitable for devices that can perform loudspeaker crossover functionality, and Mesa Modules are
suitable for devices that provide equalization only.
This chapter provides a detailed reference for all Lake Module le types. Default Module les are located in
the Default Modules folder and can be accessed and recalled utilizing the MODULE STORE/RECALL menu.
9.1 Module Types Overview
Within the Contour Module category, there are four distinct types of Module:
1. Classic Crossover Modules (featuring Bessel, Butterworth, and Linkwitz-Riley crossovers, available with
roll-off ranging from 6 dB/octave to 48 dB/octave).
2. Auxiliary Output Modules (provides EQ only functionality with a single input mix to multiple outputs
when in Contour Mode).
3. Linear Phase Crossover Modules (providing zero phase distortion with steep transition slopes using FIR
lters).
4. FIR Modules (combination of FIR lters, Classic crossovers, and output-specic driver EQ) - only
available on Lake-enabled ampliers by recalling an FIR Module, or via the import of EAW
®
Greybox™
les (.gyx), providing support for EAW Focusing.
The MESA EQ Module category provides a signal Module type of MESA EQ, that it defaulted for use as a
single input to single output, full bandwidth EQ Module and also provides HPF/LPF functionality.
9.2 Supplementary Module Data
Any Module le may contain additional parameters relating to the power output stage, including Amplier
Gain and ISVPL™ limiter. These parameters are used when the le is loaded into a Lake-enabled amplier
and ignored when loaded into another Lake device; these parameters are retained and passed through to
new Module les via the Module/System Store commands.
Additionally, loudspeaker electrical characteristic parameters (termed Fingerprint and used for LoadSmart
verication) are stored and recalled via a supplementary “.mdl” le with the same lename. This Fingerprint
le must be present in the same directory as the Module le; it is stored and recalled for Lake-enabled
ampliers, and ignored for other Lake devices. Fingerprint data may be reconnected with a Module le
simply by renaming or moving the mdl le to ensure it has the same lename and directory location as its
associated Module le. When a Fingerprint is loaded, this can be seen in the LoadSmart tab of the Amplier
Events & Control view.