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 ... 11 12 [13] 14 15 ... 19
181
Host Forum: Sonic Visualiser / Re: What about FLAC?
« on: March 30, 2009, 09:41:15 »
FLAC support is available in some builds of Sonic Visualiser; I'll try to look into extending support for it in future builds.

Whether FLAC support is available or not depends on whether it was included in the build of libsndfile that Sonic Visualiser was linked against (libsndfile is capable of reading FLAC files, but only if the FLAC libraries have been compiled in to it).

The Linux builds of Sonic Visualiser 1.5 _do_ have FLAC support included in their versions of libsndfile, and should be able to open .flac files directly (davidf, do you not find this to be the case?).

OS/X and Windows builds currently lack FLAC support.

Sonic Visualiser on OS/X is actually capable of opening any file supported by QuickTime, so users on OS/X might be able to get it to work by installing additional QuickTime codecs (I don't actually know offhand whether there is one for FLAC, but it seems likely).  One limitation here -- this is a bug in SV -- is that any file types supported by non-core QuickTime codecs will not be automatically enabled in the open-file dialog: you have to set the file dialog to "All files" rather than "Audio files" before it will let you select one of them.


Chris

182

I can't easily test the Mazurka plugins right now, as I'm using a 64-bit distro at the moment and they only come in 32-bit builds.

If you run sonic-visualiser from a command line, you might see some sort of useful error message (somewhere near the start of any debug or logging information it prints out).  For example, if I install the 32-bit Mazurka plugins .so and run my 64-bit SV build, it says:

WARNING: FeatureExtractionPluginFactory::getPluginIdentifiers: Failed to load library /usr/local/lib/vamp/mazurka-plugins.so: /usr/local/lib/vamp/mazurka-plugins.so: wrong ELF class: ELFCLASS32

If you aren't getting any useful information out of Sonic Visualiser, you could try running vamp-simple-host instead (with the -l option to list installed plugins).


Chris

183
Plugin Development / Re: coding...
« on: March 24, 2009, 18:08:29 »
When you say it isn't running in SV, what do you mean? It doesn't appear in the menus, it appears in the menus but no data is generated and displayed, or it fails in some other way (e.g. crashes)?

You might find it simpler to test in vamp-simple-host, which prints out its results directly to the command prompt -- at least that way you would see immediately whether there are any results or not, whereas in SV you could theoretically have results that simply aren't visible because their timestamps are wrong, or some such.

I can't really comment on the usage of aubio, but I would wonder what m_currentOnset is as it doesn't appear to be set anywhere.

To remove the example plugins, it should only be necessary to remove the references to them from plugins.cpp (or whatever file your library main entry point is defined in -- it's plugins.cpp in the example set).  There are three references to each plugin (the #include for its header, the static adapter declaration, and the return value from vampGetPluginDescriptor), and you would need to remove them all.  Ensure that your vampGetPluginDescriptor function returns your own plugin's adapter when it is called with index value of 0, and returns 0 for any other index value.


Chris

184
Plugin and Host Announcements / Sonic Annotator v0.2 released
« on: March 20, 2009, 20:20:09 »
Sonic Annotator is a utility program for batch feature extraction from
audio files.  It runs Vamp audio analysis plugins with specified
parameters on audio files, and writes the result features in a
selection of formats, in particular as RDF using the Audio Features
and Event ontologies.

Version 0.2 is now available, offering more stable and predictable
results than the earlier 0.1.

For more details and for downloads, please see

 http://www.omras2.org/SonicAnnotator

Sonic Annotator was developed at the Centre for Digital Music, Queen
Mary, University of London.  It was funded by the EPSRC through the
OMRAS2 project and is Free Software published under the GNU General
Public License.


Chris

185
Plugin Development / Re: dll not recognize
« on: March 20, 2009, 16:31:46 »
I would like to ask if you have codes for QM Plugins.

I'm afraid the source code for the QM plugins is not published (a question of university policy).  What is it that you want to know?  If it's purely a question of technique, it might be possible to answer it without reference to the code.


Chris

186
Announcing v0.1 of the Vamp plugin tester, a simple program that loads and tests Vamp plugins for various common failure cases.  It can't check whether you're getting the right results, but it can help you write more resilient and better-behaved plugins.

Source code:
http://downloads.sourceforge.net/vamp/vamp-plugin-tester-0.1.tar.bz2

OS/X universal binary:
http://downloads.sourceforge.net/vamp/vamp-plugin-tester-0.1-osx-universal.tar.bz2

Windows binary:
http://downloads.sourceforge.net/vamp/vamp-plugin-tester-0.1-win32.zip

There is some documentation in the README file, but the short version is that you run it at a command prompt with the library name and plugin name, colon-separated, as an argument:

$ ./vamp-plugin-tester vamp-example-plugins:spectralcentroid

... and see what it has to say about your plugins.  It may also crash; if it crashes in the middle of one of its tests, that usually means that your plugin has crashed when faced with some unexpected input (run it in a debugger, or a memory checking utility if you have one, to find out where).

This tester does report some genuine bugs when run against several of the existing Vamp plugins.  I'll be aiming to make some fixes where I'm able.

This is only the first release, so it's quite likely that the tester hasn't been tested enough itself yet.  Report any problems here, please!


Chris

187
My memory is short!  As Pablo points out in another post on this forum, you can get these errors even if the Vamp SDK is installed -- if you have version 1.x of the SDK, because Sonic Visualiser now requires version 2.0.


Chris

188
Ah, crap.

Add

Code: [Select]
LIBS += -lasound

to the file sv.prf, and then make again.


Chris

189
Sonic Visualiser is an application for inspecting and analysing the
contents of music audio files. It combines powerful waveform and
spectral visualisation tools with automated feature extraction plugins
and annotation capabilities.

Version 1.5 of Sonic Visualiser is now available.

  http://www.sonicvisualiser.org/

This release contains a small number of new features and a larger
number of bug fixes over the previous 1.4 release.  For more details,
please read the release notes at:

  https://sourceforge.net/project/shownotes.php?release_id=668854

Sonic Visualiser contains advanced waveform and spectrogram viewers,
as well as editors for many sorts of audio annotations. Besides
visualisation, it can make and play selections based on the locations
of automatically detected features, seamlessly loop playback of single
or multiple noncontiguous regions, synthesise annotations for
playback, slow down playback while retaining display synchronisation,
and show the ongoing alignment in time between multiple recordings of
a piece with different timings.

Sonic Visualiser supports the Vamp plugin API for plugins that extract
descriptive or analytical data from audio.  Vamp plugins for onset,
pitch and note detection, tempo tracking, chromagram analysis,
constant-Q spectrogram, spectral centroid, power curve, key
estimation, tonal change detection, harmonic spectrogram, structural
segmentation, timbral similarity, audio alignment calculation and a
large number of low-level spectral features are available.  There is
also a comprehensive SDK for use by developers of Vamp plugins and
hosts.  For more information about Vamp plugins, please see:

  http://www.vamp-plugins.org/

Sonic Visualiser was developed at the Centre for Digital Music, Queen
Mary, University of London:

  http://www.elec.qmul.ac.uk/digitalmusic/

Ongoing work on Sonic Visualiser and audio feature representation in
the semantic web is carried out as part of the OMRAS2 project funded
by the EPSRC.  See

  http://omras2.org/

for more information.

Sonic Visualiser is Free Software distributed under the GNU General
Public License.  The 1.5 release is available now in source code form
or as binaries for Linux, OS/X, and Windows.


Chris

190
You know, I don't think there is a way to go directly to a particular time in SV.  (Although I'm a bit wary of saying this, as SV is now big enough that I can't always remember everything that's in it myself.)

The quickest way to find a particular point in a layer is to make the layer active, then open the layer data editor (Layer -> Edit Layer Data) and scroll to the point you want.  The main pane will then scroll with you.


Chris

191
Plugin Development / Re: dll not recognize
« on: March 17, 2009, 13:27:49 »
Can you try it with the Vamp simple host (vamp-simple-host) in the SDK?  (There is a binary version of the host available in the SDK downloads, if you don't have or want to build one.)

If your Vamp plugin DLL is in the Vamp path, then just running "vamp-simple-host -l" (that's a lower-case "l", for "list") should list its name and description (among any other plugins that are also installed).


Chris

192
Getting and Using Vamp Plugins / Re: reading mp3 files?
« on: March 17, 2009, 13:25:20 »
Sorry, what output does vamp-simple-host give with the QM tempo tracker, then?  I have tried it with your example file, and I see a list of 584 beat locations printed to stdout (one per line, just the beat time followed by a colon because there is no other data associated with each beat).


Chris

193
Getting and Using Vamp Plugins / Re: reading mp3 files?
« on: March 12, 2009, 12:52:09 »
Ah.  I think the problem here is kind of simple -- the FixedTempoEstimator, being a stupid soul, only looks at the start of the audio file and assumes that the remainder is the same in terms of tempo.  However, this file (not unusually) has silence at the start, so it's quite lost.

The host would have to feed it a different section of the file in order to get any result -- and this is not something vamp-simple-host can do, though you can do it in Sonic Visualiser with a selection and the "restrict to selection extents" option in the plugin parameters dialog.

This shouldn't be a problem for other plugins, though -- for example, qm-vamp-plugins.so:qm-tempotracker:tempo (as argument to vamp-simple-host) should give you a list of tempo estimates, with a new value each time the tempo tracker thinks the tempo has changed.

It may be worth noting that none of the published tempo trackers is likely to work very well with this particular recording.  (Nice recording, by the way.)


Chris

194
Getting and Using Vamp Plugins / Re: reading mp3 files?
« on: March 12, 2009, 11:38:07 »
Thanks.  That is rather odd.  Any chance you could attach one of your test WAV files, or email it to me at cannam (at) all-day-breakfast (dot) com, so I can see whether I can reproduce the problem?

What platform is this, by the way?


Chris

195
Getting and Using Vamp Plugins / Re: reading mp3 files?
« on: March 12, 2009, 10:29:22 »
it happens with vamp-simple-host as well.. :/

Can you describe exactly what you are running and what the output is, please?  Perhaps cut-and-paste a terminal session into a post here, including the full vamp-simple-host command line and at least some representative part of its output.

Thanks,


Chris

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