On Sat, 30 May 2009 18:36:05 +1000 Fraser <fraser(a)arkhostings.com> wrote: Great, I'm sure a lot of people will like the GUIs, these are the fanciest LV2 GUIs I've seen to date. If you don't mind I'll package them for AUR as soon as I find time, so tomorrow or maybe today. Best Regards, Philipp

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Philipp, hollunder(a)gmx.at wrote: Sure, no problem. BTW I've got a point release coming up to deal with any issues that arise from the initial release. This will probably be out in the next week. I don't mind if you wait for that one. all the best, Fraser

On Sat, May 30, 2009 at 6:57 PM, Fraser <fraser(a)arkhostings.com> wrote: I am using ardour-i686 2.8, built from revision 4918 from the debian multimedia repositories, the version for debian lenny. stdout and stderr give no mention of a slv2 gui, perhaps I missed a compile flag or ardour 2.8 does not do the plugin GUI's.

On Sat, May 30, 2009 at 7:25 PM, Fraser <fraser(a)arkhostings.com> wrote: calf is not available for debian, even with the multimedia repositories, and will not build from source because of a lack of any libjack.la file, I built ardour3 but the latest version crashes when creating a session. Maybe eventually I will either build my own jack and be sure to create libjack.la, or build my own ardour2.8 so I can double check that lv2 gui support is built in. I am kind of done messing around with software for today though.

Chris Cannam &lt;cannam(a)all-day-breakfast.com&gt; writes: There is "external UI" extension that allows plugin to launch the GUI in separate process. -- Nedko Arnaudov <GnuPG KeyID: DE1716B0>

Chris Cannam &lt;cannam(a)all-day-breakfast.com&gt; writes: Yes, external UI extension is based on the UI extension that is used by gtk ui extension. gtk ui extension just defines that UI handle is a gtk widget. Nothing more. External UI extension defines that UI handle is an object that basically adds the hide and show methods. Implementation of show method can start the GUI process and setup IPC with it. The DSSI-like universal "wrapper" code that is meant to be used for "adjusting" DSSI plugins to LV2 world does what a DSSI host does. Invada plugins don't have external UI. If you are going to add LV2 support to Rosegarden I'll add external UI support to Invada. I promise. -- Nedko Arnaudov <GnuPG KeyID: DE1716B0>

Chris Cannam &lt;cannam(a)all-day-breakfast.com&gt; writes: If they are prepared to do DSSI like stuff (the only alternative we have ATM), they can reuse the DSSI-like universal "wrapper". The code needs only two defines, UI_EXECUTABLE and UI_URI. If they are not, then maybe they are looking for in-process UI extension that is toolkit independent. I have idea about cairo UI extension but it will require abstracting mouse and keyboard events. Also it will force plugin authors to use some kind of [custom] widget toolkit based on cairo. -- Nedko Arnaudov <GnuPG KeyID: DE1716B0>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Chris, Chris Cannam wrote: Well my motivation was pretty selfish I guess. I pretty much limited myself to extensions on this page: http://lv2plug.in/spec/ rather than this one: http://lv2plug.in/docs/index.php?title=Main_Page as I figured they'd have the widest adoption and thus my plugins would run in the most hosts as intended. My main concern was compatibility. It wasn't that I thought the time investment in developing plugins using External UI Extension was too high, I just figured it was better spent on using what I can see is already utilised. That being said I'd much rather have a generic solution to UI's than a toolkit specific one, and for exactly the same reason (host compatibility). If, several months ago, I'd found myself having to choose between two extensions for UI I would have gone for the External UI as they both had the same learning curve (to me). regards, Fraser