Most developers who provide multiple plugin formats using a framework which provide the API access to the different plugin formats. That means when write a plugin a developer didn't care if it is for LV2, vst3, vst, clap or even AU. It's the framework which does the lifting job.
And here is the culprit. Juce, for example, have a very crap implementation of the LV2 API and that's why juce based LV2 plugs tend to crash while vst works flawless. There is not much a developer could do when using such a framework.
DPF does a much better job on this and provide very good and stable lifting to all plugin API's, but DPF didn't provide a GUI toolkit, so a developer must wrote it's own widgets which lead to a lesser use of DPF. But when done, all plugin formats working stable.
When write a plugin for just one plugin format, likely the developer knows enough about the used plugin API to make it work correctly, bee it vst, LV2, clap or AU. The difference is just knowing the API.
So, to answer your question, no, LV2 is not more difficult then vst3, you just need to know how it works. While using a plugin framework you didn't need to know anything about the used plugin API.
Statistics: Posted by tramp — Sun Jun 02, 2024 6:24 pm