clearly-broken-software/ninjas2

Cannot be scanned nor used by Reaper Linux

Closed this issue · 5 comments

6-AND-9 commented

Hi there,

Tried to put the .so files in my VST/LV2 directory, but unfortunately Reaper is unable to scan it. That means I cannot use it.

What could be the problem and how do I figure it out?

Thanks,

  • A
6-AND-9 commented

Weird, can't run the native Linux binary but can run the yabridge converted Windows VST!?

rghvdberg commented
rghvdberg commented

I seems to work fine here on Ubuntu 20.04

  1. download and install Reaper for Linux
    🔗 https://www.reaper.fm/files/6.x/reaper666_linux_x86_64.tar.xz
  2. download and extract Ninjas2
    🔗 https://github.com/clearly-broken-software/ninjas2/releases/download/v0.2.0/ninjas2-linux64.zip
    The extracted directory looks like this
ninjas2-linux64
├── ninjas2.lv2
│   ├── manifest.ttl
│   ├── ninjas2.so
│   └── ninjas2.ttl
└── ninjas2-vst.so
  1. Now copy the ninjas2.lv2 with it contents directory to ~/.lv2
~/.lv2 
❯ ls -l ninjas2.lv2/
totaal 1416
-rw-rw-r-- 1 rob rob    1085 jan 17  2020 manifest.ttl
-rwxrwxr-x 1 rob rob 1430384 jan 17  2020 ninjas2.so
-rw-rw-r-- 1 rob rob    8997 jan 17  2020 ninjas2.ttl
  1. Reaper finds ninjas2.lv automatically.
    image
sjaehn commented

@6-AND-9 : I assume that you can scan and load other LV2 plugins from your LV2/VST directory, isn't it? And did you load any other plugin before Ninjas2? Or did you try to load Ninjas2 as the first one?

@rghvdberg : Do you dynamically link the required libs or do you create builds with statically included libs (and hide all symbols)?

Incompatible dynamically linked libs are often the reason why plugins won't load. For instance, this is the reason why Calf plugin UIs are not loaded in Reaper. Just a little idea. Maybe I'm wrong here.

rghvdberg commented

It's all static afaik. Dpf magic