Skip to content

System Overview

This section will give you a brief overview about all components of Audectra.

Studio

The main aspect of Audectra Studio is to create/edit Scenes and to control/configure stages.

flowchart LR
    A[Studio] <--> B[Stage A]
    A <--> C[Stage B]

Read more about Studio.

Scenes

An Audectra Scene is an envelope over a synchronized set of visualizations, that can be created/edited via studio and deployed/run on stages. It holds all the required information about how the configured visualizations need to be updated and rendered.

flowchart LR
    A[Scene] ---> B[Visualization A]
    A --> C[Visualization B]
    B --> E[State 0]
    B --> F[State 1]
    C --> G[State 0]

Read more about Scenes.

Stages

The main purpose of Audectra Stages is to run scenes, split their visualization output according to configured patches and forward them to bridges in a synchronized manner.

flowchart LR
    A[Stage] ---> B[Bridge A]
    A --> C[Bridge B]
    B --> E[Channel 0]
    B --> F[Channel 1]
    C --> G[Channel 0]

Each stage has two components:

  • Stage Agent, which does the heavy lifting.
  • Stage CLI, which allows to control the stage locally.

Read more about Stages.

Bridges

Bridges are responsible for forwarding the visualization render outputs of scenes to corresponding hardware devices or software components, that eventually apply the render outputs to displays, strips, light bulbs or panels.

Each stage can have multiple bridges, and each bridge multiple channels.

Patches

As you might have guessed, a patch basically maps the visualization render outputs of scenes to bridges and their channels.

Extensions

The Audectra SDK allows you to easily create your own signal/render nodes, that can then be deployed for use in scenes on studio and stages.

Read more about Audectra SDK.