RenderStream Overview

RenderStream is Disguise’s scalable architecture to extend and augment the platform’s visual capabilities, plugging in both partner applications such as 3D realtime render engines and other visual functionality extensions.

A range of RenderStream plugins have been developed enabling the sequencing of content from a variety of sources including AI, AR, and graphics processing.

RenderStream is available for use in remote rendering and local rendering mode, and enabled with the same RenderStream license.

Remote Rendering

With RenderStream remote mode, the rendering is performed on one or more dedicated render nodes which are distinct from the media servers that are compositing and outputting the content. These are typically Disguise RX nodes. Render nodes can be used to scale content endlessly without being limited by the capabilities of a single GPU, and are connected together via a high-speed network configuration.

Local Rendering

With RenderStream Local mode, the rendering is performed directly on the media server that is responsible for compositing and outputting the content, which minimises interaction delay by removing the need to transport frames through a high-speed network.

RenderStream Remote vs RenderStream Local

Criteria	RenderStream remote mode	RenderStream local mode
Flexibility	Provides maximum flexibility for rendering without being tied to the media server’s physical output.	The workload must render what is required by the physical output of the media server.
Performance	Non-rendering operations cannot impact rendering performance.	Since rendering, compositing, and other operations are executed on the same media server, it may impact the performance.
Simplicity	Requires more complex set up and additional network configuration.	Provides simplified set up in Designer and does not require additional network administartion above a regular Designer session.
Network Latency	Includes additional network latency for a stream.	Does not include additional network latency since rendering and physical output are performed on the same server.
Rack Space	Requires additional render nodes and Fabric switch.	Requires less rack space.

For more information about these modes, check out RenderStream) and RenderStream Local.

RenderStream Assets

RenderStream assets are the files that are used to create the content that is rendered by the render nodes. These assets can be created in Unreal Engine, Unity, Notch, TouchDesigner, and other third-party render engines integrated via the RenderStream SDK.

Assets are stored in a specific location on the render node. By default this is the D:\Renderstream Projects folder on Disguise hardware products, and C:\Users\USERNAME\Documents\Renderstream Projects otherwise. This path is defined by a registry key, Computer\HKEY_CURRENT_USER\Software\d3 Technologies\d3 Production Suite\RenderStream Projects Folder. The path can be changed by modifying the registry key. The change will be automatically detected and the new path will be scanned for assets.

Assets are discovered automatically by d3service, which watches the RenderStream projects folder path for changes, and are shared via the network. Any Designer instance, connected to the same network will be able to select the asset.

Engine Support

Disguise provides first-party support for Unreal Engine, Unity and Notch with RenderStream. In order to communicate with Disguise, both Unreal Engine and Unity require the installation of a plugin on the render node. Visit the Disguise GitHub for the latest plugins.

Other engines, such as TouchDesigner and Volinga, are maintained by their developers. RenderStream is open source for developers to implement their own support. Take a look at Extending RenderStream to learn about making your own implementation of RenderStream for custom engines.