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 ... 16 17 [18] 19
256

The QM Vamp plugin set (now at version 1.3) is now available for 64-bit Linux, as well as 32-bit Linux, OS/X, and Windows.

Downloads from the usual page:

http://www.elec.qmul.ac.uk/digitalmusic/downloads/index.html#qm-vamp-plugins


Chris

257
Version 1.2pre2 of Sonic Visualiser is now available for testing.  This is the second pre-build of version 1.2, with a few new fixes over pre1.

Win32 executable:
http://www.sonicvisualiser.org/pre/sonic-visualiser-1.2pre2-win32.zip

OS/X (10.4 and newer) universal binary executable:
http://www.sonicvisualiser.org/pre/sonic-visualiser-1.2pre2-osx-universal.tar.bz2

Linux executable:
http://www.sonicvisualiser.org/pre/sonic-visualiser-1.2pre2-i686-linux.tar.bz2

Source code:
http://www.sonicvisualiser.org/pre/sonic-visualiser-1.2pre2.tar.bz2

As always, please report any new problems you find in the bug tracker:

http://sourceforge.net/tracker/?group_id=162924&atid=825705

See the announcement of pre1 for a fuller description and the long, long list of changes since version 1.0:

http://www.vamp-plugins.org/forum/index.php/topic,19.0.html

New fixes since 1.2pre1:

 * Fix failure to reload audio files that were originally identified using file:/// URLs, when reloading a session file
 * Include ID3 tag support in Windows and Mac builds (was already in Linux build of pre1)
 * Avoid crash on exit
 * Fix incorrect reassignment of source model in layers that had no source model previously, when loading a main model for the first time (an obscure fix)


Chris

258
Version 1.2pre1 of Sonic Visualiser is now available for testing.  This is the first pre-build of version 1.2, and is intended to be feature complete, with "only" bug-fixes and documentation remaining to be done for the 1.2 release.

Win32 executable:
http://www.sonicvisualiser.org/pre/sonic-visualiser-1.2pre1-win32.zip

OS/X (10.4 and newer) universal binary executable:
http://www.sonicvisualiser.org/pre/sonic-visualiser-1.2pre1-osx-universal.tar.bz2

Linux executable:
http://www.sonicvisualiser.org/pre/sonic-visualiser-1.2pre1-i686-linux.tar.bz2

Source code:
http://www.sonicvisualiser.org/pre/sonic-visualiser-1.2pre1.tar.bz2

Please try it out, and report any new problems you find in the bug tracker:

http://sourceforge.net/tracker/?group_id=162924&atid=825705

A complete list of the new features in 1.2 (since 1.0) is included in the distribution package, and is also reproduced below.

Note that the timeline alignment feature is only enabled if the MATCH Vamp plugin is installed -- you can download this from the Vamp plugins download page at  http://www.vamp-plugins.org/download.html.  You should see a toolbar button with an icon like this: next to the Solo button; click this to enable Align mode.  This button is absent if SV was unable to find the MATCH plugin.


