> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/developing-with-ndi/ndi-certified/certification-process/testing-methods/ndi-monitor.md).

# NDI Monitor

1. Check for [Interoperability](/all/developing-with-ndi/ndi-certified/certification-guidelines/interoperability-requirements.md)
2. Run the testing application on a testing display connected to the PC
3. Run [NDI Screen Capture](/all/using-ndi/ndi-tools/ndi-tools-for-windows/screen-capture.md).
4. Connect to that Screen Capture setting with Studio Monitor and confirm the frame rate and resolution. Shut the Studio Monitor application down
5. Connect the NDI monitor being tested to the Screen Capture source
6. Connect a previously tested PTZ camera to the network
7. Point the PTZ camera to the NDI monitor being tested
8. Connect the testing application to the PTZ camera’s output
9. Run the test and record the results
10.  Subtract the PTZ’s previous results from the new metrics

<figure><img src="/files/CN4Lqr2iCeA2rPe7uWnu" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ndi.video/all/developing-with-ndi/ndi-certified/certification-process/testing-methods/ndi-monitor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.