Subject: Re: [linux-audio-dev] ladspa GUI round 2
From: Paul Davis (pbd_AT_Op.Net)
Date: Thu Mar 29 2001 - 23:39:17 EEST
Werner writes:
> - the plugin host should be able to start the gui
Seems OK, as discussed in email between steve h. and myself.
> - the plugin host should be able to show/hide the gui
why ?
> - the plugin api should not be connected to a plugin instance
yes, agreed.
> the connection is made in the plugin host (IPC from gui to plugin)
not quite. IPC from the gui to the plugin host.
> - the plugin host should be able to drive more than one
> plugin instance with one plugin api
yes. the plugin is instantiated again, and starts a new process for a
new GUI. this is implicit in LADSPA.
> - the plugin api itself accepts parameter changes via IPC
no. the plugin API remains as it exists right now: control and audio
ports. the API (preferably OSC) allows the GUI to ask the host to
modify the port values.
as noted, this allows for automation.
> - the plugin host should be able to set the "caption" (so called
> in qt toolkit) of the gui; this is useful if you want to have more
> than one instance of gui/plugin
why ? its the plugin's fault if it calls every example of its GUI
window(s) "foobar" ...
--p
This archive was generated by hypermail 2b28 : Sat Apr 07 2001 - 15:56:08 EEST