Skip to content

vamp plugin "segmentation fault" #635

Closed

Description

@sildeag

On Ubuntu 17.04 64-bit, Essentia 2.1, with clean build from source code --with-vamp:

libvamp_essentia.so is excluded from vamp plugins used by "sonic-visualiser 3.0." vamp plugin test fails indicating "segmentation fault." The same problem affects "audacity" except it just crashes and "sonic-annotator."

Essentia uses vamp sdk version 2.4 and latest version of vamp sdk is 2.7. Would changes made to wscript in src/examples folder be the correct place to upgrade the build so that vamp sdk 2.7 is used rather than 2.4? I would like to use something like this.

VAMP_SDK_DIR = /home/<user name>/vamp-plugin-sdk and

# Libraries required for the plugins.
#
PLUGIN_LIBS = -L../vamp-plugin-sdk/vamp-sdk -Wl,-Bstatic -lvamp-sdk -Wl,-Bdynamic -lpthread

# Flags required to tell the compiler to make a dynamically loadable object
#
PLUGIN_LDFLAGS = -shared -Wl,-Bdynamic -Wl,-soname=$(PLUGIN) $(VAMP_SDK_DIR)/libvamp-sdk.a -Wl,--version-script=vamp-plugin.map

# File extension for a dynamically loadable object
#
PLUGIN_EXT = .so

Are there any special flags that should be used in "essentia 2.1"?

Activity

  1. dbogdanov commented on Aug 18, 2017

    @dbogdanov
    Member

    No problems running the newest Sonic Visualizer v3.0.3 and sonic-annotator v1.5 on Mac OSX with the Essentia's vamp plugin built with the old SDK. Also, sonic-annotator v1.5 works fine with it on my Ubuntu 16.04 too.

  2. dbogdanov commented on Aug 18, 2017

    @dbogdanov
    Member

    @sildeag Correct, you can modify src/examples/wscript if you want to.

  3. dbogdanov commented on Aug 18, 2017

    @dbogdanov
    Member

    I get setfault in sonic-annotator on Ubuntu, when using the --build-static flag in waf configure to build the Vamp plugin. Will look into this now...

  4. added a commit that references this issue on Aug 31, 2017
    d3e436a
  5. dbogdanov commented on Aug 31, 2017

    @dbogdanov
    Member

    Fixes are to be merged in master.

  6. sildeag commented on Sep 2, 2017

    @sildeag
    Author
  7. dbogdanov commented on Sep 8, 2017

    @dbogdanov
    Member

    We'll update to Vamp 2.7 in future, but the issue was not related to that.

  8. sildeag commented on Sep 9, 2017

    @sildeag
    Author

    Thanks. Yes, with the revisions you made vamp plugin works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions