13
0
livetrax/libs/audiographer
2013-11-26 10:24:51 -05:00
..
audiographer resolve merge with master (?) 2013-11-26 10:24:51 -05:00
doc Fix export, which has been broken since the boost::signals2 changes. Also update Audiographer, bacause of its incomplete sndfile handling. Audiographer is equal to revision 74 2010-03-15 19:11:48 +00:00
private 'libs/audiographer' - Try 'lrintf' instead of 'rintf' which isn't available in MSVC 2013-09-05 09:21:30 +01:00
src 'libs/audiographer' - Use 'alloca()' for a stack based array whose size is unknown (required to be buildable with MSVC) 2013-09-05 09:18:30 +01:00
tests Use uint32_t type instead of uint 2013-07-11 15:16:50 -04:00
COPYING Re-integrate export-optimization branch. 2009-12-27 14:46:23 +00:00
README Fix export, which has been broken since the boost::signals2 changes. Also update Audiographer, bacause of its incomplete sndfile handling. Audiographer is equal to revision 74 2010-03-15 19:11:48 +00:00
wscript Apply patch from timbyr to fix building with --test. 2011-11-13 03:54:29 +00:00

AudioGrapher is Copyright Sakari Bergen 2009-2010

AudioGrapher is best described as a signal flow management library.
It includes facilities to build graphs out of signal processing elements.
Once a graph is set up, all signal flow within the graph happens automatically.

The data flow model in Audiographer is dynamic instead of synchronous - the type
and amount of data that goes in to a graph may differ from what comes out.
AudioGrapher is aimed mostly for usage by developers, as it includes lots of
facilities that ease the development process.

The main aim of AudioGrapher is to ease development and debugging of signal flow
graphs. It makes heavy use of modern C++ techniques like templates, and uses the
boost libraries a lot.

The essential classes in AudioGrapher are Sink, Source and ProcessContext. These
three define the signal flow in a graph. In addition, the core of AudioGrapher
includes lots of utility classes.

AudioGrapher includes a bunch of ready Sink, Source and Vertex implementations.
Some are utilities used when developing more vertices, while others are general
utilities (file i/o, sample rate conversion etc).