Revision C • 10/07
HARRIS CORPORATION
A-7
Appendix A VMCC
sole is not affected. However, all of the static sec-
tions that were loaded when the previous session
or macro file was taken are erased, which includes
the following session file sections:
[Mapping],
[fader_start],[fix_fader],
[fix_pan],[local_cough],
[Timer_Reset],[routercommand_1].
After the database is cleared, the new session or
macro file sections and entries are loaded into the
database and the commands are executed. For a
macro file, the commands are simply run without
regard to whether or not they match the console
or cardframe hardware, the console config, etc. For
session files, the [Mapping] section is used to
verify each command matches the console’s hard-
ware configuration before the command is ex-
ecuted to prevent incorrect routing, etc.
Pressing the console’s
Save Session
button, or
using the Save_Ses FTP literal command, causes
the SBC to first take a “snapshot” of the current
channel settings from the control panels/hardware,
writing (or overwriting) those values (all of the
button sections and current routed sources for each
channel and the [Mapping] section data) into
the database. Thus, at the end of this process, but
before the database is written to the new session
file, the database holds the current status of the
console’s buttons (bus, mode, PS, PF, Pan/Bal as-
signments, etc.) PLUS whatever previous static
command sections were last loaded (e.g.,
[fader_start],[local_cough],[fix_fader],
[Timer_Reset],[fix_pan],[routercommand_1],).
The new .ses file is then written.
Control File Formatting
VistaMax setup and configuration files are text-
only files that share these common formatting
rules: all command text is held within sections;
each section begins with a
[Section Name]
header can be up to 32 characters); each Key Value
uses a separate line within the section with a cor-
responding Entry Value (there is a 1,000 charac-
ter limit, which may be further limited by con-
straints imposed by a particular section); any text
proceeded by a semicolon (;) is a comment line
which can have up to 80 characters.
Config (.cfg) and setup (.ini) files are cre-
ated and maintained through VMCC, so the fol-
lowing information is most applicable to session
and macro files which are edited using Notepad.
Here’s how a typical section and its entries ap-
pear in VistaMax files:
[Section Name]
;Section Comment Line
KeyValue=EntryValue ;Comment
The [Section Name] defines what the sec-
tion entry values set up. The name is specific and
must be entered using exact characters. Following
each [Section Name] heading is space avail-
able for one or more comment lines. Up to 32 com-
ment lines can be added, as long as each com-
ment begins with a semicolon (;).
Each section can have up to 64 entry lines. Each
entry line is composed of a Key Value followed by
= (equal sign) and an Entry Value. The Key Value
may be up to 32 characters in length. The
EntryValue may be up to 80 characters in length,
plus each entry can be followed by an optional
comment—which can also be up to 80 characters
in length (after a ;).
The format of the Entry Value is also Section
Name specific, and it may have multiple compo-
nents, each separated by a comma.
When an Entry Value refers to a specific signal
in the VistaMax system it can be identified in three
ways: by its unique global number (
e.g., 65697
);
by its local number (
e.g., 161
), which is the same
number on all devices of the same type; or, when
the signal is referring to a signal on another de-
vice, by using its universal number (
e.g., d1.161
),
To Next Page
Loading...
