On Tue, 2012-06-05 at 06:34 -0400, Jeremy Salwen wrote:
Context. When used as event ports in the run() callback, it is always
frames, like everything else.
I deliberately avoided complicating it with a bunch of stuff to handle
beat-based time stamps in this context since this would almost certainly
be unused (learned that lesson with the event extension). It can be
added later if need be.
> 2. The specification says "The unit field is either a URID that
> 3. Are the timestamps absolute times? Or relative to the previous
Absolute from the start of the Sequence.
> 4. Why does the documentation show |FRAMES |SUBFRMS| as the timestamp
Oops, relic. I will fix this.
> 5. How are hosts/plugins supposed to deal with the multiplicity of
Indeed it would be. Hence why none of this is there, so the extension
does not imply you are expected to have to deal with any of that. I
suppose the fact that it is audio frames in this context needs to be
In short, when used as port buffers, it's always frames, don't worry
about it. The potential for other time stamp types is there for other
cases, since it's possible to use Sequences in other non-port-buffer
ways (e.g. you could send around events with entire sequences as their
P.S. lv2-dev is a better place for this sort of thing
Linux-audio-dev mailing list