Hi!
I want to use a plugin (https://github.com/stevie67/loopor). I’ve installed it, but Ardour does not see it.
I don’t know why it doesn’t work and what to do… help me
Do you have the files loopor.so, loopor.ttl, manifest.ttl and modgui.ttl in your /usr/local/lib/lv2/loopor.lv2 directory?
Does your version of Ardour support LV2? Click Help -> About -> Config and verify that it says
LV2 UI embedding: True
LV2 support: True
LV2 extensions: True
Hello!
studio@Studio-PC:/usr/local/lib/lv2/loopor.lv2$ dir
loopor.so loopor.ttl manifest.ttl manifest.ttl.in modgui modgui.ttl
studio@Studio-PC:/usr/lib/lv2/loopor.lv2$ dir
loopor.so loopor.ttl manifest.ttl manifest.ttl.in modgui modgui.ttl
Config:
Build documentation: False Debuggable build: False Export all symbols (backtrace): False Install prefix: /usr Strict compiler flags: [] Internal Shared Libraries: True Use External Libraries: False Library exports hidden: True Free/Demo copy: False ALSA DBus Reservation: True Architecture flags: None Aubio: True AudioUnits: False Build target: x86_64 Canvas Test UI: False Beatbox test app: False CoreAudio: False CoreAudio 10.5 compat: False Debug RT allocations: False Debug Symbols: False Denormal exceptions: False FLAC: True FPU optimization: True Freedesktop files: False Libjack linking: weak Libjack metadata: True Lua Binding Doc: False LV2 UI embedding: True LV2 support: True LV2 extensions: True LXVST support: True Mac VST support: False OGG: True Phone home: True Process thread timing: False Program name: Ardour Samplerate: True PT format: True PTW32 Semaphore: False Threaded WaveViews: True Translation: True Unit tests: False Windows VST support: False Wiimote support: False Windows key: Mod4><Super PortAudio Backend: False CoreAudio/Midi Backend: False ALSA Backend: True Dummy backend: True JACK Backend: True Builstack: -unknown- Mac i386 Architecture: False Mac ppc Architecture: False C compiler flags: ['-I/home/ardour/linux-x86_64-v5/ardour', '-I/home/ardour/linux-x86_64-v5/gtk/inst/include', '-DHAVE_RF64_RIFF', '-DWAF_BUILD', '-DNDEBUG', '-std=c99', '-pedantic', '-Wshadow', '-Wall', '-Wcast-align', '-Wextra', '-Wwrite-strings', '-Wunsafe-loop-optimizations', '-Wlogical-op', '-fshow-column', '-O3', '-fomit-frame-pointer', '-ffast-math', '-fstrength-reduce', '-pipe', '-DARCH_X86', '-mmmx', '-msse', '-mfpmath=sse', '-DUSE_XMMINTRIN', '-DBUILD_SSE_OPTIMIZATIONS', '-DLXVST_64BIT', '-Wall', '-Wpointer-arith', '-Wcast-qual', '-Wcast-align', '-Wno-unused-parameter', '-DBOOST_SYSTEM_NO_DEPRECATED', '-D_ISOC9X_SOURCE', '-D_LARGEFILE64_SOURCE', '-D_FILE_OFFSET_BITS=64', '-DENABLE_NLS', '-DPROGRAM_NAME="Ardour"', '-DPROGRAM_VERSION="5"', '-Wstrict-prototypes', '-Wmissing-prototypes'] C++ compiler flags: ['-I/home/ardour/linux-x86_64-v5/ardour', '-I/home/ardour/linux-x86_64-v5/gtk/inst/include', '-DHAVE_RF64_RIFF', '-DWAF_BUILD', '-DNDEBUG', '-ansi', '-Wnon-virtual-dtor', '-Woverloaded-virtual', '-fstrict-overflow', '-Wall', '-Wcast-align', '-Wextra', '-Wwrite-strings', '-Wunsafe-loop-optimizations', '-Wlogical-op', '-fshow-column', '-O3', '-fomit-frame-pointer', '-ffast-math', '-fstrength-reduce', '-pipe', '-DARCH_X86', '-mmmx', '-msse', '-mfpmath=sse', '-DUSE_XMMINTRIN', '-DBUILD_SSE_OPTIMIZATIONS', '-DLXVST_64BIT', '-Wall', '-Wpointer-arith', '-Wcast-qual', '-Wcast-align', '-Wno-unused-parameter', '-DBOOST_SYSTEM_NO_DEPRECATED', '-D_ISOC9X_SOURCE', '-D_LARGEFILE64_SOURCE', '-D_FILE_OFFSET_BITS=64', '-DENABLE_NLS', '-DPROGRAM_NAME="Ardour"', '-DPROGRAM_VERSION="5"', '-std=c++11', '-DBOOST_NO_AUTO_PTR', '-Woverloaded-virtual', '-Wno-unused-local-typedefs', '-D__STDC_LIMIT_MACROS', '-D__STDC_FORMAT_MACROS', '-DCANVAS_COMPATIBILITY', '-DCANVAS_DEBUG'] Linker flags: ['-L/home/ardour/linux-x86_64-v5/gtk/inst/lib']
Is there a requirement that the LV2 plugins be compiled as 64 bit when using a 64 bit build? I have a 64 bit installation, but my lv2 plugins are in /usr/local/lib instead of /usr/local/lib64, and as far as I could see the ttl files do not describe what architecture the plugin was built for.
When I run file on the so files it confirms that the plugins were build as ELF 64-bit files, but the ttl files do not mention architecture at all.
Do you see any other LV2 plugins in Ardour?
It’s strange that you have manifest.ttl.in and modgui in that directory and that you have the files both in /usr/lib and /usr/local/lib
Did you install in both directories on purpose?
What happens if you run
ldd /usr/local/lib/lv2/loopor.lv2/loopor.so
and
ldd /usr/lib/lv2/loopor.lv2/loopor.so
You should be seeing something smilar to
linux-vdso.so.1 (0x00007ffd5b92e000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f13332ca000)
libm.so.6 => /lib64/libm.so.6 (0x00007f1332fcd000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f1332db6000)
libc.so.6 => /lib64/libc.so.6 (0x00007f1332a15000)
/lib64/ld-linux-x86-64.so.2 (0x00007f1333858000)
If you run
lv2ls | grep loopor
you should see
http://radig.com/plugins/loopor
if everything is working as it should.
lv2ls comes with the lilv package so you have to install that in case you get a command-not-found.
I think the plugin architecture has to match Ardour’s but even 64-bit Ardour searches for LV2 plugins in /usr/local/lib/lv2 .
It doesn’t appear to look in /usr/local/lib64/lv2 ; I’ve had to put symlinks from the LV2s that installed into lib64/lv2 to lib/lv2 for them to show up.
And a 32-bit Ardour will probably work in a 64-bit distro if you have the 32-bit userland libs installed but you won’t be able to use any 64-bit plugins youve compiled yourself.
It depends on the installation program if the files are put in lib or lib64. Many programs you complile yourself puts 64-bit libs in /usr/local/lib.
Hi!
studio@Studio-PC:~$ ldd /usr/local/lib/lv2/loopor.lv2/loopor.so
linux-vdso.so.1 => (0x00007ffe54df9000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f92e10e8000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f92e0ddf000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f92e0bc8000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f92e0801000)
/lib64/ld-linux-x86-64.so.2 (0x000055f621467000)
studio@Studio-PC:~$ lv2ls | grep loopor
Error opening file /home/studio/.lv2/Graphic_Equalizer_x32_MidSide_-Grafischer_Entzerrer_x32_MidSide_�_�.lv2/manifest.ttl (No such file or directory)
lilv_world_load_file(): error: Error loading file file:///home/studio/.lv2/Graphic_Equalizer_x32_MidSide_-_Grafischer_Entzerrer_x32_MidSide_%D0%BD%D0%B0%D1%88_%D0%B4%D0%B2%D0%BE%D1%80.lv2/manifest.ttl' lilv_world_load_bundle(): error: Error reading file:///home/studio/.lv2/Graphic_Equalizer_x32_MidSide_-_Grafischer_Entzerrer_x32_MidSide_%D0%BD%D0%B0%D1%88_%D0%B4%D0%B2%D0%BE%D1%80.lv2/manifest.ttl Error opening file /home/studio/.lv2/Graphic_Equalizer_x32_Stereo_-_Grafischer_Entzerrer_x32_Stereo__.lv2/manifest.ttl (No such file or directory) lilv_world_load_file(): error: Error loading filefile:///home/studio/.lv2/Graphic_Equalizer_x32_Stereo-Grafischer_Entzerrer_x32_Stereo%D0%9D%D0%BE%D0%B2%D0%BE%D0%B5_%D0%BF%D0%BE%D0%BA%D0%BE%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5.lv2/manifest.ttl’
lilv_world_load_bundle(): error: Error reading file:///home/studio/.lv2/Graphic_Equalizer_x32_Stereo_-Grafischer_Entzerrer_x32_Stereo%D0%9D%D0%BE%D0%B2%D0%BE%D0%B5_%D0%BF%D0%BE%D0%BA%D0%BE%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5.lv2/manifest.ttl
lilv_world_add_plugin(): warning: Duplicate plugin http://radig.com/plugins/loopor
lilv_world_add_plugin(): warning: … found in file:///usr/lib/lv2/loopor.lv2/
lilv_world_add_plugin(): warning: … and file:///usr/local/lib/lv2/loopor.lv2/ (ignored)
Error opening file /usr/local/lib/lv2/lsp-plugins-lv2-1.0.23-x86_64/manifest.ttl (No such file or directory)
lilv_world_load_file(): error: Error loading file `file:///usr/local/lib/lv2/lsp-plugins-lv2-1.0.23-x86_64/manifest.ttl’
lilv_world_load_bundle(): error: Error reading file:///usr/local/lib/lv2/lsp-plugins-lv2-1.0.23-x86_64/manifest.ttl
http://radig.com/plugins/loopor
what does it mean?
The first ldd command tells us that your loopor plugin is 64-bit, so you’re running a 64-bit distro.
Is Ardour also 64-bit? Help -> About should say “Intel 64-bit” at the bottom.
If it doesn’t the problem is that you’re running a 32-bit version of Ardour.
Do you see any LV2 plugins in Ardour at all?
The missing manifest.ttl files are strange since all LV2 plugins should have that file.
There could be a problem with the Graphic_Equalizer being a 32-bit (x32) program but lv2ls should have found the manifest file anyway.
Can you see that file in the directories where you get the error?
Please run ‘ls -la’ instead of ‘dir’ so we can see the file size and permissions. It could be that you have the wrong ownership and read permissions on that file or directory, if you put it there as root for instance.
There could potentially be a problem with the directory names you have as well. Particularly the ones in your .lv2 directory where you have the strange “%D0%9D%D0%BE%D0%B2%D0%BE%D0%B5_%D0%BF%D0%BE%D0%BA%D0%BE%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5” string as part of the name.
Perhaps that confuses Ardour when it’s scanning for plugins.
You can try and rename your /home/studio/.lv2 directory to /home/studio/_lv2 , to hide it from Ardour, and see if that changes anything.
lv2ls sees both /usr/lib/lv2/loopor.lv2/ and the duplicate /usr/local/lib/lv2/loopor.lv2/ and ignors the latter.
It also sees the correct http://radig.com/plugins/loopor entry.
Why do you have that plugin in both directories?
If the one in /usr/lib/ is an older one that you installed through your package manager you should remove that so that you only have the newer one in /usr/local/lib
Hi!
OS 64bit, Ardour - 64bit.
Yes, i see other plugins
renamed /home/studio/.lv2 directory to /home/studio/_lv2 - nothing has changed… Ardour plugin does not see
root@Studio-PC:/usr/local/lib/lv2/loopor.lv2# ls -la
итого 44
drwxr-xr-x 3 root root 4096 янв 16 22:18 .
drwxr-xr-x 3 root root 4096 янв 18 22:58 …
-rwxrwxrwx 1 root root 14688 янв 15 22:25 loopor.so
-rw-rw-r-- 1 root root 2309 апр 22 2017 loopor.ttl
-rw-r–r-- 1 root root 289 янв 15 22:25 manifest.ttl
-rwxr-xr-x 1 root root 289 апр 22 2017 manifest.ttl.in
drwxr-xr-x 5 root root 4096 янв 16 22:18 modgui
-rw-rw-r-- 1 root root 755 апр 22 2017 modgui.ttl
all other plugins are in the folder /usr/lib/lv2
moved the plugin to this folder /usr/lib/lv2.
it did not help.
The -rwxrwxrwx on loopor.so should be -rw-r–r-- (chmod 644) but I set my permission to that (chmod 777) and Ardour still finds it.
I’m sorry but I have run out of ideas. You should go to the chat forum and see if someone over there can help you.
It’s available through Help->Chat or directly at http://webchat.freenode.net/?channels=ardour
Thank you for participating
You have two copies of loopor your system. One in /usr/lib and one in /usr/local/lib. The LV2 libraries used to discover and load LV2 plugins finds them both, and ignores the 2nd one (in this case, the one in /usr/local/lib). So whatever reason(s) there are for it not appearing in Ardour are related to the version in /usr/lib (probably installed via your system software package manager), and are probably not related to the one in /usr/local/lib
Good day! This plugin I compiled with the command MAKE INSTALL from the source code. It was installed in usr/local/lib/lv2/. I reinstalled the system to UbubteStudio 17.10. Re-installed the plugin. Ardour plug-in found. But the GUI is not showing and I can’t figure out whether it works or not, so as to create a loop and play it back I can’t. Has anyone tried the plugin to use? It works? Or at me hands curves…
Good day! This plugin I compiled with the command MAKE INSTALL from the source code. It was installed in usr/local/lib/lv2/. I reinstalled the system to UbubtuStudio 17.10. Re-installed the plugin. Ardour plugin found. But the GUI is not showing and I can’t figure out whether it works or not, so as to create a loop and play it back I can’t. Has anyone tried the plugin to use? It works? Or at me hands curves…
The loopor as no GUI, only a MOD specific html ui.
Hi,
A few things to consider…
That plugin is made for the ARM CPU-based MOD Duo guitar effects pedal, I don’t think it is really intended for use in DAWs like Ardour, at least that doesn’t appear to be it’s focus…
I use this plugin in the MOD Duo, and it works well but it currently also has no UI of it’s own in the MOD and relies on their template ‘tuna can’ UI. Perhaps the UI referred to in the GitHub notes is a MOD UI which would be different from a UI shown in a DAW or other LV2 plugin host. In any case whatever the state of the UI is it is quite possible not complete enough to get opted in when you compile the source code.
Anyway it’s an alpha state plugin developed for a different platform, I think it’s pretty realistic at this point to expect some difficulties 
oops posted at the same time as x42…
Hi. Most interesting is that the plugin works, but weird. I can’t control the recording process. The sound recording occurs, but when the recording starts and when it ends is not clear, also, I could not get overdub write and reset. I suspect that the problem is in the logic controlling the buttons of the plugin. I will experiment.
GMaq, In Your Mod Duo button work as a switch or as a simple button?
Hi! Good news… the Plugin works!!! The problem was in the controlling to plugin. To control it requires a short push on button (control pulses)… it Remains to understand how to change this logic… I will think.