changeset 129:a34ea87daa58

converted README to Markdown
author Jamie Bullock <jamie@postlude.co.uk>
date Thu, 31 May 2012 16:25:17 +0100
parents 110afbaa8aaa
children b6bf86eafc97
files README
diffstat 1 files changed, 35 insertions(+), 42 deletions(-) [+]
line wrap: on
line diff
--- a/README	Fri Mar 30 13:26:41 2012 +0000
+++ b/README	Thu May 31 16:25:17 2012 +0100
@@ -1,77 +1,72 @@
-LibXtract  
----------
+# LibXtract
 
-LibXtract is a simple, portable, lightweight library of audio feature extraction functions. The purpose of the library is to provide a relatively exhaustive set of feature extraction primatives that are designed to be 'cascaded' to create a extraction hierarchies. 
+LibXtract is a simple, portable, lightweight library of audio feature extraction functions. The purpose of the library is to provide a relatively exhaustive set of feature extraction primatives that are designed to be 'cascaded' to create a extraction hierarchies.
 
 For example, 'variance', 'average deviation', 'skewness' and 'kurtosis', all require the 'mean' of the input vector to be precomputed. However, rather than compute the 'mean' 'inside' each function, it is expected that the 'mean' will be passed in as an argument. This means that if the user wishes to use all of these features, the mean is calculated only once, and then passed to any functions that require it.
 
- This philosophy of 'cascading' features is followed throughout the library, for example with features that operate on the magnitude spectrum of a signal vector (e.g. 'irregularity'), the magnitude spectrum is not calculated 'inside' the respective function, instead, a pointer to the first element in an array containing the magnitude spectrum is passed in as an argument. 
+ This philosophy of 'cascading' features is followed throughout the library, for example with features that operate on the magnitude spectrum of a signal vector (e.g. 'irregularity'), the magnitude spectrum is not calculated 'inside' the respective function, instead, a pointer to the first element in an array containing the magnitude spectrum is passed in as an argument.
 
 Hopefully this not only makes the library more efficient when computing large numbers of features, but also makes it more flexible because extraction functions can be combined arbitrarily (one can take the irregularility of the Mel Frequency Cepstral Coefficients for example).
 
-A complete list of features can be found by viewing the header files, or reading the doxygen documentation, available with this package, or at http://libxtract.sourceforge.net
+A complete list of features can be found by viewing the header files, or reading the doxygen documentation, available with this package.
 
-Dependencies
-------------
+## Dependencies
 
 To compile LibXtract, the following software is also needed:
 
-automake >= 1.6
-fftw3 (compiled with floating-point support)
+    automake >= 1.6
+    fftw3 (compiled with floating-point support)
 
 To build the PD external, the PD header 'm_pd.h' is required
 
-Installation
-------------
+## Installation
 
 Type:
 
-./configure --enable-pd_example --enable-fft
-make
-sudo make install
+    ./configure --enable-pd_example --enable-fft
+    make
+    sudo make install
 
 There following configure flags are optional:
 
---enable-pd_example (to build the PD example)
---enable-fft (to enable functions that require fftw3)
---enable-simpletest (to build the simpletest example)
+    --enable-pd_example (to build the PD example)
+    --enable-fft (to enable functions that require fftw3)
+    --enable-simpletest (to build the simpletest example)
 
 If you wish to build a Universal binary on OS X:
 
-CFLAGS="-isysroot /Developer/SDKs/MacOSX10.4u.sdk -Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc" \./configure --isable-dependency-tracking --your-options
+    CFLAGS="-isysroot /Developer/SDKs/MacOSX10.4u.sdk -Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc" \./configure --isable-dependency-tracking --your-options
 
-Building the MSP external
--------------------------
+## Building the MSP external
 
 Type:
 
-cd examples/MSP
-make
-sudo make install
+    cd examples/MSP
+    make
+    sudo make install
 
 To build for a specific architecture:
 
-make intel
-or
-make ppc
+    make intel
+    or
+    make ppc
 
-Building the Python bindings
-----------------------------
+## Building the Python bindings
 
 To build the python bindings, add to your configure flags:
 
---enable-swig --with-python
+    --enable-swig --with-python
 
 This requres additional dependencies to be resolved:
 
-swig >= 1.3
-python (with development files) >= 2.5
+    swig >= 1.3
+    python (with development files) >= 2.5
 
 It might work with earlier versions of Python, but this has not been tested.
 
 If you do not have the 'standard' version of Python on OS X, you might need to tell the configure script where the python library is e.g.:
 
-./configure --your-flags LDFLAGS="-L/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config/"
+    ./configure --your-flags LDFLAGS="-L/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config/"
 
 To find your Python library type:
 
@@ -81,34 +76,32 @@
     export PYTHONPATH=/usr/local/lib/python2.7/site-packages
 
 
-Building the Java bindings
---------------------------
+## Building the Java bindings
 
 To build the java bindings, add to your configure flags:
 
---enable-swig --with-java
+    --enable-swig --with-java
 
 This requres additional dependencies to be resolved:
 
-swig >= 1.3
-java (with development files) >= 2.0
+    swig >= 1.3
+    java (with development files) >= 2.0
 
 It might work with other versions of Java, but this has not been tested.
 
 On OS X, you will probably need to set your CLASSPATH environment variable before running ./configure
 
-export CLASSPATH=/System/Library/Frameworks/JavaVM.framework/Classes/classes.jar
+    export CLASSPATH=/System/Library/Frameworks/JavaVM.framework/Classes/classes.jar
 
 On OS X, you also probably need to tell the configure script where to find your Java (JNI) headers.
 
-./configure --flags  CFLAGS="-I/System/Library/Frameworks/JavaVM.framework/Headers"
+    ./configure --flags  CFLAGS="-I/System/Library/Frameworks/JavaVM.framework/Headers"
 
 To find out where your headers are:
 
-locate jni.h
+    locate jni.h
 
-Disclaimer
-----------
+## Disclaimer
  
 This program is free software; you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by