SET(..., value)
RAMP(..., target, duration)
SPLINE(..., target, target_slope, duration);
do we really need spline? How many plugins are going to implement that? If
the host wants to approximate a spline, send multiple short linear ramp
events. Then you only need timestamp (start), duration, and value. The
plugin just has to arrive at that value by the end of the duration. Slope
is implied.
beat
number
tick number
I would think you only really need one of these, since you can
calculate the other if you really need it. (Ask for time info, or
track meter changes, or whatever there is.)
Anyway, these would both have to be doubles (64 bit), since integers
would introduce large rounding errors (can't have *both* timestamps
and positional data as integers), and float (32 bit) have
insufficient resolution.
beat events could be integral - the host sends the beat # timestamped to the
very first sample at or beyond the beat edge.
Tim