Subject: [Fwd: [linux-audio-dev] ladspa plugin GUI proposal]
From: Dave O'Toole (dto_AT_qwsi.net)
Date: Thu May 25 2000 - 01:14:33 EEST
Dave O'Toole wrote:
>
> Paul Barton-Davis wrote:
>
> > sake. There is no way to connect anything to them and expect any kind
> > of notification that they've changed. This is why your point about
> > having the host construct and run the GUI is well-taken: it can both
> > drive the port values when relevant GUI events happen, and drive both
> > the GUI and the port values in the case of automated playback of
> > events.
>
> I agree with you here about host-constructed and host-managed interfaces
> (which might be graphical.) This is the approach I'm using for GNU's
> OCTAL system. Plus, given the thorny synch issues that would be involved
> in having plugins with their own little event loops (to speak nothing of
> efficiency if you *do* get it right) as well as other problems, I don't
> know how this could be made to be a workable solution.
>
> Someone mentioned the beauty of many VST interfaces. I'm of the opinion
> that the "chrome" factor is of zero practical importance. Am I nuts, or
> is it really so important to be able to make 3-d chrome interfaces for
> plugins? What if the user wants something different? What if the user is
> blind? My thinking is that it's already secondary if it doesn't end up
> on the CD you make with it. The primary concern should be user control
> and audio quality.
>
> --
> @@@ david o'toole
> @@@ dto_AT_gnu.org
> @@@ www.gnu.org/software/octal
-- @@@ david o'toole @@@ dto_AT_gnu.org @@@ www.gnu.org/software/octal
This archive was generated by hypermail 2b28 : Thu May 25 2000 - 05:03:46 EEST