[gmpi] Re: Req 76,78

  • From: "Angus F. Hewlett" <angus@xxxxxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Mon, 07 Feb 2005 11:22:42 +0000

Jeff McClintock wrote:

Cleanly separating GUI and Audio code is a natural consequence of good design. If good design to you is "completely useless", stick with VST, you won't be dissapointed.

This is true... but sending all GUI<->Audio communication through a single central switchboard strikes me as somewhat restrictive.

Thinking of big and complex plug-ins... yes, if we want, we can have the host mediate everything, but it gains us relatively little - most users will not actually be able to work with the automation data that's generated, as it'll be too complicated for them to understand. On top of that, both our GUI and Audio code may become significantly more complex, and will have to have extra bulletproofing because all of a sudden the user is given the ability to generate junk data on any of our communications pipes :-/

That said, maybe GMPI is best focused on getting logically simple plug-ins to work well, and JACK (or something like it) is a better way to integrate behemoths such as DR-008 or Kontakt.

Regards,
      Angus.

--
=========================================================
Angus F. Hewlett, Managing Director (CEO)
FXpansion Audio UK Ltd - http://www.fxpansion.com
Registered in the UK - #4455834 - VAT: GB 798 7782 33
========================================================= 


----------------------------------------------------------------------
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: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts:

  1. Home
  2. gmpi
  3. Archive
  4. 02-2005