LV2, when?

[dromer]

^_^

[jpcima]

It's not on focus atm, but also I'm not very satisfied with the state of the current LV2 wrapper for JUCE. Is it for MOD devices specifically?

Just off the top of my head

• plugin has 400 or so parameters, the LV2 control ports don't scale well. It slows down Ardour a lot; this needs patch parameters, which wrapper does not have
• patch parameters are not fully featured in LV2 (no parameter enums, no grouping, etc)
• needs parameter automation from plugin to host (delay syncing on tempo change)
• wrapper doesn't support denormalized parameter ranges

[falkTX]

There is a request for official JUCE LV2 support here https://github.com/juce-framework/JUCE/issues/123

[jpcima]

As a note, for this plugin, I'd rather keep the quality uncompromised rather than use LV2 specific workarounds. If needs are not met, I'll rather stick to VST (can provide VST2)

It's the LV2 checklist so far.

• [ ] control port change notify / not polling parameter changes (no solutions)
• [x] control port change request (kxstudio extension)
• [ ] denormalized parameter ranges (need support, fork or official)
• [ ] cmake support (PR or official)