jonetsu wrote:Yes and no. Commercial plugins tend to perform in a similar way on all DAWs. When a commercial plugin does not work in a DAW, it's immediately the DAW that is concerned. The way commercial plugins are made might be a good hint on assuring interoperability. After all, they are built to run as good as possible. To have as smooth of a commercial venture as possible, to minimize support issues and increase good reputation.
The main problem of the LSP UI is that it's currently implemented using GTK2. This already has problems with JUCE-based hosts. Also as I see it has problems with Bitwig. Sadly but I have not so much time to port all widgets to pure X11 implementation. But first tests showed that pure X11 implementation works well on JUCE and probably will work well on Bitwig.
Anyway, the self-containtment of the DAW does not exclude that fact that DAWs can violate X11 protocol (like it's done in JUCE) or VST protocol (like it's done in Reaper with the UI).
Currently I can not say what's happening between Bitwig and LSP UI because Bitwig doesn't forward stderr to the console (as other hosts do), so I need some time to think about how to capture plugin's output. The same I can say about X11 events that should be immediately passed to the UI and processed by the GTK core.