Consider End Binary Distro of LV2

[baconpaul]

The LV2 with the community fork has several bugs. We keep getting reports like this:

so lets stop the binary distribution of it at least, since it seems with juce 7 the community juce 6 fork is no longer actively maintained.

[haenkel]

Not enough time to create anything pullrequestworthy but I quickly tried something and thought I'd share it. If I do something like this: https://github.com/haenkel/surge/commit/899bacb54899ce9c5854c56fa300e5586a933261 then patches seem to (re)load correctly in all formats for me. (haven't tried ardour but same happens in reaper)

[baconpaul]

So that just forced things to load twice right?

[haenkel]

simplified the above example but yes it does that

[dvzrv]

so lets stop the binary distribution of it at least, since it seems with juce 7 the community juce 6 fork is no longer actively maintained.

JUCE 7 has native support for lv2 :)

[baconpaul]

Yes I know. It doesn't seem to work quite properly for us when we check in the hosts that support it; but also we are on juce 6 still!

[baconpaul]

or more accurately: a version of juce 6 with some accessibility patches which are critical so moving is a pain.

you can build surge today with juce 7 if you want and get an lv2. this is just about whether we should continue to ship a binary built with the community build.

[mkruselj]

JUCE 7 has native support for lv2 :)

Yep and LV2 produced by JUCE 7 doesn't work in Reaper, for example.

[baconpaul]

meh lets not change anything for 1.2

[baconpaul]

Done