Recent Posts

Pages: [1] 2 3 ... 10
Host Forum: Sonic Visualiser / Re: Signal generator plug-in
« Last post by aconto on April 12, 2017, 09:39:51 »
No suggestions ? I'd like to hear the melody extracted with Melodia, and possibly export the output in order to feed some plug-in, maybe into another workstation. So I'd like to export audio or midi data, or to figure out how to convert the text file which comes out from the export menu into an audio file.
Host Forum: Sonic Visualiser / Signal generator plug-in
« Last post by aconto on April 10, 2017, 10:49:40 »
Hello everybody. I'm looking for a signal generator for hearing some features of melody extraction such as Melodia. Anyone could suggest me something ?
Host Forum: Sonic Visualiser / Re: Sonic Visualiser 3.0 released!
« Last post by cannam on March 07, 2017, 14:33:01 »
And predictably enough, within a week a 3.0.1 is necessary!

Downloads from the usual place:

The update fixes two crashes on Windows and updates the MIDI device driver layer on all platforms.

Plugin Development / Vamp Plugin SDK v2.7 available!
« Last post by cannam on March 03, 2017, 11:47:18 »
Version 2.6 of the Vamp plugin SDK is now available.

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

Version 2.7 is a bugfix and minor enhancement release. For more details, see the changelog at

Host Forum: Sonic Visualiser / Sonic Visualiser 3.0 released!
« Last post by cannam on March 03, 2017, 11:45:05 »
Sonic Visualiser 3.0 is out!

What's new in this release:

Getting and Using Vamp Plugins / Re: Vamp plugins not loading in Audacity
« Last post by cannam on January 19, 2017, 10:21:32 »
Hi there -- I believe this plugin doesn't show up because Audacity has no way to display any of its outputs. Audacity only shows those plugins that have at least one output that can be displayed on a label track -- it can't display grid output from Vamp plugins, and all of the CQ outputs are grids.

That is the way it used to work anyway, I haven't checked the code very recently.
Getting and Using Vamp Plugins / Vamp plugins not loading in Audacity
« Last post by meowsqueak on January 19, 2017, 01:34:36 »
I am trying to use the CQ Vamp plugin with Audacity, however I am not able to get to a point where Audacity shows the plugin in the UI.

I am using Ubuntu 14.04.5 with Audacity 2.1.2 (fresh install from PPA). I have tried both the pre-compiled 1.1 (64bit) from the website, and compiling it myself. I have placed the, cqvamp.n3 and file in ~/.vamp. I have also tried ~/vamp and /usr/local/Iib/vamp. I have also tried setting VAMP_PATH.

In all cases, Audacity does not show the plugin in the Add / Remove Plugins dialog. However when opening audacity with strace -eopen I see that the file is opened three times when the dialog is opened, so there's some detection of the .so file. Unfortunately Audacity shows no relevant messages in dialogs, or on stderr or stdout, so I'm at a loss to know why it isn't recognising the plugin beyond opening the .so.
It's true that there has never been a 64-bit Windows build of the QM Vamp Plugins. Making one is a priority for us once SV v3.0 is out.

There are various reasons why few Vamp plugins are available in 64-bit builds for Windows.

The proximate reason is that none of the most widely-used Vamp hosts (Sonic Visualiser, Sonic Annotator, Audacity) exists in a 64-bit Windows version. Since 32-bit hosts can't load 64-bit plugins, there's no pressing reason to produce 64-bit plugins. This will change with Sonic Visualiser v3.0, which for the first time will have a 64-bit Windows build, as well as an adapter that allows it to load 32-bit plugins (out-of-process). So SV v3.0 can continue to use the 32-bit Windows plugins, but also provides more of an incentive to produce 64-bit ones.

In a way this can be attributed to Microsoft's success at providing excellent 32-bit compatibility in 64-bit Windows. On both Linux and OSX we have already had to face the issue of requiring all existing plugins to be rebuilt in 64-bit versions because the underlying platform standard changed. This has never been forced on anyone in the Windows world.

Finally there are various practical reasons, such as that many of the 32-bit Windows plugin builds have been produced using the MinGW compiler which until recently was not readily available in a stable 64-bit version. (I think until fairly recently the 64-bit Visual C++ compiler wasn't included in the free version of Visual Studio either?) So it's not just a question of using the same native platform compiler on the newer platform and getting a new build for the new architecture, as it has been on both Linux and OSX.

The QM plugin set is relatively tricky to rebuild as well, because of its use of LAPACK and BLAS.

Anyway, that's the explanation -- the short answer is that a 64-bit version is "planned soon".

Pages: [1] 2 3 ... 10