Operational View
Build and operate production workflows using connected functional nodes.
AvailableBroadcast Studio Orchestration Platform
Professional broadcast orchestration software connecting video, devices, graphics and automation in one unified production environment.
Currently in active development.
The Operational View in the current development build.
The unified studio
Modern broadcast environments combine cameras, switchers, routers, recording systems, graphics engines and control interfaces. OnAirRender Studio brings these systems into a unified operational model, helping production teams manage complex workflows from one place.
Equipment as it is installed: discovered on the network and the workstation, or added by the operator.
What each device offers, mapped to this workstation's hardware configuration.
Logical nodes and directed connections that describe intent: what should reach where.
The scripts, panels and operator actions that run the programme.
The diagram describes the architecture. Device support differs per manufacturer and model; see Integrations for verified status.
Platform capabilities
Build and operate production workflows using connected functional nodes.
AvailableRepresent equipment, connections and signal paths within your studio infrastructure.
AvailableCoordinate supported devices through native APIs and control protocols.
AvailableEvery function of the platform is available to Lua scripts, so any production task can be automated.
AvailableDesign the operator's own control screen, with live monitors, buttons and lists, and run it with the project.
AvailablePlay and operate broadcast graphics designed in OnAirGraph, layered over video and fed with live data.
AvailableOrganise studio devices and functional resources in a shared operational workspace.
In DevelopmentStream Deck, X-keys and Skaarhoj keys and levers run actions on the devices of the project.
AvailableThe software
Every product image on this site comes from the current development build of the application. Device names and values come from test setups.
Operational View
Sources, destinations and virtual devices are placed as nodes. A connection states an intent, for example that a picture should reach a recorder, and OnAirRender works out how to deliver it through the hardware available on the workstation.
Physical View
Discovered devices appear with their connectors, rooms and online state. Physical cables, network media transport, USB links and logical routes are drawn as distinct connection types.
Device control
Stream Deck, X-keys and Skaarhoj panels are configured per key and per lever. Each control runs an ordered list of actions on devices in the model, such as an audio channel mute or a router crosspoint.
Operator interface
The operator's interface is designed in OnAirRender Studio itself: live video monitors, buttons, lists, tabs and status fields are placed on a canvas, and each control is wired to Lua. A production gets exactly the control screen it needs, from a single take button to a complete live control desk.
Integration architecture
OnAirRender is designed around an extensible integration architecture, allowing broadcast devices and software systems to participate in coordinated workflows.
Native SDKs bring physical and network video into the engine and back out, each device handled in its own worker process.
Routers and production switchers are represented as devices whose state can be read and, where validated, controlled.
Disk recorders and software recorders participate in the same operational model as every other device.
Audio consoles, control surfaces and lighting desks connect through their native protocols.
Discovery, scripting and facility devices that let workflows react to and act on the studio environment.
Broadcast graphics are designed in OnAirGraph and played as layers by the OnAirRender engine.
Technology partners
We are interested in working with broadcast hardware manufacturers, SDK providers and system integrators to expand the capabilities of the OnAirRender platform.
Devices are integrated through their native SDKs and protocols and exposed as resources that workflows can use. Each new integration is validated on hardware before it is described as available.
Interested in OnAirRender Studio, hardware integration or a technical partnership? Get in touch.