Re: [Jack-Devel] transport rolling + new slow-sync client

On Fri, Jun 10, 2011 at 10:55 AM, Paul Davis <[hidden]> wrote:
> On Fri, Jun 10, 2011 at 10:49 AM, Dan Muresan <[hidden]> wrote:
>> Hi,
>>
>> I was wondering what happens if the transport is already Rolling, and
>> a new slow-start client activates itself? Does Jack transition from
>> Rolling to Starting and wait for the new client to complete syncing? I
>> don't see that transition in the diagram -- and without it I don't
>> understand how a slow-start client could reliably synchronize with an
>> already-rolling transport...
>
> that's correct. it cannot. it would have to request a transport stop
> (which of course, any client may do), and then optionally restart the
> transport.

there is another implementation strategy that i've implemented in
ardour for syncing to timecode, which is to guesstimate how long it
will take to sync, aim "ahead" by roughly half that much, wait for the
master to get within a range where ardour can do "fast sync" (i.e.
change some data pointers rather than read new data), and then do that
sync and keep going. its complex and heuristic, so i can't recommend
it.

1307717834.28195_0.ltw:2,a <BANLkTin98KM2d1eYUkto+ckFRfh7=BSqpw at mail dot gmail dot com>