livetrax

History

Robin Gareus e55ef88ee9 refactoring to prepare for real-time export * add a threaded TmpFile Writer * update API calls to that process_export_fw() can be used as process_function The idea is to re-use export infrastructure from normalization: export to a tmp-file and then encode target formats after that.		2016-07-14 04:35:48 +02:00
..
audiographer	refactoring to prepare for real-time export	2016-07-14 04:35:48 +02:00
doc
macos/audiographer/audiographer.xcodeproj
MSVCaudiographer	Accommodate the fact that 'msvc_resources.rc.in' got moved to a new path	2016-05-21 10:33:18 +01:00
private	Ensure export starts with a clean state	2016-02-14 13:23:45 +01:00
src	prepare loudness normalization	2016-05-02 15:44:13 +02:00
tests
COPYING
README
wscript	prepare loudness normalization	2016-05-02 15:44:13 +02:00

README

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).