Data Portal

The Data Portal Nodes exchange data unidirectionally between each other without the typical Ventuz binding. It is possible to send data from any place to another within a single Runtime. Next to all standard data types like float, strings and arrays, the Data Portals can send textures, JSON objects and events. The connection between the Sender node and the Receiver is 1 to n. So multiple Receiver nodes can access the same Sender. Internally, the Sender Data Portal writes to the memory and is available to any Receiver Data Portal(s) to read the data. Receiver nodes can also navigate to its Sender node via the button on the bottom of the properties window.

• The ID property defines the address so that sender and receiver with the same ID can connect for the data transfer.
• The Scope of the Receiver and Sender nodes defines in which area of the Runtime the data is accessible.
  • Scene Scope has its limit within a single Scene. Another Scene e.g. the Layout Scene or a Scene hosted by a Scene Port won't access the data.
  • Pipe Scope the data is accessible within a Ventuz Pipe. If you have a Multi-Pipe scenario, for example a standard Director Preview and Program setup, the data stays within the Preview Pipe or the Program Pipe.
  • Global Scope is throughout the whole Runtime.
• Enabled flag allows for the sending of data to be enabled or disabled. (This is only available on a Sender)
• AutoCleanUp If enabled, those output properties will be automatically removed that do not have n corresponding input on selected Sender node. (This is only available on a Receiver)
• Connected indicates if the Receiver is connected to a Sender in its Scope. (This is only available on a Receiver)
• SenderEnabled indicates whether the connected sender is enabled. (This is only available on a Receiver)
• Latency output property displays the latency between the Sender and Receiver node in frames; e.g. 1 means that data is received 1 frame after it has been sent. (This is only available on a Receiver)

Note that the different scopes are not subsets of each other. For example, this means that a receiver in scope Global cannot receive data from a sender in scope Pipe and vice versa.

The Output Data properties of the Receiver are updated when the Input Data channels of the Sender are added or deleted. The Outputs are always the same as the Inputs in terms of type and name. Be aware, deleting the Input channel will also un-bind any and all bindings on any and all Data Portal Receivers with its address. If the node is not connected to a Sender, the output properties are not updated. Via the MissingSenderBehaviour property on the Receiver node you can define what happens with the outputs if the specified sender is missing:

KeepLastValues	The Receiver node keeps the last output values and does not change anything.
ResetOnlyOnLoad	The Receiver node only resets its output to the default values if the Sender is missing when the scene was loaded. Once the receiver is connected and then again loses its sender the outputs do not reset anymore.
ResetAlways	The outputs are reset every time the sender changes on the receiver node and cannot be found.

Changing the Receiver to a non-existing node, will not delete the output properties. When changing a Receiver to another existing Sender, the outputs of the Receiver, and bindings, will be affected depending on the value of the AutoCleanUp property. You can manually perform a cleanup by pressing the CleanUp button at the bottom of the PropertyEditor. On the Receiver node you additionally have the Go to Sender button to navigate to the selected Sender node.

Copyright 2025 Ventuz Technology