Version 2.10, 2020-05-18 (minor feature release)
* Add a method to PluginWrapper, the host-side base for adapters
like PluginInputDomainAdapter that modify the processing behaviour
of a plugin, that tells it to "disown" the wrapped plugin. The
former behaviour, and still the default, is for the wrapper to
take ownership of the wrapped plugin. The alternative behaviour
makes it easier to mix these classes with some modern C++ styles
that use managed pointers
Version 2.9, 2019-11-13 (maintenance release)
* Fix non-thread-safe behaviour in PluginAdapter. Plugins built
using the adapter classes in version 2.8 or earlier cannot safely
be used simultaneously across threads with other instances of
themselves or of other plugins in the same library (i.e. shared
object). Hosts have been required to provide synchronisation for
such cases. Version 2.9 introduces synchronisation in the plugin,
making this usage safe. Unfortunately this does not make host code
safe when using older plugin builds, as the problem and its fix
are in the plugin side of the SDK. Caution is still required, but
this fix does allow updated plugin builds to avoid problems with
some existing hosts
* Change required C++ language standard from C++98 to C++11. This
is because of the use of std::mutex in the above fix
Version 2.8, 2019-02-07 (maintenance and minor feature release)
* When running in a 32-bit process within 64-bit Windows (WoW64),
use the VAMP_PATH_32 environment variable instead of VAMP_PATH
(hosts running in this context already use "Program Files (x86)"
instead of Program Files)
* Fix off-by-one rounding errors in frame-to-ns conversions. Unlike
the other changes here which are invisible to plugin code, this
change can lead to different results in the lowest significant
figures from existing plugins if relinked against the newer code
* Fix path environment variable character encoding handling on
Windows
* Fix theoretical possibility of integer overflow in RealTime
constructor
* Fix use of undefined behaviour in PluginRateExtractor
Version 2.7.1, 2017-03-06 (maintenance release)
* Fix inclusion mechanism for FFTs which could cause a host
application to crash in certain circumstances due to
conflicting versions of C-linkage symbols
Version 2.7, 2017-02-24 (maintenance and minor feature release)
* Add ability to PluginLoader to list plugins only in (or not in)
certain library files
* Fix fixed-sample-rate output timestamps in printout from the
simple host, and add regression test script using test plugin
* Switch the convenience FFT interface for plugin usage from the
very slow reference implementation previously provided, to the
somewhat faster KissFFT
* Add a top-secret compiler flag to switch internal FFTs to single-
precision only
* Fix some small but long-standing memory leaks and minor bugs
Vamp is an audio processing plugin system for plugins that extract descriptive
information from audio typically referred to as audio analysis plugins or
audio feature extraction plugins.
Just like an audio effects plugin (such as a VST), a Vamp plugin is a binary
module that can be loaded up by a host application and fed audio data. However,
unlike an effects plugin, a Vamp plugin generates not more audio, but some sort
of symbolic information. Typical things that a Vamp plugin might calculate
include the locations of moments such as note onset times, visualisable
representations of the audio such as spectrograms, or curve data such as power
or fundamental frequency.
