Recent Posts

Pages: 1 ... 5 6 [7] 8 9 10
61
Plugin and Host Announcements / Silvet Note Transcription plugin v1.1 released
« Last post by cannam on September 09, 2015, 12:24:17 »
Silvet is a Vamp plugin for note transcription in polyphonic music.

   http://code.soundsoftware.ac.uk/projects/silvet

Silvet listens to audio recordings of music and tries to work out what notes are being played. It uses the method described in "A Shift-Invariant Latent Variable Model for Automatic Music Transcription" by Emmanouil Benetos and Simon Dixon (Computer Music Journal, 2012).

The plugin is provided with source code under the GNU General Public License, and with binaries for Windows, OS/X and Linux.

This new v1.1 release replaces the "draft" mode with a much faster "live" mode, adds a number of new outputs (note onsets, offsets, pitch activation matrix, chromagram), and adjusts some internal processing parameters to improve performance in test datasets.
62
Plugin and Host Announcements / Constant-Q library and Vamp plugin, v1.1
« Last post by cannam on September 09, 2015, 12:14:37 »
A new release of this Constant-Q transform library and Vamp plugin is now available:

  https://code.soundsoftware.ac.uk/projects/constant-q-cpp

Most of the changes concern code organisation, for example giving the Chromagram class its own formal API in the underlying library. However, there is also a fix to label ordering in the Vamp plugin.
63
Plugin Development / Vamp Plugin Tester v1.1 released
« Last post by cannam on September 09, 2015, 11:32:04 »
Version 1.1 of the Vamp plugin tester, a program that loads and tests Vamp plugins for various common failure cases, is now available.

Info and downloads:

https://code.soundsoftware.ac.uk/projects/vamp-plugin-tester

Change log:

https://code.soundsoftware.ac.uk/projects/vamp-plugin-tester/repository/entry/CHANGELOG

The tester can't check whether you're getting the right results, but it can help you write more resilient and better-behaved plugins. It's a really good idea to run the tester on any new plugin before you release it.

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.

If it crashes in the middle of one of its tests, that probably 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.

Chris
64
Host Development / Vamp Test Plugin v1.1 released
« Last post by cannam on September 09, 2015, 11:24:35 »
Version 1.1 of Vamp Test Plugin, the world's least interesting Vamp plugin, is now available.

Vamp Test Plugin is the equivalent of a TV test signal: it produces a set of very simple static outputs intended to help the authors of Vamp hosts check that they are handling plugin output sample types correctly. This release adds an output which is calculated from the input (to facilitate testing that input blocks are provided correctly) and a frequency-domain version of the same.

See https://code.soundsoftware.ac.uk/projects/vamp-test-plugin for more information.

If you are the author of a Vamp host, you might find it useful.

Chris
65
Host Development / jVamp v1.3 released
« Last post by cannam on September 09, 2015, 11:12:55 »
Announcing v1.3 of jVamp, a Java/JNI interface allowing the use of native-code Vamp plugins from host applications written in Java or other JVM languages.

This release simplifies the API, removing an unnecessary dispose() call and eliminating a class of native-heap memory leak.

See https://code.soundsoftware.ac.uk/projects/jvamp for more details and downloads.

Chris
66
I think I agree with your suppositions.

Tempo, beat, and onset estimators will be seriously affected by crackles (or jumps!) in the source audio. Pitch analysis could be affected by play speed, wow and flutter, and potentially also sources of hum. The dynamic range of analogue source material is likely to be different from that of digital recordings, and noise such as tracking errors from loud passages in vinyl recordings may colour analysis of pitch, timbre, and dynamics.

Frequency bandwidth and EQ will also be narrower, but many methods consider only a limited bandwidth anyway (partly because it depends so much on the reproduction).

Tape hiss is unlikely to affect anything very much unless possibly it's loud enough to disturb methods that have explicit silence thresholds. (Many methods will filter constant noise, either explicitly, or implicitly through analysing spectral change.)
67
Plugin Development / Re: simple feature request: "copy drawn beats to aligned audio"
« Last post by cannam on September 09, 2015, 10:46:35 »
If you have two audio files loaded in separate panes, and they are aligned, then you should be able to take annotations made against one of them and copy/paste them onto the other one and SV will adjust their timings to match the alignment. This sounds like what you are asking for?

For example:

 1. Load an audio file into a new session
 2. Use "Import More Audio" to load another (presumably of the same work)
 3. Switch on the Align control
 4. Make sure the first pane is active, and tap some instants into it (e.g. with the ";" key)
 5. Select all (e.g. Ctrl+A or Cmd+A) and copy to clipboard (Ctrl+C or Cmd+C)
 6. Make the second pane active (by clicking on it)
 7. Paste (Ctrl+V or Cmd+V)

SV should pop up a dialog saying "The instants you are pasting came from a layer with different source material from this one.  Do you want to re-align them in time, to match the source material for this layer?" Say yes to this, and the instants should be pasted into the second pane with appropriate alignment.
68
Hello,

I'd like to suggest a feature.

After one has drawn the bars or beats in a track by hand and has aligned two or more tracks, it would be nice, if SV would just copy the bars/beats to the other tracks.

Since it is able to jump to the same "note" in different tracks per the alignment tool, it should be possible for it to make references and know how to copy the beats accordingly or am I thinking to simple here?

Another thing:
It is also possible to create a line that shows the bpm when one points the mouse on it, how does one make the bpm visible as numbers and not by first pointing the mouse on it. I also miss a guide that brings me to this result: http://www.charm.rhul.ac.uk/studies/chapters/images/pubimg/thumb/thm_dlwfig18.jpg which you can find here http://www.charm.rhul.ac.uk/studies/chapters/chap8.html
69
Hello,

I installed "aubio" like all other Plugins the recommended way via creating a "vamp" folder in the library audio plugins directory. All other plugins show up in the menu:
I select "Transform" and then "show by name" and there I can see
- beatRoot
- Match Performance Aligner
- Tempogram
... for example!

But I can't see "aubio"!

I followed the steps like with all the other plugins and I even watched a video by Matthias Mauch and he did it the same way I did it.

What am I doing wrong?

My System: Mac Os X 10.9, SV 2.4.1
installed Plugin: vamp-aubio-plugins-0.5.0-osx.tar.bz2
70
This paper http://dml.city.ac.uk/blog/wp-content/uploads/2015/03/DML-Final-Workshop-Audio-Analysis.pdf mentions three tempo/beat tracker plugins, one of those is simply named "Tempotracker Vamp Plugins" (see page 11)

I can't find it in the list of downloadable plugins. However there is a thread seeming to talk about it and there it says that it has bugs http://vamp-plugins.org/forum/index.php?topic=92.0


PS: an additional site note, so I don't spam the whole Forum with small questions... in the Musicologist's guide to Sonic Visualiser they tell one to install the "Vamp Audio Plugins" (for a person like me, who usually first thinks that I am the error, it took me quite a while to try if they are referring to "Vamp Aubio Plugins" and download it. Just a text correction, but...). Also, the Mazurka Plugin demanded to install in the guide is not available for Macs, did they not mention this with purpose, because you plan to port it for Mac in the future (and so you won't have to change the guide)?
Pages: 1 ... 5 6 [7] 8 9 10