There’s a lot of great information in this thread, thanks!
I’m a beginner with Linux and the Raspberry Pi, but I’ve been blundering through these instructions and was able to get the QMidiArp plugins working using Enkerli’s method. Initially I could see them but not add them, used Giedrius’ journal method to debug, and found it wanted a bunch of related “.so” files. I ended up using “sudo apt-get install qmidiarp” to generate those, tracked them down, and copied them into the relevant folders…success.
I thought I’d then try installing the Yoshimi LV2 synth plugin, but I’ve got stuck with that one.
I installed this list of dependencies, then used “sudo apt-get install yoshimi” and copied the LV2 folder. I could now see an entry for Yoshimi in MODEP and add it, but there were no controls or parameters available. I then tried copying the above steps for QMidiArp. However, at the line “git checkout lv2extui”, instead of the message “Switched to a new branch” that you get with QMidiArp, it just says: “…did not match any files known to Git”.
There is mention of lv2extui in the Yoshimi LV2 plugin source here, but I don’t really know what this is or what to do with it. Any thoughts…?
Not all LV2 plugins have a GUI that is compatible with MOD, in that case a default UI is shown and the controls should be available in the settings menu of the plugin.
Hello,
I’m trying to make the MPB on my ubuntu.
There are some optimizations to do for a raspberry pi 3b on plugin-dep folder for the cortex a53.
Unfortunately the buildroot 2016.02 doesn’t work with the a53.
I downloaded the 2018.02 but I have some issues for r2_external tree…
How do you configured your environment to match a raspberry instead of a MOD?
@Giedrius, @Enkerli could you share a built Helm plugin? I’m trying to build a Pi-based midi-synth and got MODEP working on it, but I really want to have Helm which is not yet available. Or maybe share a high level instruction on how to build it? I read Many More Extra MODEP Plugins but sitll not sure how to start from nothing (I’ve got Windows 10 and also a small Arch Linux server) to build Helm lv2…
UPD1: so far I’ve done:
connected Pi to ethernet to get internet; apt-get update; apt-get install git
UPD2:
Nevermind, I have it working now! Step 4 resulted in successfully compiled helm.lv2 folder which I just copied to /usr/local/modep/.lv2 and that’s it!
Glad there’s still work done on these MODEP .lv2 plugins. Though I haven’t done much on Pisound for a while, I keep mentioning it whenever relevant and MODEP has been a big part of that. I’m actually planning some action-research activities which might lead me to co-design activities around plugins. Finding ways to build cross-platform plugins which end up working on a Pi4 running MODEP would be most excellent.
And the range of plugins currently available could sure serve as more than inspiration.
I discovered pisound and mod-host a few months ago, and I found that some modgui was missing … (my favorite DEXED and NOISEMAKER) … I learned and designed with pleasure … but I remain basic in programming … share my github with pleasure … at the moment I work on Helm …
Hi there blokas community! Thank you so much for this offering, Enkerli and all who contributed. I have been fumbling through the instructions here and on the mod devices pages, as I am very interested in using the remain calm plugins (esp. avocado and floaty), which are not available through the quick/easy method described by whofferbert.
So far, I have been able to successfully build the plugins through docker, but I am not sure what to do from there - to be able to move it to the lv2 folder on the pi. When I tried to follow/modify the commands on the mod devices site (see my attempt below), I just get errors that the lv2 files are directories and cannot be accessed (I also have no idea what this does, or how to properly configure it).
But I think I may have missed a step earlier on as well, since I was not able to run the bootstrap.sh script. When I try to run it, it gives me the following error message:
mod-plugin-builder has been updated to support multiple platforms
Unfortunately this requires a complete rebuild of its packages
Please delete /home/builder/mod-workdir and re-run bootstrap.sh
And when I delete the /mod-workdir/ and do this over again, I just get the same error whether I run with duo, duo x, or dwarf modifiers.
If any kind soul would be willing to offer some guidance, I would be endlessly grateful. I am sure it would be helpful for other folks as well. Otherwise, I think I will have to accept this is out of my depth and I will have to give up. Many thanks in advance.
Thanks so much for your response, Giedrius. I have successfully built the plugins using docker on a windows PC on the same network. However, I am unable to export the built plugins from the PC to the pi. I know where they need to be copied to on the pi, the trouble is getting them to the pi at all. If you have any suggestions or instructions on how to do this, it would be greatly appreciated (as far as I can see, this info seems to be missing from the original post and any replies to it).
I have also tried building the Mod Plugin Builder on the pi directly, but a) I am unsure if there is even enough space on the pi SD to do this, and b) I get the following errors when I run ./bootstrap.sh:
[ERROR] You must NOT be root to run crosstool-NG
[00:00] / make: *** [ct-ng:152: build] Error 1
and when I run sudo ./bootstrap.sh, I get the following error:
Do you have the results readily available on your Windows PC, or do they also need to be retrieved from within the docker container?
You can use scp (related to ssh) to copy files between devices. Use a command like this first, to get the .lv2 folders to the RPi:
scp -r plugins/*.lv2 patch@192.168.1.1:/home/patch/lv2/
# you may use ~/lv2 instead of /home/patch, ~ acts as a shortcut to /home/patch
# Change 192.168.1.1 part to the actual IP address of the Raspberry Pi
Search the internet for more details on ssh and scp on Windows, if you don’t have these commands already (ssh is even included in Windows 10, but you may first have to enable some Windows Feature for it to work)
You may have to first create the /home/patch/lv2 folder on the Pi manually.
Once the plugins are on the system, it’s trivial to sudo cp -r ~/lv2 /usr/modep/lv2/ to get them where they need to be.
Yes, I was having trouble figuring out how to retrieve the built plugins from the docker container. I was also unable to successfully install the MOD Plugin Builder through docker, so I am not sure if the plugins would have worked properly, anyways.
But–I am very happy to report–I managed to successfully install MBP on my chromebook’s built-in linux (after a 2-3 hour long install process and using much of my available space). Further, the plugins I wanted to add all built perfectly. A few additional plugins that I tried adding (that were available in the MPB /plugins/package/ directory) did not build properly. The scp and the cp commands both worked perfectly for transferring the files from my chromebook to the pi then to the correct directory on the pi. The commands ended up being something like:
With the period at the end for copying all of the files in the directory/subdirectories but not the folder itself (which would not be properly recognized by modep). After rebooting the pi the new plugins loaded up and all worked perfectly. Yay! Thank you so much for your support with this, Giedrius!
@Paul if I select helm.lvr2 in MODEP it works!, but it breaks the GUI. The click-zoom is not working anymore and it is not possible to move other plugins around.
You can find composite images of the 53 GUIs here.
Zynthian is up to about 978 lv2s, some hundreds without GUIs. (Reviewing each is becoming time consuming)
I downloaded the available lv2 plugins, use your script to symlink all the system lv2.
I did the same for Zynthian plugins (symlink to).
I wanted to do the same for modgui to have the GUI, but the directories already exist (« cannot overwrite non-directory […] »). So I have many plugins available now, but many don’t have GUI (example : TAL noisemaker )…
If you could share your « /usr/modep/lv2 » folder ?
)…