if the event(s) happen to late i.e after a dropout i wouldn't want it to trigger anything.
but on the other hand: i would anyway use it for a counter... then i wanted it to count further. if it counts from 1 to 4 and misses the 2th event it should go to 3 on the next supposed event to be in sync with outside. the realmetro could have 2 outlets one for events in time the other for the ones who are too late. if i had a realmetro i'd built a realcounter that'd output 1 _ 3 4 5 6 but still no idea how it can get achieved :( On Jun 22, 2007, at 6:11 PM, chris clepper wrote: > I have thought about making a 'real time' metro. One of the features > I was considering was what to do if the event happens too late, would > the output fire or drop the event? > > On 6/22/07, Enrique Erne <[EMAIL PROTECTED]> wrote: >> hi >> >> has anybody built a dropout save metro ... say if pd freezes for a >> while and comes back that the metro would still be in sync with the >> 'outside' world. that would be very nice in a life situation. >> >> some ideas ? do you think it can be done in plain pd? >> >> i failed when i tried to measure the periods between the 'ticks' and >> calculated the new delay time. >> >> i just discovered [time] from zexy which is the system time.... >> ... has anyone yet built a metro with [time] ? :) >> >> eni >> >> >> _______________________________________________ >> [email protected] mailing list >> UNSUBSCRIBE and account-management -> >> http://lists.puredata.info/listinfo/pd-list >> > _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
