Integrations

Hardware Integration Without a Closed Ecosystem.

OnAirRender Studio is designed to work across broadcast hardware and software environments through native SDKs, device protocols and network interfaces.

How to read the status labels

  • Available Implemented and working for the described use.
  • In Development Being implemented or tested.

Where a note names a model, that is the hardware the integration has been tested with. Other models of the same family may behave differently until they have been verified.

Video I/O

Native SDKs bring physical and network video into the engine and back out, each device handled in its own worker process.

  • Blackmagic DeckLink

    Desktop Video SDK · SDI

    SDI capture and playout through DeckLink cards, handled in separate worker processes, with embedded audio and held outputs that show an idle slate when nothing is routed.

    Tested with DeckLink 8K Pro and DeckLink 4K Extreme 12G. Capture audio currently uses channels 1–2. SDI fill and key output is not implemented.

    Available
  • NDI

    NDI 6 · receive

    Discovery of NDI sources on the network and reception of their video and audio in a resident worker process.

    Requires the NDI runtime. NDI output is not implemented.

    Available

Routing & Switching

Routers and production switchers are represented as devices whose state can be read and, where validated, controlled.

  • Blackmagic ATEM — discovery and state

    ATEM protocol (UDP 9910)

    Finds ATEM switchers on the network and reads their configuration and state: M/Es, keyers, AUX buses, sources and macros.

    Tested read-only with an ATEM 1 M/E Production Studio 4K.

    Available
  • Blackmagic ATEM — switching control

    ATEM protocol (UDP 9910)

    Cut, auto, T-bar, source and AUX control from control panels and from a virtual video mixer bound to a physical switcher.

    Validated against a simulator built from a real device state; not yet verified on hardware.

    In Development
  • Blackmagic Videohub

    Videohub Ethernet protocol (TCP 9990)

    Reads and sets crosspoints and labels from a routing window, with the router shown as a device in the Physical View.

    Tested with a Smart Videohub 40x40. Automatic crosspoint allocation for external sources is new and still being validated.

    Available
  • Videohub control panels

    Master Control Pro · Smart Control Pro

    OnAirRender acts as the router for Blackmagic Videohub control panels and can learn their button layout.

    First connection trials completed; button learning is not yet confirmed on hardware.

    In Development

Recording & Playback

Disk recorders and software recorders participate in the same operational model as every other device.

  • Blackmagic HyperDeck

    HyperDeck Ethernet protocol (TCP 9993)

    Deck control with transport, record, clip lists, slots and settings. A deck's playback can be used as a picture source in the engine.

    Tested with a HyperDeck Studio 4K Pro. The protocol does not offer file deletion or capacity reporting.

    Available
  • Software recorders

    Virtual devices

    Video and audio recorder nodes in the Operational View, with transport controls and record-on-signal.

    Available

Audio & Control

Audio consoles, control surfaces and lighting desks connect through their native protocols.

  • Behringer X32

    OSC · X-USB audio

    Metering and status over OSC, routing read-back, and multichannel audio through the X-USB card.

    Routing changes written from OnAirRender are still being validated on a physical console.

    Available
  • Workstation audio

    ASIO · WASAPI

    Audio routing through the workstation with level and phase analysis, meters and a 1 kHz test generator.

    Available
  • Elgato Stream Deck

    USB HID · network protocol

    Keys, dials and pages with key images rendered by OnAirRender, configured per action in the control settings.

    Tested with Stream Deck Studio, Network Dock and Stream Deck +. Other models are described but untested.

    Available
  • X-keys

    P.I. Engineering · USB HID

    Buttons, jog, joystick and T-bar levers, lamps and backlight.

    Tested with XK-12 Joystick and XKE-40.

    Available
  • Skaarhoj

    Raw Panel protocol (TCP 9923)

    A panel face model built from the panel's own topology, with RGB keys, displays and strips.

    Tested with in-house panels.

    Available
  • grandMA3

    MA-Net3 discovery · OSC

    Passive console discovery and OSC commands sent from control panels.

    Control of a physical console is not yet verified.

    In Development

Network & Automation

Discovery, scripting and facility devices that let workflows react to and act on the studio environment.

  • Network device discovery

    Ping/ARP · LLDP · mDNS · SNMP · vendor handshakes

    Finds devices across the studio network and on the workstation's PCIe and USB buses. New devices are listed for the operator to confirm.

    Network links are inferred from switch data and marked as inferred; video cabling is documented by the user.

    Available
  • Lua scripting

    Lua 5.4

    An embedded Lua runtime with a namespaced API for I/O declaration, streams, layers, devices, timers and data.

    Available
  • Comet environmental sensors

    SNMP v1 · values.xml

    Temperature, humidity, pressure and CO₂ readings with threshold events.

    Read-only.

    Available
  • Shelly and Arduino Opta relays

    Shelly Gen2+ RPC · Opta relay firmware

    Relay control for facility functions, grouped in a virtual relay bank.

    Switching is validated on simulated devices; physical relays are currently only read.

    In Development
  • Global Caché iTach

    IR (TCP 4998)

    IR code learning and sending for equipment without a network control interface.

    Validated against a simulated unit.

    In Development

Product names and trademarks belong to their respective owners. References to third-party products describe interoperability or development work and do not imply endorsement.

Missing a Device Family?

If you manufacture or operate broadcast equipment that should be part of the list, we would like to discuss a native integration.