10 Dec
2002
10 Dec
'02
7:14 p.m.
David Olofson wrote:
like tempo changes without recalculating all later event
times -- this also allows prequeuing without emptying and
reloading the queues on tempo change. in general, it makes
all timing calculations (quantization, arpeggiators etc)
one level easier, and they do tend to get hairy quickly
enough.
thats a
mistake, i think. there are some definite benefits to being
able to define events' time in musical time as well.
Like what? Since we're talking about sample accurate timing, isn't
asking the host about the musical time for an event timestamp
sufficient for when you want that information? Note that I'm talking about a low level
communication protocol for
use in situations where you would otherwise use LADSPA style control
ports, or audio rate control streams. These are *not* events as
stored inside a sequencer.
but you'll probably end up wanting to use a sequencer to
store and/or (re)generate them, based on musical time.
tim