Are there any more examples of LV2 plugin configs available, or a guide on writing them - I cannot for the life of me get LV2 plugins to run on ELK (Hifiberry Pi) at the moment, I have looked at the synth and play examples but i cant seem to make the LV2 work.
I am asking for a guide / documentation for LV2 specifically - I think I may be to do with the uri / path but where do I find the uri ??
I am using the complied for elk plugins from git hub, i simply want to run them and check cup usage at idle ,under load etc.
I can do this for vst plugins but seem to be hitting a brick wall with lv2 for some reason?
LV2 is a very particular plugin format, there’s many things that are different between LV2 and other formats.
It’s worth trying LV2 plugins locally on your desktop machine, and loading them into a host, just to get used to how they’re found and addressed - then you can move to Sushi, and on the RPi.
Most importantly, they are not addressed by a path on the disk to the file as is the case with VST’s, but by a “uri”, as you’ll see in the two example configurations we have in the sushi/misc/config_files folder.
You will see the uri’s of plugins available on your system by typing lv2ls on the terminal, assuming the lv2 frameworks have been installed on your computer. It should be available on the RPi, what it does is look for plugins placed in the paths of the machine specified in the LV2_PATH environment variable, and list them.
If when typing lv2ls, the uri of the plugin you want to load is not listed, then Sushi will not be able to load it either.
but Lv2ls only shows the core plugins included in Elk os, none from this pack -have i missed an instillation step somewhere in the middle -I’m simply trying to load and test these plugins, measure their cpu usage etc so i can compair the results of various plugins.
i understood tha these were already cross compiled for elk s im now confused.
Indeed while those general instructions apply to the VST2/3 plugins, they do not apply to LV2 - that folder is not in the LV2_PATH environment variable, so lv2ls will not find them.
It’s worth clarifying this distinction for the LV2 plugins in the README of the elk-plugins repository, thank you for pointing that out!
Either precede the command to run sushi with a line expanding the LV_PATH variable to include a path in your user folder which includes your plugins, or place them in a path already present in LV2_PATH.
In the former case I’d recommend you create a folder dedicated to LV2 plugins, to keep them separate from VST’s.