[gmpi] Re: Decision time: 8.1

Looking good so far Tim.....

> Because there are likely to be more than a single interface for a
Parameter
> (e.g. GUI and motorized MIDI control), the current state of a Parameter
must
> be sent to all listeners when that state changes.
>
>    "A Parameter can have multiple listeners, which are notified upon state
>    changes."


Yes, but....There is the question: Is this better handled by the host, or by
the plugin?

Can I sugest a simplification?

Only the host can get/set the parameter.  From the plugin's point-of-view,
it dosn't have multiple listeners.
  BUT, the host can then expose that Parameter to multiple devices (A
hardware controller plus a On-screen Slider plus a Controller automation
track etc)....

In other words: Yes, a parameter has multiple listeners, but the complexity
is handled on the host-side of the interface.
  So the plugin is simple, and the host is complex (well a little).

You also avoid having to decide up-front "What is a listener?", I mean what
if we want to have the User Interface running on one machine, and the plugin
on another? , that would involve quite complex remote proceedure call code
or whatever.  Keep the plugin simple, but allow the host writer to provide
the plumbing.

Having all parameter changes go via the host also makes recording and
playback of automation easier.

Best Regards,
Jeff


----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: