Subject: Re: [linux-audio-dev] ladspa GUI round 2
From: Paul Davis (pbd_AT_Op.Net)
Date: Thu Mar 29 2001 - 23:36:14 EEST
>I have been writing a message system which can deliver messages
>between processes (threads). There will be several processes in
>a wave editor and a few in the engine. Because some processes can
>be child processes and child's child processes, the message system
>should handle addressing, message interleaving and priorities. (Even
>in the case of threads and common memory, some kind of abstraction
>should be implemented, otherwise the code becomes kludge.)
>A plug-in would be one of the all child processes.
OSC handles all of this. Its written, its documented, Csound uses it.
I think we should too.
>The host could have standard services, and the plug-in should be
>able to check if they exists. For example, given an input region
>in the wave editor to the reverb plug-in, the reverb should be
>able to adjust the output region in the wave editor according
>to the reverberation time.
Thats not how LADSPA works, Juhana. If an editor is feeding an area to
a plugin, it simply calls "process()" one or more times, after
connecting the audio port(s) of the plugin to the relevant input and
output buffers. the plugin has absolutely no knowledge of what lies
"beyond" the pointers its told to write the output to.
--p
This archive was generated by hypermail 2b28 : Sat Apr 07 2001 - 15:56:46 EEST