NDI camera missing: discovery, video and PTZ checks

Check discovery first

Power the camera and enable its NDI output. Put camera and computer on the intended network; guest Wi-Fi, VLAN isolation, firewalls and macOS local-network permission can prevent discovery. A camera showing in OBS does not prove a separate GA360 application can discover it.

Search and assign

1. Open the application's local NDI search/discovery control. Refresh after the camera has finished starting.
2. Where supported, enter the camera IP to search when multicast discovery is blocked. An IP hint does not change the sender's identity or enable a disabled NDI output.
3. Select the exact sender and save the intended camera slot. Keep friendly labels distinct from the actual network sender/input assignment.
4. Inspect the actual picture before confirming the assignment. Avoid assigning the same input to independent numbered cameras unless that workflow explicitly supports sharing.
5. For PTZ, select the correct camera target and connect its controls. Verify PTZ capability and current live image before enabling movement.

Check dependencies separately

OBS NDI input uses its NDI plugin and runtime. Some local GA360 monitoring/control functions have their own runtime requirements. Verify what the installer reported and use the application's dependency-repair instructions. Installing a plugin in an unrelated OBS instance may not repair the managed instance.

If video works but PTZ does not

Confirm the selected target, native NDI PTZ support or configured control protocol, and exact sender binding. Center sticks, release the hold trigger and retry the control connection. Do not treat a green saved preset or visible video as confirmation that PTZ movement has connected.