Re: [LAD] LV2 Atom Sequence timestamps

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Jeremy Salwen <jeremysalwen@...>
Cc: linux-audio-dev <linux-audio-dev@...>
Date: Tuesday, June 5, 2012 - 12:47 pm

--00235433340edd490204c1b90b19
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 5, 2012 at 6:34 AM, Jeremy Salwen wrote:

>

video timecode.

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

On Tue, Jun 5, 2012 at 6:34 AM, Jeremy S=
alwen <jeremysalwen@gmail.com> wrote:
4. Why does the documentation show |FRAMES |SUBF=
RMS| as the timestamp field? From what I can tell, there is no unit which i=
ncludes frames and subframes subdivided that way, and the s=
ampler example
just uses the full 64 bits as a frames fiel=
d.=A0 Is this just a relic from the old event port documentation? (the diag=
ram seems familiar).
video timecode.

--00235433340edd490204c1b90b19--

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)