Status Updates
When any route, label, or lock is changed on the multi view by any client, the multi view resends
the applicable status block, containing only the items that have changed.
If multiple items are changed, multiple items may be present in the update:
OUTPUT LABELS:
↵
7 New output 8 label
↵
10 New output 11 label
↵
↵
Requesting Changes
To update a label, lock or route, the client should send a block of the same form the multi view
sends when its status changes. For example, to change the route of output port 8 to input port
3, the client should send the following block:
VIDEO OUTPUT ROUTING:
↵
7 2
↵
↵
The block must be terminated by a blank line. On receipt of a blank line, the multi view will
either acknowledge the request by responding:
ACK
↵
↵
or indicate that the request was not understood by responding:
NAK
↵
↵
After a positive response, the client should expect to see a status update from the MultiView
showing the status change. This is likely to be the same as the command that was sent, but if
the request could not be performed, or other changes were made simultaneously by other
clients, there may be more updates in the block, or more blocks. Simultaneous updates could
cancel each other out, leading to a response that is different to that expected.
For MultiView 16 the client can change the solo source and the audio source to embed on
the output.
Solo mode needs to be enabled either from the front panel or by sending the block:
CONFIGURATION:
↵
Solo enabled: true
↵
↵
Once enabled the following block will change the SOLO source to input 11:
Video Output Routing:
↵
16 10
↵
↵
This is not available on MultiView 4.
The following block will send embedded audio from input 1 to the MultiView 16 output:
Video Output Routing:
↵
17 0
↵
↵
The following block will send embedded audio from input 1 to the MultiView 4 output:
Video Output Routing:
↵
5 0
↵
↵
37Developer Information
To Next Page
Loading...
Need help?
General
