page A – 6
E-6 / July 2011
A P P E N D I C E S
A Simple Example From The File
As a simple example let’s look at the MUTE_METHOD option. Scroll through
the Options Text File (or look at the sample file listing at the end of this Appendix)
until you see the following three lines of code:
// Syntax: MUTE_METHOD:?
// ? 0 (default) = ON button, 1 = ON AIR.
MUTE_METHOD:0
The first line describes the syntax for this option. It starts with two
slashes, which are interpreted as the start of a comment line. Comment lines
are made for us to read, and the surface CPU ignores them. This line shows
that the syntax for the option is the keyword MUTE_METHOD followed by
a colon (:) followed by some character, as represented by the ‘?’ character.
The next line indicates that the ‘?’ can be replaced by a ‘0’ (a zero, not the
letter O) if a muting channel being ON will trigger the mute, or a ‘1’ if the
muting channel must be both ON and assigned to a main bus (thus making it
ON AIR) before it will trigger the mute. This specific example shows that the
default setting is ‘0’ for this option. Please note that this may or may not be
the case for your particular surface, as the default option is subject to change.
The idea
of how to use the file remains true.
The third line is not a comment; this is the line the surface CPU actually reads
from the file. This line, as shown, sets the muting method to ON (channel must be
ON to activate a mute, but need not be ON AIR). If this is not the desired opera-
tion, this line must be edited. Change the ‘0’ to a ‘1’ and the muting method will
change so that a channel is required to be ON AIR before it will activate a mute.
As indicated in the instructions above for modifying the file, the actual change
to operation will not happen until the surface has been rebooted and has read the
modified file.
The edited line must follow the established syntax precisely or the surface may
not behave as expected.
