Re: [linux-audio-dev] RFC: Disposable Soft Synth Interface

[Chris Cannam] the header looks OK to me, reusing ALSA and LADSPA is a nice idea indeed. however i'm a bit uneasy about the configure() method of the plugin and its implications. a couple of points: * how does the host know valid "key" parameters for configure()? * if i'm right in assuming that configure() is meant to receive data file locations (".sf2", ".pat" etc) as well as other vital instance options ("polyphony", "12" or so), it becomes hard for the host to decide what kind of control to show (file selection, text entry, slider, knob, int switch etc.). * what does configure()'s (char *) return value indicate? * can you give some reasons why the host should keep track of the key<->value pairs previously given to configure()? i'd rather the plugin provides some means of retrieving the current configuration, maybe this could help answering the first * above. i've not found any satisfying answers to these questions in both RFC and example host, can you help me out? tim