23 Dec
2002
23 Dec
'02
2:03 p.m.
If you're sync'ing with beats or measures,
you're fine. But if you're
doing it the traditional way - sync'ing with a note value - you'll
need to know what one beat actually is. Then you'll need the beat
value as well.
hrrm, this is purely theoretical. We can either add it because we MIGHT
want it, or wait. I'll put it in my notes to implement and we can think
more about it.
What if,
rather than have these as controls, they were explicit
event_ports. The host has to call
"plug->get_event_port(some_indexing_scheme);" anyway, right? What
if it had a list of 'special' queues.
plug->get_event_port(plug, EVPORT_TEMPO);
Then we get all the goodness of events, without the overloading of
the notion of controls. Just another idea.
It doesn't really change anything - and the selection of a suitable
queue is still something that belongs in the plugin implementation.
(Most simple plugins will want a single queue, since otherwise,
they'll just have to merge the incoming queues anyway.)