Documentation

[fpesari]

Hello,

I am the co-maintainer of The LV2 Porting Project, a project which aims to port as many libre plugins to LV2 as possible.
And while I am no JUCE developer - due to all the LV2-related issues with it, I simply decided to never learn using it - there are plenty of JUCE plugins which need porting out there, so I thought this module could become more popular than DISTRHO/juce, since that's a whole separate fork.

I came across jlv2 on the LV2 thread from the JUCE issue tracker (thanks for that post, by the way - it was not publicity, it was totally relevant to all users who follow that issue) and I thought, great!

The only question is:

1. For packagers, can jlv2 be used easily without having to code? (just include the module and enable it from Projucer)
2. For developers, what can we do to improve jlv2 and bring it toward fully functionality?

If there were more docs (maybe a wiki or a more detailed README.md, or a CONTRIBUTING.md), perhaps this project would receive more attention.

Another thing, I hang around some GNU/Linux audio places and I've never heard of jlv2, why don't you try showcasing it on LinuxMusicians, which is perhaps the biggest community out there for these things? If you don't want to create an account there, I can make a thread about it myself.

Thank you for this module, by the way 😸

[mfisher31]

Hey thanks @fpesari ! Yeah, JUCE won't support LV2 any time soon. As for porting JUCE plugins to LV2, these modules won't help much. They are intended to host LV2 plugins.

However, lvtk/lvtk is the place to look for implementing LV2 plugins in C++. To make it easier for porting from JUCE, I'd propose adding a new template to lvtk which essentially wraps a juce::AudioProcessor and implements the required LV2 features. Since it's JUCE and the Plugin/UI are married to one another, we're looking at having to use instance-access or external_ui which is discouraged by LV2 itself.

I vote for instance-access since it's part of the official spec. One major problem to figure out is JUCE's MessageManager... this is a singleton class can can be tricky to work with when writing LV2 plugins.

[mfisher31]

@fpesari lvtk/lvtk#42