Subject: [linux-audio-dev] Example plugin solution
From: Adam Williams (broadcast_AT_earthling.net)
Date: to syys 23 1999 - 16:08:38 EDT
The way I've been doing it for 2 years is fork one instance of the
plugin as a GUI and fork a seperate instance of the plugin for every
channel as a DSP engine. The GUI does one thing only: whenever the
user changes a widget, it sends its configuration to the plugin
server. The plugin server then propogates the configuration data to
the DSP instances. The DSP instances simply handle two events: buffer
process and reconfigure. Now you're going to need to spend some time
on the handshaking. If you want to parallelize the DSP you're better
off parallelizing at the plugin level and running each plugin
sequentially. Maybe enable the most time consuming plugins to process
multiple channels over several CPUs but make the light plugins single
channel, single processor. If you parallelize at the render level
you can't share plugins between channels or bounce tracks, pure and
simple.
--
Heroine Virtual
freeyellow.com/members4/heroine
Render the impossible into reality
This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:27:12 EST