Main Page

From OpenBroadcaster
Revision as of 13:58, 5 November 2020 by Radiorob (talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Media management broadcast framework comprised of server scheduling application that work in unison with Playout to deliver a scalable radio and TV streaming solution.

In this Wiki, you will find:

  • Help Getting Started resources for first run operation.
  • Technical notes and Installation Instructions.
  • DIY Resources for developers and experimenters to install onto bare metal hardware.

User guides, supported services and additional community resources [1]


A cross-platform, browser-based application that can command and control an unlimited number of playout devices. It's your central dashboard for media management, scheduling, and administration. Offers continuous monitoring, logging of alerts, dead air email alerts and displaying OBPlayer machines on a map. Sends automatic heartbeat email alerts indicating when OBPlayer has connectivity issues. Accessibility best practices, including the ability to set custom themes for individual users with different needs.

OBServer includes a feature-rich Modules environment expanding functionality.

Modules AdManager Drupal Broadcast Media Modules Interactive Tutorial
Modules Logger Modules Mapping Modules Ob2Ob
Modules Podcast Assembler Modules Program Manager Modules RDS Metadata
Modules SVG Editor Modules Now Playing


A stable and secure UNIX-based streaming media Python application controlled by an optional OBServer. It runs on any TCP/IP connection - even in a different country than the managing server. It can be installed remotely at the transmitter site, in the station's studio or as a virtual headless process on a server at a hosted data center. Continuous broadcasting no matter what happens functions by continually syncing with OBServer, looking for updated schedules, media, and priority broadcasts. Blank spots in schedule, falls back to a Default Playlist. If that fails, it goes into Fallback Media Mode then plays from the analog input. As a last resort, it will play a test signal . The application always plays valid CAP (Common Alerting Protocol) Alerts as the highest priority.

The Player can run under multiple configurations:

- Headless OBPlayer (Virtual Process)

- LIVE Assist with Mobile HTML5 Touch Screen interface.

- GTK desktop application for a Digital Video Screen.

- Standalone Emergency Alerting CAP Player supporting Audio, Image and Video alerting.

- Livewire RTP Player supports Axia digital consoles.


OBPlayer provides a GUI dashboard for creating Streaming mount points. Multiple OBPlayer instances may be run on the same hardware including the same computer as the OBServer.

Support for scheduled Line In Switching of sources such as satellite receivers.

RTP and Ravenna Audio over Internet Protocol (AoIP) is supported and tested using 5x Series players. This allows our systems to be compatible with modern digital boards (AXIA TELOS) and third party peripheral devices that support these low-latency protocols.