Recent Posts

Pages: [1] 2 3 ... 10
3
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.
4
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.so, cqvamp.n3 and cqvamp.cat 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 cqvamp.so 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.
5
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".


Chris
6
Host Forum: Sonic Visualiser / Re: Help test the first Sonic Visualiser v3.0 beta
« Last post by cannam on January 17, 2017, 09:33:25 »
There's a second beta up there now. You can see what's changed here: https://thebreakfastpost.com/2017/01/17/a-second-beta-of-sonic-visualiser-v3-0/

Files in the same place: https://code.soundsoftware.ac.uk/projects/sonic-visualiser/files


Chris
7
I'm working on a freeware light control program called xLights.  Last year one of our developers used your plugin host sdk to give our program features to analyze audio for the purpose of creating timing marks aligned with beats or bars or the other types of plugins you provide.  Prior to that our users always used Audacity to create timing marks and then we had the capability to import the text file exported from Audacity.

I didn't do that initial coding but I'm converting our application to 64-bit.  I got everything running but a user noticed the qm vamp plugins weren't showing up as an option for creating timing tracks.  I inspected the DLL header with dumpbin and see it's 32 bit so I assume that's the reason.  I've searched a lot and can't find a 64-bit version of the DLL for Windows anywhere.  Has it really never been created?  Our program is multi-platform so we already have all this stuff working in 64-bit on MacOS and Linux.  I thought I could just build it myself but the source code appears to list several .lib files in the build directory so I was anticipating problems with those being 32-bit.

Thanks,
Gil
8
Host Forum: Sonic Visualiser / Help test the first Sonic Visualiser v3.0 beta
« Last post by cannam on January 11, 2017, 10:48:24 »
Hello all -- we have a new (first) beta-release of what will be Sonic Visualiser v3.0, now available for download. I'd be grateful if some intrepid people would like to try it out and report what they find.

I wrote a post with more info here: https://thebreakfastpost.com/2017/01/11/help-test-the-sonic-visualiser-v3-0-beta/

And you can download binary packages (Windows and Mac so far, Linux I'm working on at the mo) plus source from the page at https://code.soundsoftware.ac.uk/projects/sonic-visualiser/files

Chris
9
Plugin Development / Re: Help to get exact bpm count and beatgrid
« Last post by cannam on September 30, 2016, 17:12:35 »
And if you use the vamp-simple-host with the vamp-example-plugins:fixedtempo plugin, does that give you the same 51.4 result as you had with your code?

I can't see anything obviously wrong with your code snippet, assuming that the audio is single channel throughout.

The QM tempo tracker works slightly differently -- it emits a new tempo every time its sense of the underlying tempo changes. This means in theory it works for tracks which vary in tempo as well, but it can mean you sometimes get a series of very close estimates which would be more useful if they had been merged together. To get a single tempo per track, one might typically pick the estimate that spans the greatest time range within the results.

10
Plugin Development / Re: Help to get exact bpm count and beatgrid
« Last post by djjoy on September 29, 2016, 10:06:18 »
Some help or comments with this question?

Best Regards,

DJ Joy
Pages: [1] 2 3 ... 10