9 Feb
2003
9 Feb
'03
12:41 p.m.
On Sunday 09 February 2003 14.29, Steve Harris wrote:
[...]
There is also the instruction cache to think of.
Practical
experience suggests that suddenly waking up a chain of plugins
causes a spike of CPU load which settles down. It may be possible
to moderate this with carefull coding however.
Well, you *could* have run() calls pull the "full on" code into the
cache every time they're called, whether or not the code is actually
executed. Obviously, you can do it with some of the data as well, but
unless your effect is guaranteed CPU bound, you probably shouldn't do
too much of that, or it'll be just about pointless to care about
silence at all.
Anyway, this doesn't sound like something that belongs in XAP. If
you're nervous, just have the host kill silent buffers (rather than
turning effectively inaudible buffers into silent buffers), and all
plugins will run full on all the time.
//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 ---