@snailerotica oh wow you found something I was not expecting. the image renders incorrectly for you very odd 🤔

as to what shouldn't be working, let's say at some point Ardour removed support for gtk-based plugin UIs 😉

@snailerotica and I think I know why the 2nd image is rendered wrong, my theory is because of bad image down-scaling.

I can see the artifacts from a fast but bad resizing, where the algorithm just skips pixels to match the target size.

Seems to me the image has exactly the black lines on the spots where this algorithm would show a pixel/line. A proper one would do an average filter so each downscaled pixel takes into account surrounding pixels too.

@snailerotica @falktx At least Invada’s spectrogram was correct . Calf’s display was entirely useless showing incorrect data. Good riddance.

@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...

@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.

@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...