The viz_probel plug-in allows the dynamic assignment of IP streams (2110) to the Viz Engine input channel.

Viz Engine manages a number of external sources to map them to a smaller number of available input channels. Viz Engine maintains control over which input channels have fixed sources from startup and which input channels can request a new source. The viz_probel plug-in maintains a table that maps a source to the Viz Engine input channel. Since each input channel in the Viz Engine corresponds to a physical Matrox connection. The plug-in effectively maps external sources to a particular Matrox physical connection.

The external component that communicates with viz_probel plug-in is usually a Virtual Studio Monitor (VSM) which communicates with the viz_probel plug-in via SW-P-08 general remote protocol.

VSM has a matrix composed of the sources and its corresponding output. This matrix state is saved in the viz_probel plug-in.

The viz_probel plug-in has the following tables:

• VSM output and corresponding sources.

• VSM output and corresponding Viz Engine input channel.

• Matrox physical connection and Viz Engine input channel. Configured by the user.

• Matrox physical connection and VSM output. Configured by the user.

Message Interface

Communication via message passing is supported which is similar to a REST API. Messages can be sent via Request(location, message) in the Viz Script.

The response is asynchronous and is only given to the plug-in user when there is change in the internal mappings.

Register

The following must be called at least once to be able to connect to the VSM.

Location: /Extensions/Probel/register

Response:

Unregister

The following must be called to disconnect from VSM.

Location: /Extensions/Probel/unregister

Response:

Sources

The following returns the corresponding Viz Engine input channel. This generally changes the matrix in VSM but not always. {} can also be releaseall or requestall.

releaseall attempts to release all sources while requestall attempts to request all available sources.

Location: /Extensions/Probel/sources/{}

Response:

The following releases a channel in the matrix in VSM.

Location: /Extensions/Probel/sources/{}/release

Response:

The following releases an all channel in the matrix in VSM except a few of them. {} can have multiple sources separated by "-". Example /Extensions/Probel/sources/releaseall/except/3-4-5-6

Location: /Extensions/Probel/sources/releaseall/except/{}

Response:

Debug

The following is used for debugging SW-P-08 implementation. If {} is 0, it sends an ImplementationRequest. If {} is 1, it sends a CrossPointTallyDumpRequest.

Location: /Extensions/Probel/debug/{}

Response:

The following is used for debugging SW-P-08 implementation. If {} is 0, it sends a CrossPointInterrogate, the next {} is a parameter indicating the output. If {} is 1, it sends a AllSourceNamesRequest, the next {} is a parameter indicating the names length.

Location: /Extensions/Probel/debug/{}/{}

Response:

The following is used for debugging SW-P-08 implementation. If {} is 0, it sends a CrossPointConnect, the next {} are parameters indicating the output and source. If {} is 1, it sends a SingleSourceNameRequest, the next {} are parameters indicating the names length and source.

Location: /Extensions/Probel/debug/{}/{}/{}

Response:

Response

The following is how the asynchronous response looks like. {} corresponds to the source.

Location: /Extensions/Probel/sources/{}/change

Response:

Configuration

To Configure this plug-in create a file called {VizEngine-Config-dir}/extensions/Probel.json. This file is used for every running instance of Viz Engine. To have a specific configuration for a running instance you can create configuration files like {VizEngine-Config-dir}/extensions/Probel-{Instance-Number}.json.

Supported config parameters:

• address: Defines the port that should be used in VSM if connection mode is configured as server (depending on the connection-mode configuration), or the address and port of VSM if configured as client.

• backup-address: Defines the port that should be used in VSM backup if connection mode is configured as server (depending on the connection-mode configuration), or the address and port of VSM backup if configured as client.

• connection-mode: Determines whether the plug-in should act as a server or client. 0 for server or 1 for client.

• fixed-entry-offset: Sources that should not be changed. This sources can not be released by plug-in the user.

• delay-in-fields: Sets the field delay before giving the response to the plug-in user.

• disconnected: Defines what should be considered as disconnected sources. Several sources can be defined separated by comma. 

• range: Limits the range at which the plug-in user can operate. This is used in the event multiple Viz Engine instances are operating using the same VSM server but must operate only on a subset of sources.

• vizch-vsmout: Shows which Viz Engine input channel corresponds to which VSM output.

• vizch-matroxch: Shows which Viz Engine input channel corresponds to which Matrox physical connector. This should match with the configuration in the usual Viz Engine configuration file.

• extended-message: Enables extended support for Probel which adds support for a large matrix with more than 1024 sources.

The Probel .json file could then look like this:

Sample Script

The following is an example of most of the functionality presented above:

As per the documentation, the user needs to call first register to be able to use the other functions.

Debug

To enable debug logs go to the usual Viz Engine configuration file and enable ACE logging:

ACELogParams = -f OSTREAM|STDERR|VERBOSE_LITE|VERBOSE -p STARTUP|SHUTDOWN|~TRACE|DEBUG|INFO|WARNING|NOTICE|ERROR|CRITICAL|ALERT|EMERGENCY

This allows for the user to see the raw messages that are being sent and received between the VSM and the plug-in.

Troubleshooting

To be able to troubleshoot it is important to understand the console log messages.

Suppose we have the following tables:

(MatroxCh#, VSMOut#): (0, 15), (1, 0), (2, 3), (3, 12), (4, 4), (5, 5), (6, 6), (7, 7).
(MatroxCh#, VizCh#): (0, 1), (1, 0), (2, 3), (3, 2), (4, 4), (5, 5), (6, 6), (7, 7).
(VSMOut#, VizCh#): (0, 0), (3, 3), (4, 4), (5, 5), (6, 6), (7, 7), (12, 2), (15, 1).
(VSMOut#, SourceId#): (0, 3), (1, 2), (2, -1), (3, 10), (4, 0), (5, 12), (6, 8), (7, 5), (8, 0), (9, -1), (10, -1), (11, -1), (12, 11), (13, -1), (14, -1), (15, 4).

All operations are done only with the tables (VSMOut#, VizCh#) and (VSMOut#, SourceId#). (MatroxCh#, VSMOut#) and (MatroxCh#, VizCh#) are redundant.

First case: Requested SourceId# has a VSMOut# that is associated with VizCh#: 

Second case: Requested SourceId# does not have a VSMOut# that is associated with VizCh#. In this case we need to do a CrossPointConnect using VSMOut that is both associated with a non-used SourceId# and is also associated with VizCh#. In this case we could not find it: None of the VSMOut in (VSMOut#, VizCh#) has a SourceId# = -1 in (VSMOut#, SourceId#). A release is needed first.

Third case: From the above state, after releasing we can request again.