On Thursday 19 December 2002 04.25, Tim Hockin wrote: > > So, the actual connections don't have much to do with snooping at > > all, but rather look something like this: > > <snip nice ascii diagram> > > > That is, the sequencer sends data to the synth *and* the synth's > > GUI. This is what makes the GUI track the automation. > > > > When automation is on "record", the sequencer takes input from > > the GUI as well, and basically records it and forwards it to the > > Synth at the same time. > > I'd call that snooping. And if a plugin controls another plugin, > the host has to snoop those events, too, or the UI is out of sync.
My point is that it isn't really snooping from the API POV. You're basically inserting Y splits in the net, sending the same events to two places. The host should never mess with, or try to understand these events; just make sure they get to both inputs. //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 ---
