Preliminary finding, based on limited testing
By default, NDI sends its streams over whatever connected network or networks it determines are "best", which can cause problems at times. When using the Send NDI feature on the Mix Master or Viewport pages, there is no network selector, unlike some other network-based protocols that Hippo uses, because the NDI toolkit does not allow a user to select a specific adapter. To ensure your NDI streams are only going to the adapters you want, follow the steps below. You will need to have NDI Tools installed on the sending Hippo, and on all receiving sources.
- On one computer on the receiving network, run the Discovery Service, found in C:\Program Files\NDI\NDI 6 Tools\Discovery Service. The computer running the Discovery Service is the "Discovery Server" for that network.
- On all receiving computers, including the one running Discovery Service if you want to be able to receive the stream there, run the Access Manager app from NDI Tools.
- Go to the Advanced tab, Network Mapping section, and type in the IP address of the computer running the Discovery Service.
- On the sending Hippo, repeat steps 2 and 3.
- If Engine was running on the sending Hippo, you will need to restart before changes take effect.
- You can use the NDI Tools app Studio Manager to check that your receiving systems are seeing the NDI stream(s) from Hippotizer.
This method can be used on multiple networks, as well. Just follow steps 1-3 for the second/third/etc network. The only change is that, on the sending Hippo, you will need to add the IP address of ALL discovery servers to the Access Manager Discovery Servers list, separated by commas.
Related to:
Articles in this section
- Frequently Asked Questions
- Sending NDI To A Specific Network
- Hippotizer Two Minute Tuesdays!
- NDI Troubleshooting
- EDID Emulation
- Configuring Windows Display settings
- Configuring networked Hippotizer hosts
- How to find the serial number of your Hippotizer
- Tips on updating or upgrading to newer versions
- OutPoint Control via DMX - Explained