Version 1.0 of the Vamp Test Plugin is now available.

This, the world's least interesting Vamp plugin, is the equivalent of a TV test signal: it produces a set of very simple static outputs intended to help the authors of Vamp hosts check that they are handling plugin output sample types correctly.

See https://code.soundsoftware.ac.uk/projects/vamp-test-plugin for more information.

If you are the author of a Vamp host, you might find it useful.


Chris

Sonic Visualiser is an application for inspecting and analysing the
contents of music audio files. It combines powerful waveform and
spectral visualisation tools with automated feature extraction plugins
and annotation capabilities.

Version 2.1 of Sonic Visualiser is now available. This is a bugfix release.

 http://www.sonicvisualiser.org/

For more information, please read the change log at:

 http://code.soundsoftware.ac.uk/projects/sonic-visualiser/repository/entry/CHANGELOG


Chris

Sonic Annotator is a utility program for batch feature extraction from
audio files.  It runs Vamp audio analysis plugins with specified
parameters on audio files, and writes the result features in a
selection of formats, in particular as RDF using the Audio Features
and Event ontologies, or as simple CSV files.

Version 1.0 is now available. This is a bugfix release.
For more details, see the changelog at

http://code.soundsoftware.ac.uk/projects/sonic-annotator/repository/entry/CHANGELOG

For more information about Sonic Annotator and for downloads,
please see

 http://www.omras2.org/SonicAnnotator


Chris

Version 2.5 of the Vamp plugin SDK is now available.

   http://www.vamp-plugins.org/

Vamp is a plugin API for audio analysis and feature extraction plugins written in C or C++.  Its SDK features an easy-to-use set of C++ classes for plugin and host developers, a reference host implementation, example plugins, and documentation.  It is supported across Linux, OS/X, and Windows.

A documentation guide to writing plugins using the Vamp SDK can be found at http://www.vamp-plugins.org/guide.pdf.

Version 2.5 is a bugfix release. For more details, see the changelog at

http://code.soundsoftware.ac.uk/projects/vamp-plugin-sdk/repository/entry/CHANGELOG

The most significant fix in this release is in the host SDK, and affects the handling of output timestamps in the (little used) FixedSampleRate output type.


Chris

Hi Justin -- is it possible it depends on a version of e.g. the VC++ runtime which is not installed on these machines?

Can you try the DLL in Dependency Walker (http://www.dependencywalker.com/) on one of the offending machines?

Chris

I just posted this analysis of some of the basic numerical data from the Sonic Visualiser user survey (the one that SV asks whether you'd like to complete, after you have run the program a few times -- you may be familiar with it):

http://thebreakfastpost.com/2013/04/26/looking-at-the-sonic-visualiser-user-survey-part-1/

The survey's been running for some time, and I've looked at responses in the past but have never previously published any data from it. Might be of interest to some!


Chris

SV doesn't actually have any means of downsampling or decimating audio on request, I'm afraid -- it would be necessary to downsample the file outside of SV before loading it.

It would be possible for a Vamp plugin to offer this as an option, but I'm not sure whether any existing one does.


Chris

Hi Mark -- it looks like you can find all the .h files http://sv.mazurka.org.uk/include/ (go there in a browser, and you'll see a file listing) and the .cpp files at http://sv.mazurka.org.uk/src/. Might not be the most elegant way to download, but it does seem to be possible.


Chris

Hi -- all the Windows builds of plugins linked at http://vamp-plugins.org/download.html are 32-bit versions, but they will work fine in a 64-bit version of Windows so long as the host is also 32-bit.

(64-bit Windows is happy to run 32-bit binaries, but the host and plugin must match -- in this case both must be 32-bit.)

The installation folders are listed at the bottom of http://vamp-plugins.org/download.html. Note that on a 64-bit Windows, you must install 32-bit plugins in

Code:

C:\Program Files (x86)\Vamp Plugins

or your language's localised equivalent -- with the (x86) suffix -- and not just in Program Files.


Chris

jVamp is a JNI (Java Native Interface) library that permits Java applications to load and use Vamp audio analysis plugins.

jVamp is intended for application developers who are interested in adding capabilities to Java applications or a Java environment; it's not currently something that an end-user would normally wish to install. But if you are working in Java, you might well find it interesting.

Note that jVamp is intended to be compatible with the Android NDK as well as desktop Java, though it hasn't been tested there (and existing binary distributions of plugins do not usually include ARM builds).

See http://code.soundsoftware.ac.uk/projects/jvamp for more information.

Chris

Version 2.4 of the Vamp plugin SDK is now available.

   http://www.vamp-plugins.org/

Vamp is a plugin API for audio analysis and feature extraction plugins written in C or C++.  Its SDK features an easy-to-use set of C++ classes for plugin and host developers, a reference host implementation, example plugins, and documentation.  It is supported across Linux, OS/X, and Windows.

A documentation guide to writing plugins using the Vamp SDK can be found at http://www.vamp-plugins.org/guide.pdf.

Version 2.4 is a maintenance and bugfix release. The main addition is a simple FFT implementation for plugins to use. For more details, see the changelog at

http://code.soundsoftware.ac.uk/projects/vamp-plugin-sdk/repository/entry/CHANGELOG


Chris

Sonic Annotator is a utility program for batch feature extraction from
audio files.  It runs Vamp audio analysis plugins with specified
parameters on audio files, and writes the result features in a
selection of formats, in particular as RDF using the Audio Features
and Event ontologies, or as simple CSV files.

Version 0.7 is now available.

For more details and for downloads, please see

 http://www.omras2.org/SonicAnnotator


Chris

Sonic Visualiser is an application for inspecting and analysing the
contents of music audio files. It combines powerful waveform and
spectral visualisation tools with automated feature extraction plugins
and annotation capabilities.

Version 2.0 of Sonic Visualiser is now available.

 http://www.sonicvisualiser.org/

This is a maintenance release -- the major version-number bump
arrives simply because the previous release was 1.9 and 2.0 is the
obvious next number!

This release adds a fullscreen mode and restores the ability to
replace the main audio model (leaving the rest of the session intact)
which was lost in the session-templates feature work for 1.9.

Note that the default OS/X build of Sonic Visualiser is now a
64-bit one. This means it requires Vamp plugins with 64-bit
support (either 64-bit plugins or at least plugins with a 64-bit
Intel version in their universal wrapper). Many of the commonly
used Vamp plugins have had 64-bit distribution for some time,
but not all of them have -- a couple still need to be updated.

For more information, please read the change log at:

 http://code.soundsoftware.ac.uk/projects/sonic-visualiser/repository/entry/CHANGELOG


Chris

But when trying this with SV, the plugin runs (i.e. there's no initialisation error), regardless of what blockSize I choose in the graphical interface.

Ah, I see what's happening here... SV is being too clever for its own good.

What's happening is that when initialise() fails, SV then quietly reinitialises the plugin using its preferred settings and runs it with those instead.

That is almost certainly a bad idea. I'm struggling to think of any situation in which it would be a particularly wise thing to do. There might be one, though, and I ought to check the version control logs before I intemperately rip out the code for the forthcoming release!


Chris

Nice. I've had a look - any specific reason for using Cross's implementation?

Just that it is very, very simple -- it's the simplest implementation I know for the most basic level of support.

Users who really care about it (either because they want the fastest or because they need some specific functionality) will probably want to do something else regardless of whether the provided version is from Cross, Ooura, or KissFFT. This way at least it doesn't provide a significant overhead in library complexity.

It's slow, compared to the fastest implementations, but it's not so slow as to be a huge overhead in most real-world methods. It's good enough to be a sensible way to get your algorithm started.


Chris