[PD] dropout save metro

[Mathieu Bouchard]

On Fri, 22 Jun 2007, Enrique Erne wrote:
> On Jun 22, 2007, at 6:54 PM, Roman Haefeli wrote:
>> lets assume you want to schedule the next 'bang' to 43s297ms, but
>> the output of [timer] maybe is '43 296', '43 296', '43 298'.
>> won't be hit at all. then i think, that this approach wouldn't be 
>> accurate at all, since there is no logical time involved. the advantage 
>> of logical time is,
> i think your totally right... too bad.

Then both of you need to read the helpfile of [timer] and compare it with 
the one of [realtime]: [timer] works in logical time only.

If you want to make a [realmetro] abstraction, you use [realtime] to 
figure out whether you are late, and in the case you figure out that you 
are too late, you bang to the right outlet of your [realmetro], so that 
the user can bang some kind of catch-up routine in order to skip a frame 
while keeping everything else in sync with the logical time.

In no case, [realmetro] will ever be in advance, except to the extent that 
buffering happens in order to smooth out the irregularities in the 
schedule (afaik this only happens for audio). It may look in advance if 
even the first bang of a given [metro] was late and you assumed that it 
wasn't.

  _ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada