On Tuesday 11 February 2003 16.11, Laurent de Soras [Ohm Force] wrote: [...] > > > - Communicates with the DSP part via the host, which is > > > an arbiter for concurrent access to parameters. > > > > I think that the OS would be a better arbiter. This would allow > > running=3D20 the GUI and DSP components in separate address spaces, > > computers, etc. > > There are not only DSP and GUI, but we thought about multi-client > issues (many people trying to change a single parameter at once). > This is also related to token. We wanted in PTAF to prevent > the GUI to control directly the DSP parameters, as it is > done in VST for example. Instead, assume GUI -> Host -> DSP. I've considered that as well. The way it would be handled by XAP is=20 connecting all GUIs to the same host, and either give them=20 priorities, or just "last activated output takes control". It doesn't=20 really matter how many GUIs (or other senders - the automation=20 sequencer would be one) there are; the same system still works. //David Olofson - Programmer, Composer, Open Source Advocate =2E- 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 -' --- http://olofson.net --- http://www.reologica.se --- ---------------------------------------------------------------------- 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