<html><body><div><div>I'm currently investigating adding LV2 support to a plugin framework. For the<br>most part, the process has been very straightforward and enjoyable, thanks to<br>the documentation and also to the abundance of open-source plugins and hosts<br>that are available for testing. It's clear that a lot of work has gone into the<br>LV2 ecosystem, so thanks for that!<br><br>Unfortunately, I've run into a few issues that I'm not sure how to resolve.<br><br>Would anyone here be able to answer these questions?<br><br>- Firstly, I have some questions about parameters. Plugins built in the plugin<br> framework currently have VST-like parameters which can change themselves at<br> any time. It seems that such parameters should not be exposed as control<br> ports, because hosts expect that control port values will never be changed<br> directly by the plugin. The 'patch' extension seems like a better fit, but<br> it's not clear how to replicate some features of control ports with the patch<br> API. Specifically:<br><br> - The 'touch' feature of the UI extension expects that each parameter<br> corresponds to a unique port, but the patch API uses a single port for<br> multiple parameters. Is there a convention for communicating 'touch'<br> information with the patch API?<br><br> - Some of the PortProperties in the core spec would be useful to apply to<br> parameters, rather than individual control ports. Is it valid to declare<br> `ScalePoint`, `enumeration`, `integer`, and `toggled` on a Parameter<br> rather than a Port? If not, is there some alternative way of conveying<br> this information?<br><br> - My plugin framework allows defining parameters with custom functions to<br> convert to/from string. This is a little more flexible than the LV2<br> system, which provides the host with parameter ranges and units, and<br> leaves all the string conversions to the host. Is there any way to allow<br> an LV2 plugin to format its own parameter value strings?<br><br>- I also have a UI-related question: When a UI requests a resize via the resize<br> struct, should the returned size incorporate the scale factor passed as an<br> option to the UI? That is, is the requested value in pixels or points? I<br> could work this out empirically by testing some plugins which implement<br> 'scaleFactor', but it'd be nice if this was documented in the spec.<br><br>I hope that's not too much all at once. Thanks for reading!<br><br>Reuben<br></div></div></body></html>