3 Feb
2003
3 Feb
'03
11:32 a.m.
On Monday 03 February 2003 15.36, Ben Loftis wrote:
Right... I'm not even sure what state we're talking about here,
but I *assume* it's basically all you need to continue playing
from where you saved the state. Freezing reverb tails and stuff?
Sounds fun but pretty useless... Might help some very special
apps - but then, will it be sufficient?
If you want to restart playback at an arbitrary point and be
sample-accurate, you must have this, right?
Nope. Sample accuracy has nothing to do with it. You'd just start
playing and make sure there are events to set the transport at the
right position before the first sample frame. (Or if you have the
plugins running all the time, you just start the sequencer, period.)
* The
"save state chunk" call seems cool, but what's
the point, really?
This could be useful for state storing in hosts, but how many
would use it? I'd certainly be reluctant to implemnt it. I think it's a good
idea (I suggested it myself a while back). The host can cache
these at regular intervals (and at the user's locate points) so you
can start playback and the host only has to preroll from the most
recent state chunk. Implementation is easy if you design for it...
just stream all your internal variables into a buffer.
So, we're basically talking about a brute-force solution to the
classic "make MIDI behave as recorded audio" problem?
It could work in theory, but what about the bandwidth required for
some plugins to do this correctly? You'll have to drop delay buffers
and the like, and then it's not a complete solution anyway. Could
work pretty well for synths though, and that's probably the
interesting part.
//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 ---