> 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/utilities/unreal-engine-sdk/ndi-receiver-actor.md). # NDI Receiver Actor An NDI Receiver Actor acts as a screen on which an NDI stream is played. The stream to be played is specified using an **NDI Media Receiver** asset. By default, the receiver actor does not have a media receiver asset set as a media source. In the **NDI IO section** of the receiver actor's settings, an existing NDI Media Receiver asset can be used, or a new one can be created. Multiple receiver actors can share the same receiver asset. #### NDI IO Settings The actor's media source references an **NDI Media Receiver** asset. Multiple NDI Receiver Actors can share the same media receiver asset. The Frame Width and Frame Height scale the display. By default, it is set up to fit a `16:9` aspect ratio. If the frames in an NDI stream have a different aspect ratio, the video will be stretched or squashed (the aspect ratio of the video will not be preserved). Enabling or disabling audio, color, and alpha channels can control which components of the stream to use for this actor. **These settings only affect this actor, not any other actor sharing the same media source**. Alternatively, displaying streams directly in an NDI Receiver Actor, users can assign an **NDI Media Texture2D** to a material and apply it to a surface. Once an NDI Media Receiver is set up, it automatically starts receiving streams when the level begins, without requiring manual activation. --- # 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/utilities/unreal-engine-sdk/ndi-receiver-actor.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.