SEL-1FS1/SEL-2FS1 and SEL-1XD1/SEL-2XD1
Installation and Operation Manual
Installation, Operation, and Specifications
© 2015 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.8 | Page 116
•
Sum and route the signal to the output channel feeding the SAP, if stereo audio is present (one
PCM)
•
Downmix to 2.0, then sum and route to the output channel feeding the SAP, if surround sound is
present (three PCMs)
•
Decode the audio, downmix to stereo, sum to mono, and then route to the output channel that
feeds the SAP, if Dolby Digital or Dolby E is present (one non-PCM)
Note:
In the above example, as audio channels change, the audio mutes or V-fades must also change, to
prevent clinks or pops from occurring downstream.
Enabling the Parameter Control Script
To enable a parameter control script, set the
Activate Script
parameter to
Enable
. Enter your script into
the
Script (Part I)
parameter (maximum 251 characters). If additional script space is needed, use the
Script (Part II to IV)
parameters.
Script Status [RO]
reports the parsing and active status of the script. If a syntax error is detected when a
new script is entered, this parameter will report
Error: x
message
(
x
is an index number starting from
the beginning of the script to indicate around which character the script parser first encounters a syntax
error).
Writing the Parameter Control Script
Parameter control scripts are made up of one or multiple statements. Each statement consists of one
condition and one or multiple assignments. During device operation, if the condition in a statement
becomes true, the assignment in the statement will take effect.
<script> ::= <statement> { <statement> }
<statement> ::=
IF
<condition>
THEN
<assignment> { <assignment> }
<condition> ::= <comparison> { <logic op> <comparison> }
<comparison> ::=
PARAM[x]
<comparison op> y
Where
x
is the CCSP ID of a device parameter, y is a value for that parameter. The device parameter
could be one of three types: integer, enum, string. Depending on the parameter type,
y
could take
different format:
Integer:
y
is integer value of the parameter
Enum:
y
is the enum value index inside the enum
String:
y
is in a '
zzzz
' string format, where
z
is a character. Special character '*' can be used as
wild card. '
AA
*' and '
AABB
' will be considered as equal
<comparison op> ::
= == | > | < | >= | <= | !=
For string type of parameter, only
==
and
!=
operators are supported.
<assignment> ::
= PARAM[x] = y
Where
x
is the CCSP ID of a device parameter,
y
is a value for that parameter. For now, we only
support integer and enum type of parameter's assignment, not string type.
