> 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/decoder.md).
# Decoder
1. Check for [interoperability](/all/developing-with-ndi/ndi-certified/certification-guidelines/interoperability-requirements.md) first. It must pass all requirements. As it does not output a signal, it must instead be able to receive an NDI signal from a device running on the current SDK version.
2. Make sure the device is tested with NDI HX2 and NDI High Bandwidth signal
3. Make sure the device is tested with Unicast and Multicast devices
4. Run ScreenCapture and capture the high refresh rate monitor
5. Run the testing application on fullscreen and connect it to [Screen Capture](https://docs.ndi.video/testing/EqLHG6swnEL4sqnELSv3/using-ndi/ndi-tools/tools-for-windows/screen-capture). Let it run for 3 minutes and get an average of latency. Keep that number somewhere
6. Run the testing application again and connect it to the NDI-enabled camera. Let it run for 3 minutes and get an average of latency. Keep that number somewhere
7. Connect the decoder and have it pull the Screen Capture NDI feed of the testing application, then output it via HDMI
8. Point the camera at the monitor and connect the testing application to the camera
9. Run the test again for 3 minutes; the latency should be much higher than your first test
10. Subtract the latency average in steps 5 and 6 from the higher number to get the decoder's latency
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ndi.video/all/developing-with-ndi/ndi-certified/certification-process/testing-methods/decoder.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
