[Ardour-Users] ambix LV2 vs ardour?
Fernando Lopez-Lezcano
nando at ccrma.Stanford.EDU
Wed Feb 20 23:06:34 PST 2019
On 2/20/19 4:21 PM, Robin Gareus wrote:
> Hi Nando!
Hey!!
> On 2/21/19 12:52 AM, Fernando Lopez-Lezcano wrote:
>
>> [ERROR]: LV2: Failed to instantiate plugin
>> file:///usr/lib64/lv2/ambix_converter_o1.lv2/ambix_converter_o1
>
> Is there any info on stdout, stderr?
Not relevant to those plugins (but I will try again - I was starting
from command line to see what ardour would have to say about this...)
>> The directory looks like this:
>>
>> ls -l /usr/lib64/lv2/ambix_converter_o1.lv2/
>> total 5068
>> -rwxr-xr-x. 1 root root 5171056 Nov 29 20:43 ambix_converter_o1.so
>> -rw-r--r--. 1 root root 5504 Nov 29 19:50 ambix_converter_o1.ttl
>> -rw-r--r--. 1 root root 901 Nov 29 19:50 manifest.ttl
>> -rw-r--r--. 1 root root 378 Nov 29 19:50 presets.ttl
>
> One possibility is that the plugin is not statically linked and requires
> external libs that conflict with Ardour's or perhaps some other plugins;
> or maybe the architecture mismatches?
>
> file /usr/lib64/lv2/ambix_converter_o1.lv2/ambix_converter_o1.so
> ldd /usr/lib64/lv2/ambix_converter_o1.lv2/ambix_converter_o1.so
The architecture is correct, I think (64 bits) and it is not statically
linked (see below - lots of shared libraries). I guess some weird
library conflict with ardour might be the culprit.
# file /usr/lib64/lv2/ambix_converter_o1.lv2/ambix_converter_o1.so
/usr/lib64/lv2/ambix_converter_o1.lv2/ambix_converter_o1.so: ELF 64-bit
LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked,
BuildID[sha1]=32450565ffb9657de4eac3c87301ac1388e33e3d, stripped, too
many notes (256)
# ldd /usr/lib64/lv2/ambix_converter_o1.lv2/ambix_converter_o1.so
linux-vdso.so.1 (0x00007ffff87fa000)
libzita-convolver.so.3 => /lib64/libzita-convolver.so.3
(0x00007f8f1047f000)
libX11.so.6 => /lib64/libX11.so.6 (0x00007f8f1033a000)
libXext.so.6 => /lib64/libXext.so.6 (0x00007f8f10325000)
libXinerama.so.1 => /lib64/libXinerama.so.1 (0x00007f8f10320000)
libasound.so.2 => /lib64/libasound.so.2 (0x00007f8f10218000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f8f10212000)
libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00007f8f10152000)
librt.so.1 => /lib64/librt.so.1 (0x00007f8f10148000)
libglut.so.3 => /lib64/libglut.so.3 (0x00007f8f10090000)
libXmu.so.6 => /lib64/libXmu.so.6 (0x00007f8f10073000)
libXi.so.6 => /lib64/libXi.so.6 (0x00007f8f10061000)
libGL.so.1 => /lib64/libGL.so.1 (0x00007f8f0ffcd000)
libGLU.so.1 => /lib64/libGLU.so.1 (0x00007f8f0ff59000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f8f0ff37000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f8f0fd9f000)
libm.so.6 => /lib64/libm.so.6 (0x00007f8f0fc1b000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f8f0fc00000)
libc.so.6 => /lib64/libc.so.6 (0x00007f8f0fa3a000)
libfftw3f.so.3 => /lib64/libfftw3f.so.3 (0x00007f8f0f827000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f8f0f7fc000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8f10991000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f8f0f7e9000)
libpng16.so.16 => /lib64/libpng16.so.16 (0x00007f8f0f7b3000)
libz.so.1 => /lib64/libz.so.1 (0x00007f8f0f799000)
libICE.so.6 => /lib64/libICE.so.6 (0x00007f8f0f779000)
libXxf86vm.so.1 => /lib64/libXxf86vm.so.1 (0x00007f8f0f772000)
libXt.so.6 => /lib64/libXt.so.6 (0x00007f8f0f707000)
libGLX.so.0 => /lib64/libGLX.so.0 (0x00007f8f0f6d3000)
libGLdispatch.so.0 => /lib64/libGLdispatch.so.0 (0x00007f8f0f616000)
libXau.so.6 => /lib64/libXau.so.6 (0x00007f8f0f60f000)
libSM.so.6 => /lib64/libSM.so.6 (0x00007f8f0f604000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f8f0f5fb000)
(so lots of things...)
By the way, lv2ls does list it just fine so it seems to be a valid lv2
plugin... And ardour sees and tries to load it, but fails at the last
moment (qtractor is fine with them).
> may shed some light.
Still in the dark :-)
Something I should try is to build without all the flags that Fedora
uses for building things. Maybe that is messing up things somehow.
Thanks!
-- Fernando
More information about the Ardour-Users
mailing list