NDI Receiver | Receives an NDI video input and provides it as a texture. | |
NDI Source List | Lists all available NDI sources. |
The NDI Receiver provides the texture of a chosen NDI source together with several meta data. The Source property defines which NDI source to use - it can be provided either as a string or using the dropdown menu that is accessed by clicking the arrow on its right.
Low Bandwidth limits the input to 640x360 pixels which saves bandwitch between the source and Ventuz andis meant to be used e.g. for preview cases. Low Latency disables frame buffering that is used to stabilize the incoming framerate. If enabled it may cause stuttering on the input depending on the NDI source and the network environment, but the frames will be processed by Ventuz without any delay.
The Tally property is based on an NDI feature that enables a receiver to tell the source that it is currently used - named after the popular concept in broadcasting. Ventuz sends a signal to the source according to the configuration of the current Pipe - so when this node is used in a Program pipe it will send an on-air signal (usually red) and on a Preview pipe it will send a previewing signal (usually green).
Like in most other Texture Nodes the Mip Map property enables automatic Mipmap generation for better quality and performance when the texture is scaled down. High Color Depth enables usage of NDIs 16-bit color depth feature while doubling GPU memory and performance.
The Volume property changes the overall volume of incoming audio. The NDI Receiver node is capable of playing back on multiple outputs Ordinals.
Each of these Ordinals can be mapped to the physical stereo pairs of your machine in the Device Configuration. You can define several mappings of a stream and channel to an output ordinal by adding any number of Property Groups with the in the Property Group List inside the Property Editor. The Stream dropdown defines which stream of the File to use. For the Channels you can choose to use any single Mono Channel, two consecutive channels as Stereo Channels or to Downmix the whole stream into a single stereo signal. In the Flags property you can turn on several options: Flip L/R swaps the left and right channels if it plays back two channels as stereo. Invert left/right phase invert the polarity of either channel. And Mid/Side to Stereo converts a mid or side channel to a stereo channel. Ordinal selects the Logical Device Ordinal used for this mapping. Gain changes the sound level of this input and the Balance adjusts the playback volume between the left and right audio channel.
The Texture output provides a reference to the received texture and can be bound to any Texture input - e.g. on the Material Node.
On the output side the node provides several information about the NDI stream. Connection Meta Data outputs any information given by the source application about the connection. Frame Meta Data provides meta data for each received frame. On Preview and On Program show whether the stream is used on any of these - using the Tally concept of NDI. Web Control URL provides a URL to a Web based Control Panel if the source application provides any information on that.
Texture Width and Height provide the stream's dimensions. The State properties Connected and Active return whether the receiver is currently connected to a source and whether it is actively decoding frames.
Note that if all input properties (except the Tally and Audio properties) are the same on two or more NDI Receiver nodes they use the same internal receiver to save time for the initial connection. You can use that to open the connection to the NDI source with one node that is not rendering anything and then you can use another NDI receiver node whose texture output is used once the Active property returns true.
The NDI Source List provides an array of all available NDI sources in the current network. You can use that array to dynamically choose any NDI source using your scene logic.