9 Dec
2002
9 Dec
'02
10:58 a.m.
On Monday 09 December 2002 15.31, Steve Harris wrote:
On Mon, Dec 09, 2002 at 02:17:06PM +0100, David
Olofson wrote:
Why filtering? The sequencer will just send events where they're
meant to go, which means that each output may be connected to a
different port, or all to the same port, or whatever.
If the outputs are connected to different ports, the *sequencer* will
automatically perform that filtering (or rather, dispatching) for
you, without even knowing about it.
//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 -'
.- M A I A -------------------------------------------------.
| The Multimedia Application Integration Architecture |
`----------------------------> http://www.linuxdj.com/maia -'
--- http://olofson.net --- http://www.reologica.se ---
(*) One example would be if all your channels are
driven by the
same sequencer, which has only one internal loop for event
output. Then event ordering is guaranteed, no matter how many
input ports the synth has, or how things are connected.
But you still have to do the filtering, which sucks. Or am I just
getting confusd.