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.
Blackmagic MultiView 16 RS-422 Protocol
General
The RS-422 protocol can be used to control Blackmagic MultiView 16 as a slave device from
third party routers and automation systems.
The “Leitch Server” mode implements the router (server) side of the Leitch Serial Pass Through
Protocol as specified in section 4 of Leitch document SPR-MAN revision D. In “Leitch Client”
mode, the Blackmagic MultiView 16 implements the controller (client) side of the Leitch terminal
protocol. Set the desired leitch mode in the ‘configure’ settings in the Blackmagic MultiView
Setup software.
This document describes the commands and parameters in the protocol that are relevant and
supported by Blackmagic MultiView 16. Other commands and parameters specified in the
Leitch protocol are accepted but ignored.
38Developer Information
To Next Page
Loading...
Need help?
General