New features in Sonic Visualiser 1.2, since the previous version 1.0:

 - SV now supports time-alignment of multiple performances of a work
 loaded at the same time.  This option is enabled when the MATCH Vamp
 plugin is installed.  When alignment is switched on and more than one
 audio file is open, SV will assume that all open files are
 differently timed performances of the same work, and will calculate
 time alignments for them.  Playback will then play only a single file
 at a time, and the playback cursors in other files will track at the
 varying speeds to try to ensure that each is at the same point in the
 underlying score.  This enables effective comparison of several such
 files, as well as a meaningful way to switch from one performance to
 another during playback (ensuring that the switch happens at the
 correct point in the performance being switched to).

 - There is a new Image layer, which can display images from the
 local filesystem or retrieved via HTTP or FTP.

 - A new measurement tool has been added.  With the measurement tool
 selected, dragging in a pane draws a rectangle labelled with the
 scale values for its start and end corners and its size.  You can
 have any number of measurements present at once; they are associated
 with the top layer, their scale values depend on the scale for that
 layer, and they are only shown when that layer is at the top and the
 measurement tool is active.  Measurements are saved and reloaded in
 the session file.  Drawing measurements can be undone and redone, and
 a measurement can be deleted by hitting Del when highlighted.  Note
 that the measurement tool shows the scale values associated with the
 pixel positions of the mouse when dragging, not any values associated
 with actual features present in the audio or its analysis (e.g. the
 values are not rounded to the nearest spectrogram bin).

 - You can double-click using the measurement tool in the spectrogram
 to get an instant measurement rectangle for a feature.  This is a
 purely graphical feature that works by calculating the boundary of a
 contiguous region of pixels "similar to" the one you double-clicked
 on; it does not use audio analysis.  Adjusting the gain and colour
 scheme etc of the spectrogram will (by design) affect the
 measurements obtained this way.

 - The spectrum can now optionally show frequency estimates of peaks
 aligned with a piano keyboard along the horizontal axis (this needs
 some refinement).

 - The harmonic cursor in the spectrogram has moved from the Select
 tool to the Measurement tool.  There is now a similar harmonic cursor
 in the spectrum.  Both of them show more information as text
 alongside the cursor than previously.

 - There is a new Erase tool for erasing individual points from an
 editable layer.

 - Several keyboard shortcuts have changed -- all of the Alt+key
 shortcuts now either use Ctrl or a plain keypress with no modifier,
 to avoid clashes with window manager shortcuts and to make them
 easier to use and remember

 - The playback controls are now in a Playback menu as well as the
 toolbar.

 - There is a new key and mouse control reference under Help (or press
 F2).

 - You can double-click on a pane in navigate mode to jump to a time.

 - All of the single-colour layers (waveform, time values etc) now
 allow you to define your own colours as well as using the built-in
 set.  The colour of a layer is now shown next to its name on the pane.

 - When you add a new single-colour layer it will use a default colour
 that is not yet in use in another layer (if there is one).

 - Single-colour layers can now optionally have black backgrounds (with
 a set of lighter colours in the default colour palette that use black
 backgrounds by default).

 - There's a new Printer colour scheme in the spectrogram with only a
 small number of grey shades.

 - Vertical zoom in a log-scaled spectrogram is much more intuitive;
 it now leaves the point that was in the centre of the visible area in
 the centre after zoom, instead of the point that was in the centre of
 the linear range corresponding to the visible area.

 - There's a new Layer Summary window which shows the panes and
 layer data in a tree layout.  This is very simplistic at the moment.

 - Each pane now has an [X] button at its top left, which removes that
 pane when clicked.

 - There's a new Solo play mode toggle button; when active, only the
 currently selected pane is played.  This is also the default when
 time alignment is in use.

 - Rewind/ffwd now stay confined to the selection if Play Selection is
 enabled; also, the rewind and ffwd "one step" buttons are now enabled
 even if there is no time instants layer for them to align to (they
 align to the time ruler instead and so jump in steps of a size
 dependent on the zoom level).

 - You can now export note layers to MIDI.

 - MIDI note velocity is partially supported.  Note velocity is
 retained when importing and exporting MIDI and is used in playback,
 but it is not yet shown in the display and cannot yet be edited.

 - You can now drag-and-drop files (of whatever type) onto SV from
 other programs such as file managers or web browsers.

 - mp3 files (and Ogg, but they aren't supported on Windows at the
 moment) are now decoded in a background thread so you can see the
 start of the track without waiting for the rest to decode.

 - Mac builds of SV can now load AAC/mp4 files and anything else
 supported by QuickTime.

 - There is now an option to resample audio files on import if they
 don't match the samplerate of the first file loaded.  By default this
 is switched off, as it affects the visible waveform.  The default
 behaviour is unchanged (play at the wrong rate).  There is still no
 option to handle multiple rates "correctly" (i.e. by resampling
 on playback and showing the waveforms at different resolutions
 according to each one's underlying rate) and there probably never
 will be.

 - SV can now open .m3u playlist files, though it's a hazardous thing
 to do as it simply loads all the files in the playlist at once.

 - SV now has various options for how to number tapped time instants
 (bar/beat, plain counter, time in seconds, tempo etc).

 - The official builds now use Qt 4.3, which fixes some nasty
 bugs in the file dialog that the version 1.0 builds suffered from.


Chris

259

What does "ldd vamp-mazurka.so" say?  It may be picking up the wrong version of the library.  Also, the 1.1 SDK had an incorrect soname for the installed plugins which the 1.1b SDK corrects, so it might be worth updating, although I wouldn't expect this to cause the error you quote.

If in doubt, try using static linkage for the SDK libraries when linking the plugin (i.e. -Wl,-Bstatic -lvamp-sdk -Wl,-Bdynamic in the link line).  Although plugins made with one of the 1.0 and 1.1 SDKs are compatible with hosts made with the other, that obviously doesn't help if the plugins themselves refuse to load because they can't find the dynamic library that matches the headers they were compiled with!

With regard to the QM plugins, we (I'm one of the QM guys) have had requests for a 64-bit build before, and hope to be able to come up with something fairly soon.  I'm afraid there is no workaround; a 64-bit host simply can't load a 32-bit shared library, full stop.


Chris

260
Plugin and Host Announcements / Vamp plugin SDK v1.1b now available
« on: October 19, 2007, 16:16:12 »

Version 1.1b of the Vamp plugin SDK is now available.

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

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.

Version 1.1b is a minor update with a small number of build and bug fixes.

The prior version 1.1 of the SDK introduced a new set of classes designed to make it very simple for an application to use Vamp plugins, without needing to do complicated plugin lookup or audio processing themselves.

Plugins and hosts remain 100% binary compatible with those built using the 1.0 version of the SDK.


Chris

261
Host Forum: Sonic Visualiser / Re: Building for 64-bit?
« on: September 20, 2007, 09:54:09 »
Do you mean building Sonic Visualiser?  On which platform -- Linux?

The qmake + make should work correctly for 64-bit Linux builds.  There is one line of code in the 1.0 release that may not compile in a 64-bit environment -- line 64 of sv/osc/OSCQueue.cpp:

    case 'h': message.addArg(arg->h); break;

If the build fails there, just comment out that line (with "//" at the start), as it isn't necessary anyway.

I've never actually used SV in a 64-bit distribution, but reports suggest that it does work OK.


Chris

262
Plugin Development / Future plans for the Vamp plugin interface
« on: August 15, 2007, 13:23:38 »

What would you like to see happen next with the Vamp plugin interface?

At the moment we're concentrating on a few enhancements that can be made while retaining binary compatibility and stability in the interface.  There will be a Vamp SDK version 1.1 release very shortly, which will add several new classes for hosts to handle plugin lookup and other utility tasks; these will retain binary compatibility and won't affect plugins at all.

However, we'd also like to find out what sort of interest there may be in non-binary compatible additions that may warrant a version 2.0 of the API at some point in future.

Some additions that have been suggested include:

  • Give features an optional duration as well as a starting timestamp.  At the moment, plugins such as note trackers that return features with duration generally do so by treating (for example) frequency and duration as two separate values in a feature structure's value vector.  This is problematic, partly because there is no way to supply separate units for the separate values in the vector (see next point).
  • Provide a way to supply separate units for the separate values in a feature's value vector.
  • Allow a plugin to declare that a particular output is causal, i.e. that all of the results from that output are returned from process() and (explicitly or implicitly) timestamped within the current process block, instead of being returned in a later block or from getRemainingFeatures.  There are various classes of host that could make use of this information, for example if the plugin is providing auxiliary data to be used in a further ongoing calculation.
  • Make it possible to group plugin parameters in some way (for example, include "normal user" and "advanced" parameters).

Any other ideas?  What problems have you faced with the current API that you may or may not have an idea how to solve?  Would you make use of any of the suggestions above?


Chris

263
Alexander,

Any chance you could post a bug report in the tracker at

http://sourceforge.net/tracker/?group_id=162924&atid=825705

and attach an example of the sort of file you're trying to import, please?

Thanks,


Chris

264
Host Forum: Sonic Visualiser / Re: Tapping in Sonic Visualiser
« on: July 06, 2007, 16:30:39 »
Hm, that is a bit laborious!  I wonder whether there is anything else we could do.

Yes, if you wouldn't mind sending me those files, that might perhaps be helpful.

As a matter of interest, if SV did gain the ability to accept taps from a MIDI device, would you be in a position to take advantage of that?  Do you have a USB MIDI keyboard for example?  It would be a non-trivial addition, but might be worth doing if users would substantially benefit.


Chris

266
Host Forum: Sonic Visualiser / Re: Tapping in Sonic Visualiser
« on: June 13, 2007, 10:45:34 »
Sorry for not replying sooner.  [Note to other readers: Serge sent me an email about substantial problems with the accuracy of the tapped timings when tapping in SV.]  To be honest, I don't really have an answer.

Tapping is implemented using a generic toolkit-level shortcut to a menu function, so it is very much at the mercy of the toolkit, windowing system, general system load, etc.  There is no real-time guarantee or system timestamping for tapping event delivery, or anything like that.  I don't understand why your results were so particularly bad, but even so I fear there may not be much that can be done within the constraints of your system to improve them, or at least I wouldn't know what.

Craig Sapp also did some measurements (on Windows -- I'm not sure whether you mentioned which platform you were using) of tapping performance and found that "long-term accuracy" was good but local quantization not so good (see http://www.charm.rhul.ac.uk/content/svtraining/svtour-20060630.ppt).  It's clear that he was seeing much better results than you are, although I consider the results he reports as "in need of improvement" as well.

To do substantially better than SV does currently, it may be necessary to bypass the GUI toolkit (Qt) for tapping events, but I'm not quite sure how best to approach that at present, at least in a cross-platform manner.

A more sophisticated and reliable method would be to use MIDI events for tapping.  Of course this would require a MIDI input device (e.g. cheap USB MIDI keyboard) but would have the advantage that MIDI library code is available on all platforms that is designed to handle rapid delivery with timestamping where appropriate.

Needless to say, patches are welcome!


Chris

267

A first prerelease version of the Vamp plugin SDK version 1.1 is now available from:

  http://www.vamp-plugins.org/pre/vamp-plugin-sdk-1.1pre1.tar.gz

The main addition for version 1.1 is a set of classes designed to make it very simple for a program to become a Vamp plugin host.

The new Vamp::HostExt namespace contains a PluginLoader class, which handles enumeration, loading and category management for plugins on the local system.  Also provided are two new plugin adapters: PluginInputDomainAdapter which provides the capability for a host to support frequency-domain plugins without needing to worry about domain conversion, and PluginChannelAdapter to transparently deal with plugins that expect different numbers of audio channels from the number available.

Version 1.1 also makes some minor beauty-and-truth updates and clarifies some of the documentation.  Apart from the new classes, the public programming API remains the same as version 1.0 of the SDK.  The SDK also remains 100% binary compatible with existing Vamp 1.0 plugins, and the API version number is unchanged at 1.

If you are likely to have any interest in the final 1.1 SDK, I urge you to test this prerelease and report on your findings!

Thanks,


Chris

268
I've added a note about VAMP_PATH to the download page.


Chris

269
I just wrote a reply agreeing with you, and saying I would add such a variable in future versions.

But then I went back and checked the code, and found that there already is one - VAMP_PATH.  On Windows, it should be a semicolon-separated list of folder paths.  I don't have a Windows box to hand at the moment -- does it work?


Chris

270
Host Forum: Sonic Visualiser / Sonic Visualiser v1.0 released
« on: May 11, 2007, 18:50:29 »
Version 1.0 of Sonic Visualiser is now available.

  http://www.sonicvisualiser.org/

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,
and slow down playback while retaining display synchronisation.  Sonic
Visualiser also supports the Vamp plugin API for plugins that extract
descriptive or analytical data from audio.

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


Chris

Pages: 1 ... 16 17 [18] 19