Re: [Jack-Devel] jack_last_frame_time always module buffer-size?

On Thu, Aug 22, 2013 at 2:34 PM, <[hidden]> wrote:

> >>>>> "P" == Paul Davis <[hidden]> writes:
>
>     P> there is no inherent relationship between the buffer size and the
>     P> frame time. code that tries to infer such a relationship will
>     P> break.
>
> Right, buffer size as such is irrelevant here.
>
> Just to make sure theres no confusion stemming from my original
> question: can i expect Jack to do its next call for my callback-func at
> a certain frame offset since the previous call?
>
> Aim here is to use jacks frame-accurate timing to schedule events at
> 'some_future_frame' by tagging with that frame's
> 'period_boundary_frame_no + 'frame_offset_inside_buffer - and as periods
> fly by lookup the current buffers worth of events using
> 'period_boundary_frame_no.
>
> It seems to work great in the client im building atm., perhaps im just
> being lucky.
>

there is no concept of "the future" in JACK. there is only "now".

frame-time has no reference origin, and the origin can be reset at anytime.

you need a timeline internal to your app, or you need to use jack transport.

--p

1377197355.19066_0.ltw:2, <CAFa_cKnidi0xM-bSKaYUNnLBXMRe_d_Ji8E9GiaO_TqNPa-Ysw at mail dot gmail dot com>