Setting Up HDMI Systems
Dealing with Sources with Limited Sink Support
For sources with limited sink support, the following system design considerations and control suggestions are provided.
System Design Considerations
If at all possible, replace the source device with one with that supports more sinks.
If a repeater is connected between the source and the HDMI UTPro and the repeater is not necessary, remove the repeater and connect the source device directly to the HDMI matrix switching input. The HDMI UTPro becomes the first repeater and one sink is eliminated, allowing you to add one more destination to the system.
If a repeater is connected between the HDMI UTPro and a display device and the repeater is not necessary, remove the repeater and connect the display device directly to the UTP
Example of Reducing Sinks:
A reduction in sinks can be made by removing unnecessary repeaters either upstream or downstream of the HDMI UTPro.
If a source supports five sinks downstream of the first repeater and the sinks (repeaters and destination devices) total six, removing a repeater will reduce the number to five. In this example, the source will not transmit the protected content until the number of sinks is reduced to five or less.
Important: If the repeater that is removed is downstream of the HDMI UTPro, you will need to clear the input’s sink key cache and then persist the cleared state to eliminate the key(s) before routing the source to any of the destinations; for instructions, see page 68.
Control Suggestions
Either a controller or a modified configuration file can provide a workaround for sources with limited sink support.
Program an external controller so that the source(s) can only be routed to a limited number of specific destination devices.
Use XNConnect to create a virtual matrix (VM) that limits routing of the source(s) to a limited number of specific destination devices.
External Controller
For control programming information for an HDMI UTPro using an external controller, see the external controller’s documentation.
Tip: Locking the control panel after routing the desired sources can prevent accidental switching of a source to more sinks than it supports and the resulting need to empty the cache and go through the initial authorization process again. For locking instructions, see page 55.
XNConnect
XNConnect can be used to create virtual matrices (VMs) which limit the routing of a source to specific destinations.
Caution: Virtual matrix modifications are an advanced feature of XNConnect that should not be attempted unless you are familiar with XNConnect and the AMX Matrix Switcher being configured.
To create new virtual matrices, we recommend contacting technical support (see page 43) to request a custom configuration file. If you decide to create them yourself, see page 119 or the XNConnect Help file.
VM 2 (red)
VM 3 (blue)
VM 1 (orange)
FIG. 40 Example of VMs created for control of sources with limited sink support
Instruction Manual – | 65 |
|
|
