Managing NDI signal visibility in your network
By default, NDI is designed to be open and discoverable - any NDI-enabled device on your network can see every available NDI signal on the same network.
If your requirements are simple and you do not need or want, for example, an NDI signal from Avid Media Composer in Edit Bay 1 to be visible or accessible in Edit Bay 2, you can limit NDI signal visibility to ensure each machine only sees its own NDI output.
To limit NDI signal visibility to individual machines
- Ensure you have NDI Tools installed. If you do not, download it from https://ndi.video/tools/
- Open NDI Access Manager
- Go to Receive Groups → Click on public → Delete
- Click New and enter a unique name, for example “editbay1”. Note that you should not use this name on any other computer on your network.
- Go to Receive Groups → Click on public → Delete
- Enter the same name as you did for the Receive Group, for example “editbay1”.
- Click Apply / OK
- Quit and reopen LDE and the app you intend to send an NDI signal from, for example Avid Media Composer.
- In LDE, double-click on your NDI source (or add a new NDI source if you do not have one), and select your NDI signal from the dropdown.
- Repeat these steps for any other machines on your network that you want to limit visibility on, ensuring that each machine uses the same name for both its Receive Group and Send Group, and that this name is unique to that machine. For example:
- Edit Bay 2 → Receive Group: editbay2, Send Group: editbay2
- Edit Bay 3 → Receive Group: editbay3, Send Group: editbay3
Each machine will only see its own NDI signals, and will not see signals from other edit bays.
If you’d like to undo these changes and revert to NDI’s default behavior, delete your custom Receive Group and create a new one called “public”, and do the same for Send Group. Your NDI signal will be visible to all machines that have “public” configured as a Receive Group in NDI Access Manager.