Though it is still in a state I consider alpha at the moment, everything that is crucial is implemented:
from audio, midi, time position, parameters, programs, state, latency and gui.<br/>
Not recommended to release anything based on this yet, as there are memory leaks and the GUI only works on Linux at the moment (and known to break REAPER due to not plugging into the host runloop yet).
This VST3 implementation uses
<a target="_blank" href="https://github.com/DISTRHO/DPF/tree/develop/distrho/src/travesty">custom C-compatible API headers</a>
instead of the official SDK, so that we can have commercial plugins while not being tied to Steinberg and its restrictive licensing.<br/>
There is a lot of boilerplate code to implement for stuff that the SDK typically does for you, and it is still pretty unclean, but works for now for testing.
Worth noting that there is a clear DSP / UI separation for this VST3-compatible DPF implementation.<br/>
Instead of the UI having direct access to the DSP side and just calling functions, everything is passed through a VST3 "connection point" as messages.<br/>
There is something in place to support hosts that do not provide the "connection point" interfaces, so everything still works there too.
I expect to finalize the VST3 support already in October as there does not seem to be any technical limitation or blocker,
it is just time needed to implement all the things.<br/>
Sadly VST3 only officially specifies support for Linux, macOS and Windows.<br/>
DPF can build for more systems than just these 3, so I
<a target="_blank" href="https://github.com/steinbergmedia/vst3sdk/issues/86">made a question/request upstream</a>
for how to tackle the issue.
<h3>Other DPF updates</h3>
In other DPF news, I began experimenting with supporting