How wooters/minidsp works
Project type and purpose
• Project type: a small, open-source C library (“miniDSP”) offering digital signal-processing (DSP) routines plus audio I/O and plotting utilities.
• Purpose: let applications record/play audio, read/write audio files, compute cross-correlations and delays, and invoke gnuplot for visualization.
File structure
• Top-level C modules:
– biquad.c / biquad.h (IIR biquad filter routines)
– fileio.c / fileio.h (read/write audio via libsndfile, HTK format output)
– liveio.c / liveio.h (live audio capture/playback via PortAudio)
– minidsp.c / minidsp.h (collector interface, high-level DSP functions like GCC-PHAT)
• Tests folder: examples and test programs that link against libminidsp.a and gnuplot_i:
– gcc_phat_test, gcc_phat_multi_test, testliveio, testliverec
• Build and configuration: Makefile at root and tests/Makefile; Doxyfile for docs.
README for additional insights
• Dependencies: FFTW, PortAudio, libsndfile, gnuplot_i.
• Typical workflow: user allocates buffers, calls live I/O or file I/O APIs, processes data via DSP calls, optionally plots via gnuplot_i.
Components and interactions
a. Main components
• Core Library (“libminidsp”)
– DSP Module (minidsp.c/minidsp.h: MD_gcc, MD_get_delay, MD_get_multiple_delays)
– Filter Module (biquad.c)
– File I/O Module (fileio.c)
– Live I/O Module (liveio.c)
• External Dependencies
– FFTW (FFT engine)
– PortAudio (live audio input/output)
– libsndfile (file-based audio I/O)
– gnuplot_i (plotting interface)
• Client Applications / Test Binaries
– testliverec, testliveio, gcc_phat_test, etc.
b. Relationships and data flow
• From Client → libminidsp API
• Within libminidsp: File I/O and Live I/O modules feed raw audio buffers into DSP module; DSP outputs processed data → Client or plotting.
• DSP routines invoke FFTW for transforms.
• Plotting routines link libminidsp data to gnuplot_i.
c. Architectural patterns
• Layered design:
– Hardware Abstraction (PortAudio) and File Abstraction (libsndfile)
– Core DSP Layer (FFTW-based algorithms)
– Utility Layer (filters, plotting wrapper)
• Test harness = thin client layers demonstrating API usage.
d. Key technologies/frameworks
• C99, Makefile build
• External libs: FFTW, PortAudio, libsndfile, gnuplot_i