Tools

Imagemap
ToolsBuild systemsCompilersI/O Libraries used in this courseTiming and performanceQuality and accuracy
hide
Tools
hide
Build systems
leaf
Simplify building of applications by handling depencies and compilers based on the local environment
hide
Cmake
hide
www.cmake.org
leaf
cmake.org > Cmake > Help > Documentation User Link
leaf
Generates a platform specific Makefile or IDE project (e.g. Xcode or VS projects)
leaf
run cmake and then make to build (or open the generated project)
hide
additional options can be added to cmake or make to adjust for particular needs
leaf
e.g. for debug, or to add defines or compilation options
hide
CMakeLists.txt file
hide
Start with:
leaf
project(csound_test) cmake_minimum_required(VERSION 2.8)
hide
to build applications:
leaf
add_executable(executable file.c file2.c)
hide
dependencies:
leaf

include_directories("/usr/local/include")
target_link_libraries(executable portaudio)

hide
better:
leaf

find_library(CUNIT_LIBRARY cunit)

if(CUNIT_LIBRARY)

  find_path(CUNIT_INCLUDE_DIR cunit.h)

  include_directories(CUNIT_INCLUDE_DIR)

  target_link_libraries(application ${CUNIT_LIBRARY})

endif()

hide
even better if cmake support for the library exists:
leaf
find_package(LibXML++ REQUIRED) include_directories(${LibXML++_INCLUDE_DIRS})
set(LIBS ${LIBS} ${LibXML++_LIBRARIES})
hide
More details:
leaf
cmake.org > Wiki > CMake:How To Find Libraries User Link
hide
to build libraries:
leaf
add_library(<name> [STATIC | SHARED | MODULE] [EXCLUDE_FROM_ALL] source1 source2 ... sourceN)
hide
Others
leaf
Scons
leaf
Autotools
leaf
Waf
hide
IDE projects
leaf
Generally not cross-platform
hide
Compilers
leaf
MS compilers
leaf
GNU Compiler collection (GCC)
leaf
LLVM (clang)
leaf
Intel compiler (icc)
leaf
etc...
hide
I/O Libraries used in this course
hide
libsndfile
leaf
mega-nerd.com > Libsndfile User Link
leaf
Read/write Audio files
hide
Portaudio
leaf
portaudio.com User Link
leaf
Play and record audio in realtime from sound cards
leaf
If possible install them from package managers like apt-get or homebrew
hide
Timing and performance
hide
Use timers within the program
leaf
#include <time.h>

clock_t begin, end;
double time_spent;
begin = clock();
/* here, do your time-consuming job */
end = clock();
time_spent = (double)(end - begin) / CLOCKS_PER_SEC;
leaf
But this is not presice enough on Linux... so use (on UNIX variants):
leaf
#include <sys/time.h>

struct timeval start, end;
double mtime
long seconds, useconds;
gettimeofday(&start, NULL);
usleep(2000);
gettimeofday(&end, NULL);
seconds = end.tv_sec - start.tv_sec;
useconds = end.tv_usec - start.tv_usec;
mtime = ((seconds) * 1000 + useconds/1000.0);
hide
Use the time stamp counter (TSC), which although not accurate in terms of wall clock time, can give a good measure of actual CPU processing time.
leaf
Or examine and count assembler instructions if the process is small
hide
Profiler
leaf
Provides relative execution times for different functions
leaf
To examine bottlenecks and suggest areas for improvement
hide
Performance can be different every time, so an average over multiple runs is recommended
leaf
Statistics like standard deviation can also be useful as they can inform about the variability of execution time
hide
Quality and accuracy
leaf
Rule of thumb: Faster algorithms have less accuracy
leaf
This generally results in inferior sound quality
hide
Error for signals is commonly quantified using Mean Squared Error calculation
leaf
Must have a benchmark signal
leaf
Then calculate MSE with relation to this one
leaf
Add the squares of the difference of each sample, then divide by the number of samples
leaf
en.wikipedia.org > Wiki > Mean squared error User Link
leaf
This can allow comparison between different methods
leaf
However, it can't tell whether it sounds better, as it is too broad