Troubleshooting: start here

Define the symptom

Write one sentence stating what you did, what you expected and what happened. Example: “I selected the saved NDI camera; video appeared but the PTZ controls did not connect.” That distinguishes picture, control and discovery instead of treating everything as a camera failure.

Check each layer

1. Account: Can you sign in to the correct Hub? Is the application included and the record assigned?
2. Computer: Is the right version running? Is storage available? Did the OS grant microphone, camera or network permission?
3. Application: Did it launch from its supported launcher? Is its local controller reachable? Is it busy updating or connecting?
4. Dependency: Does OBS connect? Is the required plugin present? Is the NDI runtime available to this application?
5. Device or network: Is the camera/reader/controller powered, on the expected network and discoverable? Does it work independently?
6. Event: Is the correct event, course, stream destination or scanner assignment selected?

Make one controlled change

Save relevant state, stop live operations where required, change one setting and repeat the same test. Avoid changing camera names, ports, passwords and assignments at the same time. Keep a note of which change affected the symptom. Do not expose a local controller to the public internet to fix a localhost problem.

When to escalate

If the same action still fails, prepare a support report with versions and exact messages. Include a screenshot of the failed step and relevant diagnostic output with credentials removed. For a live event, use your established backup procedure rather than experimenting with disruptive maintenance.