[LAD] [ANN] LV2 beta3
steve at plugin.org.uk
Thu May 10 15:21:12 UTC 2007
On 10 May 2007, at 16:10, Lars Luthman wrote:
> On Thu, 2007-05-10 at 16:05 +0100, Steve Harris wrote:
>> On 10 May 2007, at 14:51, Thorsten Wilms wrote:
>>> On Thu, May 10, 2007 at 12:53:44PM +0200, torbenh at gmx.de wrote:
>>>> the problem will be rather: why has this plugin a GUI in ardour and
>>>> ingen and not in qtractor.
>>>> while this other plugin has a gui in qtractor and non in ardour and
>>> So how can the toolkit issue be adressed?
>>> Could there be something like GUI hosts to assist plugin hosts
>>> by running plugin GUIs that use another toolkit?
>>> What does DSSI do?
>> DSSI runs the plugin UI in a separate process with its own X
>> connection. It's not ideal, but it works OK. The biggest problem is
>> that it makes it trickier for the host to re-parent the UI - I don't
>> know if anyone's made that work.
> Re-parenting can be done using the XEMBED protocol, implemented in
> GTK as the Socket and Plug widgets. You need to give the Socket the
> window ID of the Plug or vice versa, so to do it in DSSI would
> require a
> (trivial) extension of the host <-> GUI communication protocol. I did
> some simple experiments with it earlier and it seems to work fine.
OK, well that's cool then.
It would still suck on windows because processes are very expensive
there, but that doesn't concern me too much; X servers are not that
common on windows anyway, so hypothetical DSSI/LV windows UIs could
use a different mechanism.
More information about the Linux-audio-dev