Here’s the output of
$ sord_validate /usr/lib/lv2/…/eq6m.ttl: http://pastebin.com/q6McZjGi
Here’s the output of
@dsreyes1014: I’ve tested eq10q rc2.2 in ardour 5.4 using lilv 0.24 under last debian testing. I think that this setup is pretty similar than yours and should be able to reproduce your issue. For me, it is working fine.
According to your posts: Are you building eq10q from source? if so, which version 2.1? or last SVN?, I’m asking because 2.2 is not published yet. In fact there are some mistakes in ttl files of 2.1 version which are corrected in 2.2 release candidate (apologies for those errors). I suspect that you are building eq10q from 2.1 because of the error reported by your sord_validate has been fixed in rc2.2. Please, can you try my binary package (eq10q_rc2.2_installer.run) or the last head version of eq10q’s SVN on your gentoo packaged ardour? Keep in mind to delete every previous eq10q installation file before each new eq10q installation (to avoid a possible conflict with some path not properly updated). Let me know any progress on that.
@sapista: Is that the same binary that you posted from google drive?
@sapista: The installer script does work with the new Ardour-5.5 build on Gentoo. Thanks for this.
@dsreyes1014: Glad to hear that. So the issue is only related with 2.1 version of EQ10Q. I think I’m going to release version 2.2 in a few days because the installer scrips seams to be working for many people.
I would like to thank all people that has spent some time testing rc2.2 version. Your feedback is much appreciated.
this still works here in 2019! I instead did things slightly different by extracting the run-installer with --target and copying the appropriate plugin into ~/.lv2
I wasn’t sure what was wrong in debian’s 10 packaged eq10q as the full plugin interface was not loading… but the extracted one from eq10q_2.2_installer.run fixed it.
The compiling fails with pow10 functions – this is deprecated with pow(base,exp), – even after compilation works, the runtime does not reveal the full interface, … so the fix for me is to go with the pre-compiled bundle from eq10q_2.2_installer.run…