# Content IO

Content provider device nodes are the ones that can receive or send content aka Textures. Among these there are:

* **Video in/out**: these are
  * *Deltacast*
  * *BlackMagic*
  * *DirectShow* compatible sources
* **NDI**
* **Spout**
* **Unreal Texture Share**

All of the above are described in detail in the following pages, except Unreal Texture Share which is described in [Unreal Engine pages](/real-time-content-playback/unreal-engine-integration-overview.md).

## Receiving Content

As usual the process starts in the Devices window.

### Create Receiver Device Nodes

<div align="left"><figure><img src="/files/G03hrJCtgYLVSftVMDvU" alt=""><figcaption></figcaption></figure></div>

The initial setup for receiving Content (a Texture) into LightAct always starts in the **Devices** window where you have to create an appropriate **Receiver** device.

### Getting Content into Layer Layouts

<div align="left"><figure><img src="/files/S4LhRNpjQHKefPwAUytQ" alt=""><figcaption></figcaption></figure></div>

To get the texture into LightAct's layer system you will always use the same node. It's called **Get Texture (from Device)**.

<div align="left"><figure><img src="/files/votlC6FsC4HkCnvMjDjH" alt=""><figcaption></figcaption></figure></div>

You can find it by typing in get texture device or similar search keywords.

{% hint style="info" %}
**Good to know**: in most cases you will be using [Content Input layer template ](/layers-and-layouts/stock-layer-templates/content-layer-templates/content-input-template.md)to get the content into LightAct's layer system.
{% endhint %}

## Sending Content

<div align="left"><figure><img src="/files/AhmSsC88hSMKXnbqxROu" alt=""><figcaption></figcaption></figure></div>

LightAct also allows you to send Texture through Content Sender Device nodes.

<div align="left"><figure><img src="/files/KVqLLC8hnk1F71JWpYWe" alt=""><figcaption></figcaption></figure></div>

A Layout node that works with these *Sender* Device nodes is called **Set Texture (to Device)**.

{% hint style="info" %}
**Good to know**: a Stock Layer Template that will give you a head start is called [Send texture](/layers-and-layouts/stock-layer-templates/generative-layer-templates/send-texture.md).
{% endhint %}

## Special Cases

Some content inputs are slightly different, so you'll find additional information below.

### Deltacast

{% hint style="warning" %}
Please note, LightAct does not support receiving or sending Interlaced video streams.
{% endhint %}

Deltacast requires a special handling of its FLEX technology. Read more about it:

{% content-ref url="/pages/frufcyhXhma3aqfpdpPk" %}
[Deltacast FLEX Management](/integrations/content-io/deltacast-setup/flex-management.md)
{% endcontent-ref %}

### RealSense

RealSense is primarily designed for computer vision so there is a slightly different approach.

{% content-ref url="/pages/1XDWWpDJsAexKTE4L0ux" %}
[RealSense](/integrations/content-io/realsense.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.lightact.com/integrations/content-io.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.