DirectOut PRODIGY Series Integration Configuration
Caution
Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.
Configuration Overview
A PRODIGY device connects to hi as one Node through its Ember+ provider. The Node has two capabilities on the same address and Port: Crosspoint Management for the routing matrix, and Parameter Control for the Ember+ tree. hi finds the matrices automatically.
|
Configuration |
What hi Sees |
Use When |
|---|---|---|
|
PRODIGY Routing and Parameters |
The matrices in the top three levels of the Ember+ tree as Sources, Destinations, and Crosspoints with their channel labels, and the parameters that you pin on the Node. |
hi must route PRODIGY channels, or monitor and change PRODIGY parameters such as the microphone preamp settings. |
Caution
DirectOut offers Ember+ as a separately purchased software option for each device. A PRODIGY device without the option does not provide the Ember+ provider.
Before You Begin
-
Use Node admin and open Inventory > Nodes. See Manage Nodes.
-
Confirm the license and minimum hi version in Required Configuration.
-
Confirm that the Ember+ license is installed on the PRODIGY device. The Ember+ provider runs on the management (MGMT) port at TCP Port
9000. -
Confirm the network access in Network Requirements.
Configure PRODIGY Routing and Parameters
Device Configuration
-
Obtain the Ember+ software option from DirectOut for each PRODIGY device that hi controls.
-
Install the license file in update mode. The license file is coupled to the serial number of the device.
-
Open DEVICE INFO > PRODIGY License Info and confirm that the Ember+ service is licensed and running.
-
Record the address of the management (MGMT) port. The Ember+ provider listens on TCP Port
9000on this port. Ensure that the hi server can reach the provider.
hi Configuration
-
Add the PRODIGY Series integration (manufacturer DirectOut Technologies) in Inventory.
-
Enter the device address and the provider Port for the Crosspoint Management capability and for the Parameter Control capability. hi defaults both to
9000. -
Create the Node and wait for hi to read the matrices and labels.
-
Browse the parameter tree of the Node and pin the parameters that your workflow needs. See Parameter Control Nodes.
-
After the Node is created, use Reinitialize Router in the Operations group when hi must read the matrices again.
Settings Summary
|
Setting |
Device Side |
hi Side |
|---|---|---|
|
Ember+ option |
Purchased and active on each device |
No hi setting |
|
Control Port |
Ember+ provider Port |
Port of both capabilities
|
Common Checks
|
Symptom |
Check |
|---|---|
|
The Node does not connect. |
Confirm that the Ember+ option is active, that the provider is enabled, and that its Port is reachable from hi. |
|
A matrix is missing in hi. |
Confirm that the matrix is in the top three levels of the Ember+ tree. |
|
A parameter value does not update in hi. |
Confirm that the parameter is pinned on the Node. |
Verify the Configuration
Confirm that the expected matrix and the pinned parameters appear in hi. Compare the channel labels in hi with globcon. Route a noncritical Destination from hi and confirm the change in globcon. Change a pinned, noncritical parameter from hi and confirm the change in globcon. Change the same parameter in globcon and confirm that the new value appears in hi.