Content-Type: text/plain; charset=ISO-8859-1
On Tue, Jun 5, 2012 at 3:44 PM, David Robillard wrote:
> On Tue, 2012-06-05 at 06:34 -0400, Jeremy Salwen wrote:
If the timestamps are absolute, are they reset on every call to activate()?
I thought lv2-dev was for developing the lv2 spec and extensions, but my
questions were more about implementation of plugins/hosts.
Content-Type: text/html; charset=ISO-8859-1
On Tue, Jun 5, 2012 at 3:44 PM, David Ro=
billard <email@example.com> wrote:
On Tue, 2012-06-05 at 06:34 -0400, Jeremy Salwen wrote:
Context. =A0When used as event ports in the run() callback, it is alw=
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). =A0It 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? =A0Or relative to the previous
Absolute from the start of the Sequence.
> 4. Why does the documentation show |FRAMES |SUBFRMS| as the timestamp<=
Oops, relic. =A0I will fix this.
> 5. How are hosts/plugins supposed to deal with the multiplicity of
> unit which is tossed at it.
Indeed it would be. =A0Hence why none of this is there, so the extens=
does not imply you are expected to have to deal with any of that. =A0I
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 worr=
about it. =A0The 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
Thanks David,If the timestamps are absolute, are=
they reset on every call to activate()?I thought lv2-dev was for d=
eveloping the lv2 spec and extensions, but my questions were more about imp=
lementation of plugins/hosts.