> 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/sdi-encoder.md).

# SDI Encoder

1. Check for [Interoperability](/all/developing-with-ndi/ndi-certified/certification-guidelines/interoperability-requirements.md)
2. If the computer supports SDI as a monitor output, run the test as an HDMI encoder. If it does not, continue on.
3. Set the Testing application on a testing monitor
4.  Connect a previously tested SDI camera to the SDI encoder, and position and it towards the testing application as if you were testing the PTZ result
5. On the testing application, connect to the Encoder’s NDI output
6. Run the tests, and subtract the average of the PTZ camera’s previous results from the SDI encoder’s results

<figure><img src="/files/8Fd8LVClV5O3PNSpAavK" 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/sdi-encoder.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.