Greetings all,
I'm seeing this message when starting Qtractor (not using a template).
lilv_world_load_file(): error: Error loading file `file:///home/windowsrefund/.lv2/stegosaurus.lv2/manifest.ttl'
The plugin in question is stegosaurus which I've compiled and installed. Installation adds the plugin to various locations under /usr as well as a single ~/.lv2/stegosaurus.lv2/waves/sine.wav file.
Since that path above is created under ~/.lv2, Qtractor ends up looking for a ~/.lv2/stegosaurus.lv2/manifest.ttl file which we already know does not exist.
I tried outsmarting this reasonable behavior and result by simply creating an empty ~/.lv2/stegosaurus.lv2/manifest.ttl file and then using the Options/Plugins/Blacklist dialog to select and add that file in the hopes that Qtractor would ignore any attempt to load it at startup.
My attempt did not work.
Any suggestions? I know I can simply ignore the message but now I'm just curious to know if the blacklist is even working or if I'm misusing the feature.
Thanks in advance.
re. blacklisting a plugin doesn't seem to be working...
hi,
blacklisting doesn't work for LV2 plugins, which are identified by an (abstract) URI and not a file-system path to a designated shared object (.so) as are all other plugin types (LADSPA, DSSI, VST2, VST3 and CLAP).
sorry
one other thing you may not realize about LV2 plugins: there can only be one version of the plugin in all of the configured search paths; having more than one and only with same URI, for example in ~/.lv2 and /usr/lib/lv2 won't work as you'd expect with other plugin types--LV2 URIs must be unique. always.
so you'd better move all files from /usr/lib/lv2/stegosaurus.lv2/* to ~/.lv2/stegosaurus.lv2/ (or remove the later).
sorry again
ps. or can just ignore the message; or report upstream to the developer that it's never good practice to install stegosaurus.lv2 on two places in the file-system.
Yep, I get it. I didn't move…
Yep, I get it. I didn't move any files and just compiled and installed using the provided Makefile. I'm of the same opinion that dropping a static .wav file in that path is a bad idea as even something like $XDG_DATA_HOME as a base would be more suitable. I'll send a PR upstream.
Add new comment