Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - cannam

Pages: 1 ... 12 13 [14] 15 16 ... 19
196
Getting and Using Vamp Plugins / Re: 0 tempo?
« on: March 11, 2009, 17:25:12 »
I tried running the example plugins and several of the other downloadable plugins' tempo extractors but I keep getting 0 results. any ideas? I'm running them on wavs, and can see it being processed (i.e., i see a loooooong list of timestamps) but everything is 0. :(

Does this happen if you run them with vamp-simple-host, or only with the code that you're working on?

It certainly doesn't sound (on first reading) like a problem I know about or would expect to see.


Chris

197
../plugin/RealTimePluginInstance.h:24:37: error: vamp-hostsdk/PluginBase.h: No such file or directory
../plugin/RealTimePluginInstance.h:25:35: error: vamp-hostsdk/RealTime.h: No such file or directory

You need to install the Vamp plugin SDK, somewhere such that Sonic Visualiser can find its headers.  (The default install target of /usr/local should be OK in most situations.)


Chris

198
Getting and Using Vamp Plugins / Re: reading mp3 files?
« on: March 11, 2009, 14:30:21 »

Nothing about Vamp plugins themselves has any bearing on the file types your host can support -- you just have to be able to decode the audio file and pass the decoded data to the plugin.  The plugin neither knows nor cares what file type the data came from, and it certainly cannot decode mp3 or any other compressed format itself.

So, I'm afraid, your question really comes down to "how do I read and decode an mp3 file in my program?"

I imagine your choice really is to use an mp3 decoder library such as madlib (if license and so on permit), or to run the plugin host in some sort of scripting environment in which the mp3 file is decoded by a separate decoder program run in a script or batch process (e.g. mpg321) and the resulting wav file is fed to the host.

If it's any help, Sonic Annotator (http://omras2.org/SonicAnnotator) can run Vamp plugins on mp3 files, but it pulls in an awful lot of code to do so because it pulls in (GPL-licensed) libraries from Sonic Visualiser in order to save development time.  I wouldn't necessarily advise that approach if all you want is to read an mp3, but it might be worth taking a look at it.


Chris

199
You probably just need to put

Code: [Select]
#include <stdlib.h>

at the top of the source file.


Chris

200
I've recently posted a video example of audio alignment using Sonic Visualiser and the MATCH Vamp plugin (which SV will use to do automatic alignment, if it is installed):

    http://vimeo.com/3310893

At the moment it lacks any sort of voiceover or explanatory subtitles -- I may well go back and add some, but this was my first attempt at videoing anything on that particular platform so it's pretty simplistic.

There is also a written tutorial on this subject, linked from the documentation page:

    http://sonicvisualiser.org/documentation.html


Chris

201

I see the EPSRC website (one of the funding bodies responsible for Sonic Visualiser) has a new press release about the program, in connection with their recent Pioneers exhibition showcasing a number of EPSRC-funded projects.  It's a bit breathless, as press releases often are, but here we go:

    http://www.epsrc.ac.uk/PressReleases/digitalmusic.htm


Chris

202
Hm, these are not supposed to have changed.  Numpad-Enter, or semicolon.

The forthcoming 1.5 release (first test builds available now in http://sonicvisualiser.org/pre/) will also allow you to "tap" using any attached MIDI device -- a fairly commonly requested feature.


Chris

203
Could you give me the steps on how to create it (e.g. sample.c compiled to sample.o)

Well, to be honest it should be enough to just add the files to your project.  If they are present in the project file listing, that should be enough...  If you re-build the project (i.e. build from clean), do the files you imported from aubio (e.g. sample.c) appear in the log of files being compiled?  I don't have Visual Studio to hand (running Linux at the moment) but I'm pretty sure it tells you what files it's compiling -- I can't remember whether it also tells you what files it is linking though.


Chris

204
Sorry to take so long to respond to this one.

The problem is simple enough -- the qm-vamp-plugins.so has been linked against a libc version which has pulled in specific versioned symbols, resulting in a binary that isn't backward compatible against older versions of libc.  I'm pretty sure that there is nothing you can do about this yourselves other than upgrading your version of libc.

I don't know whether it's possible for me to solve this by building in a backward compatible way on a system whose core glibc version is 2.4 -- I will try to investigate this in time for the next point release.  Apologies for the troubles.


Chris

209
--Then, i copied some codes from Pitchdetection.cpp file of Aubio. Then I added the aubio library files and put it on a folder called aubio.
--Then compile it and got that errors.

You're quite sure that the Aubio library files were included in the build and link, at this point?

The most obvious reason why you would have symbols such as _del_fvec undefined in the link would be simply that the file that defines them (e.g. sample.c, in this case) was not compiled and/or linked with the build.  That is, either sample.c was not compiled into sample.o, or sample.o was not linked into your dll.

I know I may be stating the obvious here, but it's worth checking.

Incidentally, I'm going to move some of these threads into another forum -- they should really be in the Plugin Development forum rather than the one about using plugins.


Chris

210

That's strange, these are plain C functions that are defined in the aubio source files (del_fvec is defined in sample.c, declared in sample.h, etc).

I can't see, at first reading, what could cause this.  Hmm.


Chris

Pages: 1 ... 12 13 [14] 15 16 ... 19