5 Feb
2003
5 Feb
'03
12:27 p.m.
On Wednesday 05 February 2003 16.37, Steve Harris wrote:
On Wed, Feb 05, 2003 at 01:40:59 +0100, David Olofson
wrote:
Yes, but that's a plugin specific exception, I think. There's an
important difference: A DSP plugin will run in RT context, which is
not required for a "local-half" GUI plugin. Consequently, one have
more freedom, both in terms of basic "local-half" implementation, and
choice of IPC methods for the local/remote connection.
//David Olofson - Programmer, Composer, Open Source Advocate
.- 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 ---
Well, you might still be able to comment on an
idea: Splitting up
the GUI in two parts; one that runs in the same process as the
DSP plugin, and one that runs in another process, possibly on
another machine. This would allow the "local" part of the GUI to
interact with the DSP plugin more effectively, while still
messing with your favourite toolkit in another process.
Dividing the rendering is effectivly ehat happens, eg. the DSP part
does the meter maths and outputs a control signal for the
amplitude.