8 Jan
2003
8 Jan
'03
5:58 p.m.
On Wednesday 08 January 2003 19.23, Steve Harris wrote:
On Wed, Jan 08, 2003 at 09:18:38AM -0800, Tim Hockin
wrote:
I dont like the fact that the id changes after the first block its
used in and that the instrument has to comminicate the internal VID
back to the host.
And (somewhat related to that), even though VVIDs come with a host
managed table of void *, int32 or whatever, it doesn't have any
issues with inter-process gateways, wire connections and the like
that any two-way communication system has. It's not latency sensitive
(obviously), and the table isn't an issue, since it's only used by
the *synth*. (The sender only uses the VVIDs, which are just indices
into the table.)
That is, if you want to talk to a remote synth, just allocate VVIDs
from the remote *host*, and everything will Just Work(TM).
(Which reminds me; the alloc_vvids() call needs to know which
receiver the VVIDs are for, obviously. The target queue as an
argument should be sufficient, as the host should be able to keep
track of which queues are gateways to remote hosts.)
//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 ---
On Wed,
Jan 08, 2003 at 12:09:56 -0800, Tim Hockin wrote:
Can you elucidate what your objections are? I've stated my
problems with VVIDs :) What is LUT? What is voice-marking? The
negative VVIDs are
valid for the duration of the block, after which they use
their new names. It seems simple to me.
It doesn't to me!