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↵
↵
In the absence of simultaneous updates, the dialog expected for a simple label change is as follows:
OUTPUT LABELS:↵
6 new output label seven↵
↵
ACK↵
↵
OUTPUT LABELS:↵
6 new output label seven↵
↵
The asynchronous nature of the responses means that a client should never rely on the desired
update actually occurring and must simply watch for status updates from the MultiView and use only
these to update its local representation of the server state.
Requesting a Status Dump
The client may request that the MultiView resend the complete state of any status block by sending
the header of the block, followed by a blank line. In the following example, the client requests the
MultiView resend the output labels:
OUTPUT LABELS:↵
↵
ACK↵
↵
OUTPUT LABELS:↵
0 output label 1↵
1 output label 2↵
2 output label 3↵
…
↵
Checking the Connection
While the connection to the MultiView is established, a client may send a special no-operation
command to check that the MultiView is still responding:
PING:↵
↵
If the MultiView is responding, it will respond with an ACK message as for any other
recognized command.
109109Informations pour les développeurs
To Next Page
Loading...
Need help?
General