Mercurial > hg > vamp-plugin-sdk
diff README @ 44:ce61ad9b9159 1.0
...
author | cannam |
---|---|
date | Wed, 01 Nov 2006 17:48:21 +0000 |
parents | 1eb2419fc326 |
children | 2403ae53b8a5 |
line wrap: on
line diff
--- a/README Tue Oct 31 19:55:47 2006 +0000 +++ b/README Wed Nov 01 17:48:21 2006 +0000 @@ -1,10 +1,11 @@ Vamp ==== -http://www.sonicvisualiser.org/vamp.html An API for audio analysis and feature extraction plugins. + http://www.vamp-plugins.org/ + Vamp is an API for C and C++ plugins that process sampled audio data to produce descriptive output (measurements or semantic observations). @@ -44,9 +45,6 @@ * Vamp plugins do not have to be able to run in real time. -Vamp reuses some ideas from several existing systems, notably DSSI -(http://dssi.sourceforge.net) and FEAPI (http://feapi.sourceforge.net). - About this SDK ============== @@ -136,20 +134,29 @@ Installing the example plugins so that they can be found by other Vamp hosts depends on your platform: - * Windows: copy examples/vamp-example-plugins.dll and - examples/vamp-example-plugins.cat to C:\Program Files\Vamp Plugins + * Windows: copy the files + examples/vamp-example-plugins.dll + examples/vamp-example-plugins.cat + to + C:\Program Files\Vamp Plugins - * Linux: copy examples/vamp-example-plugins.so and - examples/vamp-example-plugins.cat to /usr/local/lib/vamp/ + * Linux: copy the files + examples/vamp-example-plugins.so + examples/vamp-example-plugins.cat + to + /usr/local/lib/vamp/ - * OS/X: copy examples/vamp-example-plugins.dylib and - examples/vamp-example-plugins.cat to /Library/Audio/Plug-Ins/Vamp + * OS/X: copy the files + examples/vamp-example-plugins.dylib + examples/vamp-example-plugins.cat + to + /Library/Audio/Plug-Ins/Vamp When building a plugin or host of your own using the SDK, you will -need to include the headers from the vamp-sdk directory. When linking -your plugin or host, we suggest statically linking the SDK code in -preference to distributing it alongside your plugin or host in DLL -form. An easy way to do this, if using a project-based build tool +need to include the headers from the vamp-sdk directory; then when +linking your plugin or host, we suggest statically linking the SDK +code (in preference to distributing it alongside your program in DLL +form). An easy way to do this, if using a project-based build tool such as Visual Studio or XCode, is simply to add the .cpp files in the vamp-sdk directory to your project. @@ -173,6 +180,15 @@ http://www.sonicvisualiser.org/ -Chris Cannam -Centre for Digital Music -Queen Mary, University of London +Authors +======= + +Vamp and the Vamp SDK were designed and made at the Centre for Digital +Music at Queen Mary, University of London. The SDK code was written +by Chris Cannam, copyright (c) 2005-2006 Chris Cannam. Mark Sandler +and Christian Landone provided ideas and direction, and Mark Levy, Dan +Stowell, Martin Gasser and Craig Sapp provided testing and other input +for the 1.0 API and SDK. The API reuses some ideas from several prior +plugin systems, notably DSSI (http://dssi.sourceforge.net) and FEAPI +(http://feapi.sourceforge.net). +