Re: [LAD] LV2 Atom Sequence timestamps

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: David Robillard <d@...>
Cc: linux-audio-dev <linux-audio-dev@...>
Date: Tuesday, June 5, 2012 - 9:55 pm

--e89a8ff248198b2e0404c1c0b317
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.

Jeremy

--e89a8ff248198b2e0404c1c0b317
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 5, 2012 at 3:44 PM, David Ro=
billard <d@drobilla.net> wrote:

On Tue, 2012-06-05 at 06:34 -0400, Jeremy Salwen wrote:

br>
br>

Context. =A0When used as event ports in the run() callback, it is alw=
ays
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

br>
p be

See above.

> 3. Are the timestamps absolute times? =A0Or relative to the previous

on

Absolute from the start of the Sequence.

> 4. Why does the documentation show |FRAMES |SUBFRMS| as the timestamp<=
br>

ld

Oops, relic. =A0I will fix this.

> 5. How are hosts/plugins supposed to deal with the multiplicity of

br>
br>
en

> unit which is tossed at it.

Indeed it would be. =A0Hence why none of this is there, so the extens=
ion
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
more clear.

In short, when used as port buffers, it's always frames, don't worr=
y
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
payloads)

Cheers,

-dr

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.

Jeremy

--e89a8ff248198b2e0404c1c0b317--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] LV2 Atom Sequence timestamps, Jeremy Salwen, (Tue Jun 5, 10:34 am)
Re: [LAD] LV2 Atom Sequence timestamps, David Robillard, (Tue Jun 5, 7:44 pm)
Re: [LAD] LV2 Atom Sequence timestamps, Jeremy Salwen, (Tue Jun 5, 9:55 pm)
Re: [LAD] LV2 Atom Sequence timestamps, David Robillard, (Wed Jun 6, 10:50 pm)
Re: [LAD] LV2 Atom Sequence timestamps, Paul Davis, (Tue Jun 5, 12:47 pm)