Replies: 1 comment
-
Direct LV2 export is not really maintained anymore. Can you possibly thy the faust2juce way qnd create a LV2 plugin form there ? Another way is Fadeli, which is probably faster to make work. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I coded a simple 5 band EQ, tried it in Faust IDE and it works just fine. Then I exported it for linux lv2-64bits, lv2-64bits-qt4 and lv2-64bits-qt5 to try each of them. I took the folder that contains all the files (.ttl and .so) and moved them to corresponding directory in linux where every other lv2 plugins reside. I tried every version of my exports (plain, qt4 and qt5) and none of them worked in MODEP. MODEP-GUI can list my plugin however its thumbnail says "no interface available". When I try to load the plugin on the scene, I get "error loading plugin". So I checked other working MODEP LV2 plugins to see its file structure. The structure in the folder is,
-plugin.so
-plugin.ttl
-manifest.ttl
-modgui.ttl
-modgui (folder)
--icon-plugin.html
--stysheet-plugin.css
--screenshot-plugin.png
--thumbnail-plugin.png
--knbos (folder, containing knob images)
--pedals (folder, containing the background image)
--utils (folder, containing other images)
So I decided to use an existing LV2 modep plugin as a preset, I overwrited the .so file with my .so file keeping the original name. I adjusted every ttl file and tried again. No luck, still getting the same error, "no interface available", "error loading plugin" in MODEP-GUI. I am guessing the root of the problem is in the .so file. Any advice?
Any future development plans for modep-gui?
Beta Was this translation helpful? Give feedback.
All reactions