Subject: [linux-audio-dev] Communication between LADSPA GUI and host
From: Richard W.E. Furse (richard_AT_muse.demon.co.uk)
Date: Fri May 26 2000 - 00:27:23 EEST
Leaving aside the choice of the actual graphical toolkit in use (custom C,
custom XML, direct Gtk or whatever) and the exact threading-relationship
between GUI and host, how's this for a scheme?
(1) LADSPA DSP plugins remain unchanged.
(2) LADSPA GUI plugins may be contained in the same library or in a
separate one. LADSPA GUI plugins (when present) relate to a particular
LADSPA DSP plugin. The host may choose not to use the GUI plugin. The GUI
plugin can work independently of its corresponding DSP plugin (and vice
versa).
(3) The LADSPA GUI plugin provides the following core functions, where port
indexes correspond to the port indexes on control ports (in & out) on the
corresponding DSP plugin:
LADSPA_Data getControlValue(LADSPA_GUIInstance instance, int port); [for
use with input ports]
void setControlValue(LADSPA_GUIInstance instance, int port, LADSPA_Data
value); [for use with output ports and automated input ports]
void setControlLockState(LADSPA_GUIInstance instance, int port, int
locked); [for use with manual/automated input ports]
There are logically equivalent alternatives to this that may be more
efficient (e.g. using a connect_port(), is_dirty(), sync() etc) - I'm
interested at this stage in an unrefined simple model.
-- Richard
This archive was generated by hypermail 2b28 : Fri May 26 2000 - 04:07:39 EEST