9 Dec
2002
9 Dec
'02
10:38 a.m.
On Monday 09 December 2002 15.16, Steve Harris wrote:
On Mon, Dec 09, 2002 at 01:49:38PM +0100, David
Olofson wrote:
If the hosts dont implement it, neither will the plugins... viscous
circle.
Well, let's put it as simple as this:
If your plugin has controls that may refuse certain values
within the valid range, they *must* tell the host when this
happens. Otherwise, automation and preset save/restore will
most probably not function properly.
Now, whether *hosts* care to implement it is another matter, but I
would think that most hosts would, as you can't have preset
save/restore without it.
Either way, this might just be another thing that can be built into
the host SDK lib, maybe in the form of a default handler for
plugin->host events on Master Event Ports.
//David Olofson - Programmer, Composer, Open Source Advocate
.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`---------------------------> http://olofson.net/audiality -'
.- M A I A -------------------------------------------------.
| The Multimedia Application Integration Architecture |
`----------------------------> http://www.linuxdj.com/maia -'
--- http://olofson.net --- http://www.reologica.se ---
This
sounds pretty complex. I'm not sure the hosts will be able
to reliably implement this correctly.
It doesn't have to, unless it actually cares. If you save a
preset with a "bad" value in some field, the plugin will just fix
it when you load the preset.