[gmpi] Re: Topic 4: Host Interface

> 1.  Are plugins run in-process or out-of-process?
 
i agreed with all. in-process seems a good starting point. and proxies levels 
between a 
in-process plugin and out-of-process plugs can surely be written after.
the only thing is, providing out-process plugins, sure we have a more system 
based
specification, that would lead to a better app2app communication. 
 
> 2.  What kinds of special needs are there in events to/from a plugin?

events should cover the more possibilities we can.
events like parameters, midi/notes, timecode, transport have to be provided.
 

> 3.  Is the host a plugin too? 
 
yeah. i agree with laurent.
 

> 4.  Can the host be a chain of simpler plugins (sequencer, timeline,
> automation)?
 
this is sure better. i really like this idea, so one can even simple provide 
new versions of
some part of the host as separate plugins. each one interacting. think of a 
plugin for controlling
a transport, that starts a timecode provider plugin, connected to a sequencer 
plugin that sends
midi notes to other synths plugin that pass thru effects plugs and finally go 
to a audio driver out plugin
( i'm really fond of modular point of view, since i find myself better, with 
better possibilities to interact with. if
you simply do not want to provide your user a "modular" view, simply construct 
your non-modular host
of "hardwired" plugins and provide a fixed interface to that ).
i know the fact of having all in plugins ( especially for drivers and 
controllers/proxies ones ) could not be easy
to implement and to handle. but i see in this the direction of gmpi, its future 
essence. if all remains like before
gmpi imho is like another plugin spec that do not offer anything new, anything 
better than before.
i want everyone think on this point of the topic. i really want to see complete 
modulars virtual studios. cause one is
in studio with some players and needs a pianoroll sequencer ( plugin ), another 
day is playing a live act
in a club and needs a pattern sequencer ( plugin ) or both, but he would like 
to use in both environment the same
audio mixer ( plugin ), everything in the same rock solid host app, handling 
scheduling/interaction of all these
events/streams - generators/processors. 

> 5.  Does the host interface provide transport control, UI updates, track
> information?
 
i think these should be leaved to the single plugins.

lou

Other related posts: