Re: [DSSI] xsynth commit

[Chris C. <ca...@al...>]

On Thursday 18 Nov 2004 09:20, Chris Cannam wrote:
> dssi.h does say (and has always said):
>
>      * A plugin is not required to select any particular default
>      * program on activate(): it's the host's duty to set a program
>      * explicitly.  The current program is invalidated by any call to
>      * configure().
>
> So perhaps it's simply the wrong thing to try to set any program or
> port values from either instantiate or activate.  The host should
> give the ports their published defaults; if the user selects (or
> selected on previous load) a program, then the host will select that
> too, after the ports have been connected.

Although, given the notorious inadequacy of LADSPA port defaults, this 
isn't likely to be very satisfactory either.  The last thing we want is 
to encourage plugins to start up in a stupid-sounding state.  Perhaps 
that is the fatal flaw in my argument about activate: that a plugin 
might have a legitimate need for a place to do some first-time setup 
that it can't actually do in instantiate.

Perhaps that does imply a need for another API call.  I think I'd like 
your view on how Xsynth, Hexter etc would actually cope with a regime 
like the one I described in the email quoted above, first, though.


Chris