MCM9000 uses different API for different use-cases. Please refer to the appropriate APIs described below while using or integrating them with your system.
API 2.0
The GUI of MCM9000 is and its functionality are built upon API version 2.0. The key element here is that all indexes are numeric based (i.e they are based on id’s). It reflects the internal database structure. For example, in ott, if we have 6 channels we have 6 profiles
API 3.0
API 3.0 is specifically designed for standard multi-viewers, and hardware multi-viewer.
...
** API 3.0 is useful only when the system is automated by a third party.
API 4.0
API 4.0 is specifically designed for broadcast controller integration. It replicates some behavior of NMOSbefore it existed, such that the configuration is based on senders and receivers.
...
Also, the system is static (For example, a multiviewer that has a preset configuration and can’t be changed), and doing integration based on API version 4 with the broadcast controller there is no ability to implement resource management.
MCS and API 5.0
API 5.0 is specifically designed for MCS functionality. Although, MCM9000 also shares most of the API 5.0 as MCS, there is a difference in their functionality such as,
...