User Manual

Example when the controlled device starts earlier than the controlle
r
• If a logical session, as on an Ethernet network, needs to be established, the controller tries to establish the session befor
e
the sequence example above
.
Parameter sync sequence
Immediately after communication starts, the controller does not know anything about the most recent status of the controlled device.
Therefore, the controller must query all parameters that it plans to handle.
This also applies for when preset recall is executed, because the controller does not know how the device has changed
.
Querying the most recent status of the controlled device or when a snapshot recall occurs
Example 1: Query the DCA fader value.
get MTX:mem_512/60000/0/0/0/0/0 0
0
Query the 1ch level of the DCA fader with raw values.
OK get MTX:mem_512/60000/0/0/0/0/0 0 0 -776
0
The 1ch level of the DCA fader is -77.60.
Example 2: Set the DCA fader value.
set MTX:mem_512/60000/0/0/0/0/0 0 0 -776
0
Set the 1ch level of the DCA fader to a raw value of -77.60
.
OK set MTX:mem_512/60000/0/0/0/0/0 0 0 -7760 "-77.60
"
The 1ch level of the DCA fader was set to "-77.60"
.
Executing this sequence synchronizes the status with the controlled device.
However, if the controller receives a change notification from the controlled device during this query sequence, the controller needs to query again
.
Note that, as with a GPI controller made by user, if you want to apply the physical positions of the controller to the device,
there is no need to execute the above sequence
.
If you want to apply the physical positions of the controller to the device immediately after a connection is established, without any user interaction,
simply use set commands to do so.
A
pplying the most recent status of the controller to the device
Depending on the controller specifications, the above two sequences may be used in combination
Example: The GPI fader uses the status of the controller, bu
t
other parameters use the status of the controlled device.
Parameter query sequence at any given time
LEDs and displays on the GUI
Indications are updated on the basis of the result notifications returned after the processing of the set commands
.
A
lternatively, send an explicit get request and apply the result to the indications, as shown below.
Controlled deviceRemote controller
Connection unknown
Connection detection
Connected physically
Starting
* With the first devstatus devmode
request, a result notification
is returned.
Device starting
Device normal running
NOTIFY devstatus devmode "normal"
OK devstatus devmode "normal"
devstatus devmode
Controlled deviceRemote controller
Normally runningNormally running
OK set MTX:mem_512/60000/0/0/0/0/0 0 0 -7760 "-77.60"
set MTX:mem_512/60000/0/0/0/0/0 0 0 -7760
OK set MTX:mem_XXX/XXXXX/X/X/X/X/X X X XXXX "XXXX"
OK set MTX:mem_XXX/XXXXX/X/X/X/X/X X X XXXX
OK set MTX:mem_XXX/XXXXX/X/X/X/X/X X X XXXX "XXXX"
OK set MTX:mem_XXX/XXXXX/X/X/X/X/X X X XXXX
SyncedSynced
* Repeat set for all the necessary parameters.
Apply
Apply
Apply
Controlled deviceRemote controller
Normally running
Normally running
Connection detection
OK get MTX:mem_512/60000/0/0/0/0/0 0 0 -7760
get MTX:mem_512/60000/0/0/0/0/0 0 0
OK get MTX:mem_XXX/XXXXX/X/X/X/X/X X X
get MTX:mem_XXX/XXXXX/X/X/X/X/X X X
OK get MTX:mem_XXX/XXXXX/X/X/X/X/X X X
get MTX:mem_XXX/XXXXX/X/X/X/X/X X X
SyncedSynced
* Repeat get for all the necessary parameters.
Apply
Apply
Apply
Controlled deviceRemote controller
OK get MTX:mem_512/XXXXX/X/X/X/X/X X X
get MTX:mem_512/XXXXX/X/X/X/X/X X X
Apply
An event occurs that
calls for a value to be queried.
One example of using this sequence would
be for refreshing the UI after boot-up or after
changing tabs.
MTX3/MTX5-D/XMV Series/EXi8/EXo8 Remote Control Protocol Specifications V1.0.1
18