General Information

NMOS control is enabled on a driver level. No changes are needed in Viz Engine. NMOS connection requests must be sent out-of-band for X.mio3. For X.mio5, the requests can be either out-of-band or in-band.

  • Out-of-band: RDS and receiver NIC on the attached machines must be located in a network separated from the essence network, which hosts video, audio and ancillary data flows.

  • In-band: The RDS can be hosted in the essence network, NMOS requests are sent alongside the essence flows.

Important: PTP signals are always in-band.

Configuration

  • Configure Viz Engine as usual.

  • Open %ProgramFiles%\Matrox DSX-TopologyUtils\System64\Axxxxxx.json with any text editor, where Axxxxxx is the serial number of your installed Matrox IP card.

  • Edit the mandatory entries:

    • enabled must be set to true to enable NMOS functionality.

    • host name and port in the section fallback registration server must point to the RDS (Registration & Discovery Server) for manual configuration.

    • use service discovery must be set to true for automatic discovery of the RDS.

    It is recommended to set the Control IP and port to the values shown in the following example:

Example:
"enabled": true,
"local host name": "0.0.0.0",
"local port": 8080,
"fallback registration server": {
    "host name": "10.1.1.240",
    "port": 5432,
    "api version": "auto"
},
"use service discovery": true,
"use dns-sd unicast only": false,
"heartbeat interval": 5,
"use secure communication": false,

  • Edit all the labels, so that they can easily be identified in control applications or NMOS explorers (optional).

  • Save the file and restart either the machine or mvNetworkService from Windows services.

Special Firewall Rules

In case the a firewall is active on the system, two rules must be added for the NMOS service to run properly:

  • If the default Windows firewall is not used, UDP port 5353 must be opened for the process mDNSResponder.exe for service discovery to work. If the Windows firewall is used, this is done by the driver installer.

  • The Matrox NMOS service (mvNetworkService) must be accessible. Use the following in an administrator console to add the rule to the Windows firewall:
    netsh advfirewall firewall add rule name="Matrox NMOS API" protocol=TCP dir=in localport={local port} action=allow program="C:\Program Files\Matrox DSX-TopologyUtils\System64\mvNetworkService.exe"

    where {local port} is the listening port for the incoming requests as configured in JSON file mentioned above.