|
|
Where is the plugin installed to? Is it a LV2 or VST2? If the latter have you configured Ardour to search that location? |
|
|
Hello. Yes, I have set up VST2 and VST3 folders to search, and both Ardour version 6.9 and 7.1 have the same search settings, but for some reason 7.1 is the only one that does not recognize Vital. Of course, the version of Vital is the latest version currently available. |
|
|
There should be no difference for VST3 plugins between Ardour 6.9 and 7.1 - so this is a bit of a mystery Is there any information in Ardour's Plugin Manager when you scan for the plugin? PS. there should be no need to set a custom VST3 path same for LV2 (only VST2 requires this). |
|
|
I'm sharing images from my scans with each of Ardour 6.9 and Ardour 7.1! (I've been using the VST3 version for a long time because I couldn't figure out how to get the LV2 version to work.) Ardour6.9_.png (12,130 bytes) Ardour7.1_.png (13,983 bytes) |
|
|
Select the Vital.vst3 and at the bottom the error message should show |
|
|
VST3 module-path '/usr/lib/vst3/Vital.vst3/Contents/x86_64-linux/Vital.so' [Info]: Scanning: /usr/lib/vst3/Vital.vst3 [ERROR]: Could not load VST3 plugin '/usr/lib/vst3/Vital.vst3/Contents/x86_64-linux/Vital.so': /lib/x86_64-linux-gnu/libsecret-1.so.0: undefined symbol: g_task_set_name Cannot load VST3 module: '/usr/lib/vst3/Vital.vst3/Contents/x86_64-linux/Vital.so' Scan Failed. I got the above message. |
|
|
That looks like https://forum.vital.audio/t/not-working-on-linux-libraries-are-not-statically-linked/2194/13 is back. |
|
|
I saw the page you linked to. Does this mean that the problem is on the Vital side and not Ardour? Sorry if I am wrong X( |
|
|
Yes, it is a problem with Vital not being statically linked. Consequently, it clashes with some hosts, because they both use different versions of the same software libraries. Plugins should always be statistcally linked. |
|
|
Understood. Thank you very much for your kind attention! |
- Anonymous
