|
AudioRack Suite is an open-source radio broadcast automation and live assist system. I started writing AudioRack in 2002 after my experience using a commercial automation system at our local community radio station, KURA. At the time, the system required constant attention as it would crash often, and I was not very pleased with the constraints that the system placed on automation. Initially, I used AudioRack as a file player running alongside the existing automation system at KURA to do my weekly show. This allowed me to build my playlists at home and move everything over to KURA. At the same time, I was also using iTunes and some apple scripts to run automation for an internet radio station that I was running on the side. After starting development, it became apparent to me that the AudioRack project was an opportunity to build a stable, scalable radio automation system from the ground up that would handle all of the things that I wanted: Portable playlists that could be moved with associated media between locations, network access for remote management and control, shared music libraries, software based mixing system to eliminate the need for an external mixing console, and an organic, interactive automation system that adjusts to programming material inserted by live DJs. Pre-generated rotations are not the friend of the live DJ!
Years later, AudioRack Suite is happily running both KURA and MountainChill.com as new functionality continues to be added. Get involved in the development of AudioRack Suite - help make it into what you need.
System Overview
The system is composed of the following components:
- ARServer - multi-client, mutli-bus audio engine.
- Clients - (ARStudio and ARManager) User interfaces to the ARServer and library/automation database.
- Database (MySQL 5.1 and latter supported).
- File System - Audio File Storage, anything from a local hard disk to a networked RAID system.
- Audio Input/Ouput device(s).
Clients can run on either the same host computer as the ARServer or on a separate computer which has network access to the database and the ARServer. Multiple ARServer instances can be run on a single computer.
ARServer
ARServer manages the playing, recording, and processing of all the audio
- Multi-bus, multi-output mixer can handle live audio input sources, VoIP audio sources, and file based audio sources.
- Extended IAX VoIP protocol allowing AAC-LC coded for high quality mono and stereo remote feeds.
- Manages the current playlist, handling segues, logging item meta-data, performing database queries for automation, etc.
- Support for four live input mute groups and monitor mix-minus functions for it's audio outputs.
- Automatic mix-minus for VoIP feed to callers when an VoIP audio source is live.
- Network machine control hardware is available to control Turntables, CD players, telephone mutes, etc, associated with live inputs and mute groups.
- Audio Processing: 8 AudioUnit processor plugin per player, output, or recorder, processor speed allowing.
- Multiple simultaneous audio file recorders and SHOUTcast mp3 stream encoders from any mix bus or live input source.
- SHOUTcast stream encoder will handle track posting from program logs.
- Broadcast delay - can be applied to any output or recorder.
- Multiple ARServer instances can share a common database library.
- Library and Automation make use of a customizable relational database structure.
- Can be accessed and operated from a simple telnet session, or from the user friendly ARStudio front end client.
|
ARManager Client
ARManager is the Operations Mangement component of AudioRack Suite
- Intuitive library, automation and schedule management user interface.
- Administer multiple independent libraries or single libraries shared by multiple ARServers.
- Multiple ARManager clients can access a single database at the same time.
- Easily switch between databases.
- Graphical schedule viewer.
- Customizable database queries.
- Full editing of item meta data.
- Tight integration with ARStudio if ARStudio is made available on the same machine.
- Database changes are performed through ACID compliant sessions to prevent corruption.
- Local or network access to a database for both single computer and remote operation.
- SSH tunnel support for secure access to a database located behind a network firewall.
- Multi-window interface for items and libraries, with window to window drag and drop support.
- Item type transparency - Playlists, Files, Tasks, etc are all managed the same.
- Text and XML exporting and reporting from most windows and views.
|
MAC OS X SYSTEM REQUIRMENTS
- PowerPC (native) or Intel (using PowerPC emulation) based Macintosh system. This software in not a universal binary format. Any one interested in compiling and testing a universal binary?
- QuickTime 7.0 or higher.
- OS X 10.4 or 10.5. Will NOT run in 10.6 out of the box, due to Apple's elimination of PowerPC emulation.
- At least 256M of RAM, 512M would do you good.
ARServer allocates wired (dedicated, never paged out) memory for all of it's audio buffers. This work out to around 4MB per player at the 44.1ksps file sample rate plus 34MB for an eight channel, 96 ksps mix bus buffer and an additional 8MB per input definition (for mix-minus buffer).
- 1.2 GHz G4 or faster recommended for default 96ksps audio engine sample rate. If the sample rate is reduced to 44.1ksps, a 400 MHz G4 does fine.
- Access to a MySQL version 5.1 or latter server. Any one interested in helping to add SQLite and PostgreSQL support?
|