[gmpi] Re: Req 76,78

  • From: Mike Berry <mberry@xxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Thu, 03 Feb 2005 22:02:15 -0700

Didier Dambrin wrote:

>plugins can already put their UI in another process if they want, they >don't

need the host to help them communicate with themselves

users can't put the DSP part of a plugin on another CPU if the GUI
expects to run there as well.

yes you can. The simple fact that the UI & processing are in separated *threads* means that a dual CPU system will spread both CPU's on timeslices of both threads at the same time. Under windows that is.

I think that you are missing another very very important aspect of having the GUI communicate with the DSP through the host. It gives the host the ability to record the entire communication between the GUI and the DSP, with the opportunity to then display that in some sort of editable form for the user. The fact that a lot of VST plugins GUI-DSP links are completely invisible to the host means that the automation capabilities of VST plugins are all over the map, and a major headache for host developers.

Mike Berry
Adobe Systems

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: