On Wed, 2011-03-02 at 16:58 +0100, Olivier Guilyardi wrote:
NO. This is, very deliberately, not how the UI extension works.
You /can/ do this with certain extensions, but it is an awful kludge and
should not be done for fundamental communication. You can however do it
to add optional whiz-bang features (like waveform rendering) - if the UI
and plugin are in the same process - which is not necessarily true.
UI <=> Plugin communication is handled via ports via the host. This
allows many things, the most obvious of which being that whole network
transparency thing you just threw out the window ;) The other obvious
reason is that all of that "high performance IPC" stuff, which involves
multiple threads and synchronization etc, is not easy, and obviously not
something we want every single plugin and UI to have to solve
repeatedly. Host's job.
> Just an example: a compressor plugin which shows the input and the output
Plugins communicate via ports. Specifically, we need a higher level
'message' extension which logistically would function like MIDI does
now, except.. not be MIDI.
Linux-audio-dev mailing list