Its a bug in the latest guitarix release, introduced when we switch to a
newer waf version to allow building with python3. It's fixed in our
repository already and will be fixed for you within our next release.
As it is just a warning, you could safely ignore it (for now).
Am 11.04.20 um 22:17 schrieb Tim:
Hi. I've been getting errors with this plugin for some time now.
lilv_world_load_file(): error: Error loading file
`file:///usr/lib64/lv2/gx_colwah.lv2/manifest.ttl'
error: failed to open file /usr/lib64/lv2/gx_wah.lv2/gx_colwah.ttl (No
such file or directory)
It looks like an oversight bug, missing the manifest.
See if the author chimes in here...
Tim.
On 4/11/20 11:58 AM, Jeanette C. wrote:
Hey hey,
I ran into some trouble with LV2 plugins and Ecasound, which uses
liblilv. This was exemplified - in my case - with gx_colwah (from the
guitarix suite). Ecasound tried to load the file manifest.ttl.
I noticed that gx_colwah.lv2 didn't contain a manifest.ttl, but a
gx_colwah.ttl .
Would the two fulfill the same function? Is it a more recent part of
the standard to allow/force a file like plugin_name.ttl instead of
manifest.ttl.
Could all this be an issue within liblilv (0.,24.6 installed here) or
would it be the host application. i.e. Ecasound which enforces that
behaviour?
Apologies for the probably overcomplicated questions, but my
understanding of the LV2 format is uite limited.
Best wishes,
Jeanette
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
https://lists.linuxaudio.org/listinfo/linux-audio-user
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
https://lists.linuxaudio.org/listinfo/linux-audio-user
