Added tag vamp-plugin-sdk-v2.10 for changeset fa74c473e48c
Build file for 2.10 package
Update version number and CHANGELOG
Add ability to disown a wrapped plugin - making it possible to use the adapters in some situations involving managed pointers that didn't work previously
Update library URI so as not to be document-local
Merge
Show error code if library can't be loaded
Added tag vamp-plugin-sdk-v2.9 for changeset a7e6d747fd3f
Date
Merge from branch c++11-mutex
Use the tag (which doesn't exist yet)
Update Docker build
Flag for C++ standard
This will be v2.9
A better way, I think, of handling static initialisation order
Switch from C++98 to C++11
Avoid simple static allocation of mutex, as it could lead to mutex being destroyed before last adapter that needs to use it (since adapters are usually also static)
Don't even ask to unload library if another plugin is loaded from it
Toward making PluginAdapterBase::Impl actually thread-safe!
Ensure VAMPSDK_DIR is defined before being used
Looks like choco currently has a broken version of wget; use an older one
Added tag vamp-plugin-sdk-v2.8 for changeset be688783aa37
Correct release date
More build files
Tiny whitespace change
Update versions throughout to 2.8
Update CHANGELOG (release date is provisional)
Header for getenv
Use VAMP_PATH_32 environment variable instead of VAMP_PATH, when running in a 32-bit process within 64-bit Windows (WoW64)
Wide-char environment variable lookup
Doc note
Merge from branch vamp-kiss-naming
Libsndfile path
Another attempt to run the installer. Not hopeful about this one.
Have a go at bringing in libsndfile
Bit confused by this now
Ah, duplicate key problem - try this arrangement instead
Experiment with AppVeyor build
Avoid buffer underflow
Extensively rename things in the KissFFT headers to use a Vamp prefix. The motivation is not to change anything about the Vamp SDK library builds, but to avoid confusion in case any other code (for example that pulls in the Vamp SDK as part of a wider project definition) accidentally includes these headers instead of, or as well as, some other copy of KissFFT.
The PluginRateExtractor hack was exploiting undefined behaviour. Let's just give in and make that API official
Rework canonicalisation so as to avoid theoretical possibility of integer overflow. (This is unit tested in svcore, not here - tests pass)
Update before install; seems to be necessary (based on other projects) to avoid recent Ruby-related error
More (off-by-default) debug output
Added tag vamp-plugin-sdk-v2.7.1 for changeset 2dbb3f920abc
Update CHANGELOG and versions
Added tag vamp-plugin-sdk-v2.7.1 for changeset 25e023bad200
Choose another method (which should actually work) to override linkage for KissFFT
Added tag vamp-plugin-sdk-v2.7 for changeset 124752918a1b
1 2 3 ... 11 Next ยป (1-50/542) Per page: 25, 50, 100
Also available in: Atom