[LV2] Best practice to get plugins using 3rd party extensions/features to pass validation?

Hanspeter Portner dev at open-music-kontrollers.ch
Tue Jul 11 13:37:25 PDT 2017

On 11.07.2017 15:49, Filipe Coelho wrote:
> On 11.07.2017 15:45, Hanspeter Portner wrote:
>> A prominent reason are plugins using 3rd party extensions/features (e.g.
>> harrisonconsoles' inlinedisplay:queue_draw/schedule, kxstudio's
>> programs:interface, modgui).
> Hello.
> The kxstudio extensions can be found here:
> https://github.com/KXStudio/LV2-Extensions
> So they're easy to install. (copy *.lv2 bundles to LV2_PATH)
> The MOD stuff is here: https://github.com/moddevices/mod-sdk
> Easy to install as well.
> I use kxstudio & mod stuff in my plugins, and have no issues regarding validation.

I know I (as developer) can install them manually. I wanted to know something
else, though, from the user's perspective.

I'll try to rephrase...

Who's job is it to provide the 3rd party extension/feature definitions on the
user's machine?

1) it is the users job (e.g. grab the 3rd party *.ttl from the web)
2) it is the developer's job (e.g. ship the 3rd party *.ttl (or a shortened
version thereof) with the plugin)
3) it is the distribution packagers job to provide the 3rd party *.ttl via a
4) it is enough for a plugin to validate on the developer's machine
5) ...

More information about the Devel mailing list