On Mon, Sep 2, 2019 at 11:26 PM Markku Tavasti <[email protected]> wrote:

> On 3.9.2019 1.13, J. Liles wrote:
> > LV2 support was not missing in the first place due to lack of
> > development resources. It was intentionally omitted because LV2 does not
> > align with the goals of the project. In short, LV2 is a comparatively
> > heavy-weight and heavy-handed dependency, but doesn't offer much, if
> > anything, over LADSPA (unless you count hype as a pro). I see LV2 in the
> > same general light as systemd, if that clears matters up any.
>
> That may be true if looking just LADSPA vs LV2 specs, but I don't see
> that as correct point of view. For end-user relevant thing is 'can I use
> the plugin I want' and without LV2 support, answer may be 'no' because
> many great plugins are LV2. Sure, goal of non is to be light as
> possible, but maybe this goal might be reconsidered. Computers are
> evolving, and more memory and cpu power available for everybody.
> Computers that were mainstream at time of when non started are mostly
> now out of order.
>
> If LV2 would be added as compile time option, then it would be still
> possible to build without extra footprint.
>
>
I have never had a use for LV2.  There are many things which are convenient
for end users but cross purposes with reasonable technological and
philosophical goals. Users love highly integrated, monolithic proprietary
software from iconic brands, for example. By using Linux we are already
"buying" into a system that is opposed to that kind of thing. Adding LV2 as
a compile time option would mean that it would not be tested or maintained,
as, again, I don't use LV2. Believe me, it isn't as though I haven't
considered this. Any solution begins to look a lot like what I don't like
about LV2 in the first place, which involves unnecessary layers of
abstraction. I even worked on my own plugin standard for a while, but I
decided I didn't want to follow in the tracks of LV2 and complicate
everyone's life with yet another format. The fact is: LADSPA may not be
great, but it's what we've got and it's better than LV2. There aren't
enough resources in the community to maintain all these different plugin
formats. If you need LV2 that badly, then just use a different mixer or
apply the patch yourself or take on the massive effort of fixing the mess
that the introduction of LV2 created and make everything compatible and
maintainable again.

Reply via email to