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.

Receiving Content

As usual the process starts in the Devices window.

Create Receiver Device Nodes

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

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

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

Good to know: in most cases you will be using Content Input layer template to get the content into LightAct's layer system.

Sending Content

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

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

Good to know: a Stock Layer Template that will give you a head start is called Send texture.

Special Cases

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

Deltacast

Please note, LightAct does not support receiving or sending Interlaced video streams.

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

Deltacast FLEX Management

RealSense

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

RealSense