13
0
livetrax/libs/audiographer
Robin Gareus 6c8a062be9 move export-analysis implementation into cc-file.
lib/libfftw3f.a(apiplan.o):apiplan.c:(.text+0x430): multiple definition of `fftwf_destroy_plan'

This is because static symbols in a .dll have no fixed address and
are mapped when loading the dll. Static functions in .exe do have a fixed
address.
With a header-only implementation the functions are provided
libardour.dll and ardour.exe
2016-02-10 15:11:45 +01:00
..
audiographer move export-analysis implementation into cc-file. 2016-02-10 15:11:45 +01:00
doc
macos/audiographer/audiographer.xcodeproj
MSVCaudiographer Add newly introduced source(s) to our MSVC project (audiographer) 2016-02-10 10:55:42 +00:00
private Use proper UTF8 file-names during export. 2016-01-27 22:58:59 +01:00
src move export-analysis implementation into cc-file. 2016-02-10 15:11:45 +01:00
tests NOOP, remove trailing tabs/whitespace. 2015-10-05 16:17:49 +02:00
COPYING
README
wscript move export-analysis implementation into cc-file. 2016-02-10 15:11:45 +01: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).