Beast - Music Synthesizer and Composer
C++ C Python Shell Makefile Perl Other
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
Demos
Effects
Instruments
Samples
af-tests
aidacc
beast-gtk
bse
config
data
debian
docs
drivers
ebeast
external/v8pp
keys
launchers
misc
plugins
po
r+d-files
res
sfi
skins
tests
tools
yapps2_deb
.autom4te.cfg
.gitattributes
.gitignore
.travis.yml
AUTHORS
COPYING
HACKING.md
MAINTAINERS
Makefile.am
Makefile.decl
NEWS
README.md
acbeast.m4
autogen.sh
beast.doap
configure.ac
ld-symbolic.m4 BUILD: link with -Bsymbolic-functions to optimize ELF relocations Oct 17, 2014
stamp-h.in
taptool.sh
topbuildid.hh

README.md

BEAST & BSE

License LGPL-2.1+ Build Status

DESCRIPTION

Beast is a digital synthesizer and music creation system. It has support for Linux Audio Plugins (LADSPA), multi-track editing, unlimited undo, real-time synthesis, MIDI and various free audio codecs. Bse is the Beast Sound Engine, a library providing the synthesis and audio functions used by Beast.

REQUIREMENTS

Beast is a soft realtime application which needs elevated CPU scheduling priorities to avoid audio glitches and drop outs. For this purpose, it installs a small uid wrapper which acquires nice level -20 for the synthesis threads and then immediately drops privileges. For Linux kernels of the 2.6.x series and later, this enables the low-latency scheduling behavior needed to avoid audio artefacts.

In order to build release tarballs, Rapicorn, GnomeCanvas, Ogg/Vorbis, libflac and npm are required. Support for MP3 files is optional and requires libmad (MPEG audio decoder library) when compiling Beast. Compilation requires g++-5.2.1 or later and a recent Linux distribution like Ubuntu-14.04.

INSTALLATION

In short, Beast needs to be built and installed with:

./configure
make
make check         # run simple unit tests
make install
make installcheck  # run audio tests

Note that Beast has to be fully installed to function properly, and that the binaries built in the launchers/ directory have to be installed with permissions of the root user.

BINARY PACKAGES

New source code pushed to the Beast repository is automatically built and tested via Travis-CI. Ever so often we create release candidate packages and later release packages after a stabilization phase. Some of the release candidates and the stable versions are provided as binary packages which can be installed via apt:

# Enable HTTPS transports for apt
apt-get -y install apt-transport-https ca-certificates wget
# Recognize signatures from the Beast-Team
wget -qO- https://beast.testbit.org/apt/archive.key | sudo apt-key add -
# Add Beast release packages to the repository list
echo "deb https://beast.testbit.org/apt xenial/stable/" |
  sudo tee -a /etc/apt/sources.list.d/beast-team.list
# Update package list and install Beast
apt-get update && apt-get -y install beast

The directory xenial/stable/ holds end user release packages, and the directory xenial/rc/ holds temporary release candidates.