Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Audio Server Audio Server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Audio Server
  • Audio ServerAudio Server
  • Wiki
  • Home

Last edited by Travis Dec 28, 2020
Page history

Home

Audio Server

The Audio Server solves a variety of audio routing problems for radio stations.

Including:

  • Audio playback: Create multiple audio players, and control them with a REST API.

  • Streaming: Send audio to a live stream (Icecast or Shoutcast).

  • Recording: Record the audio output to a file.

  • Mixing audio sources: Play audio from any combination of microphone inputs, live streams, and audio files.

  • JSON Configuration: Everything is defined in simple JSON configuration files.

  • HTTP control with REST API: Easily control all aspects of the server with anything that does HTTP requests (like JavaScript).


Technical Overview

  • The Audio Server takes a set of audio sources (file, stream, audio input device), and sends them to a set of audio outputs (file, stream, audio output device).

  • Written in C++ with the JUCE framework.

  • Includes HTTP server (Civetweb) allowing control through a REST API.

  • Linux, Mac, and Windows.

  • Runs best on Linux from the command line. Mac and Windows are also supported. Windows includes a GUI.

  • Stores settings in JSON config files.

  • Launches multiple instances of the Audio Server for each config file (see Example Config Files below).

  • Each instance is controlled by the same REST API, and has its own set of audio sources and audio outputs.

  • Compiled as a single binary with minimal dependencies (only libshout needed on Linux).

Contents

Example Usage

This is the best placed to start.

  • Configuration file

    • Initializing the server from JSON configuration files.
  • REST API

    • Controlling the server through HTTP requests.

Structure

This describes the properties and methods of each component.

  • Sources

    • Audio Input Device, File, HTTP Stream
  • Outputs

    • Audio Output Device, File, HTTP Stream

Control

This is the REST API documentation.

  • Sources

    • List or edit sources.
  • Outputs

    • List or edit outputs.
  • Config

    • Read current config, or write config to JSON files.

Status

  • System

    • Status of system, and disk space.
Clone repository
  • Config
    • Webhooks
    • main
  • Control
    • Config
    • Events
    • Outputs
    • Sources
  • Diagrams
    • Two Rooms
  • Examples
    • Config
    • Control
  • Ideas
  • Status
    • System
  • Structure
    • Outputs
    • Sources
  • Home