13 Dec
2002
13 Dec
'02
5:20 p.m.
Plugins can
look at
host->ticks_per_beat.
No, that can change at any time (or many times) in the block. Yes, although sending one event for every tick,
assuming that a tick
is the smallest time unit that the sequencer knows about, means that
you get lots of tick events, or that you need to do some extra work
in plugins, to calculate the ticks that don't come in as events.
Do we really need to send tick events EVER? Assuming we like the idea of a
tick:
plugin: host->tick_me(100, cookie); /* alert me in 100 ticks */
host delivers a tick event at the right time.
I guess I don't really like that. I'd rather see:
plugin recognizes the need for some action in 1/4 beat.
plugin knows there are 18,900 samples per beat (140bpm @ 44.1k)
plugin delivers a long-term event to itself for now+4725 samples
This should solve the issue of needing to know the passing of linear musical
time. It doesn't solve the need for a plugin to know about looping or
transports in musical time. Does a plugin need to know this? Maybe useful
for it to go to the middle of a sample or something...