Let's play a little game...
What is working in this picture that shouldn't? Can you tell?
@x42 for legacy reasons basically.
the lack of UIs for a few plugins on recent updates has been quite painful for some users.
this UI stuff is out-of-process so it should be safe to use. we lose the instance-access parts, but I always disliked UIs and DSP in the same process anyhow.
also got a few more working now...
@x42 I see the need for this on systems still running current stable Debian but wanting an updated Ardour. It gives a bit more time for people to move from it, rather than just removing the UI support outright.
but also, it is fun :)
I already had all pieces for UI bridging and IPC in place in other tools, so making this was quite quick.
and potentially serves as a way to allow other kinds of UI bridging - think webkit that relies on gtk3 or QtWebEngine - but for LV2 UIs...
@falktx we’ve been telling dev (and users) since 2012 to not use GTK or QT based plugins. At some point we have to make a cut. 2024 seemed like a good year. Especially since Debian is about to drop GTK2. So those plugins won’t be packaged anymore to begin with.