On Nov 29, 10:30 am, Matt Mayer
> Sergio Sanmiguel wrote:
>
>
>
>
>
> >>> Hey Guys,
> >>> Thanks for all the input.
> >>> I was looking in the 702T Users Manual and & found this:
> >>> "24 Hour Run (mode):
> >>> ...the generator will also re-jam if the time-of-day clock is reset.
> >>> Once jammed, the generator will run continuously from the timecode
> >>> clock, not the time-of-day-clock."
> >>> The funny thing here is that when I enter the menu to reset the TOD
> >>> clock it actually reads the current time. I mean, the TOD clock
> >>> actually keeps better track of time better than the TC generator (as
> >>> expected)
> >>> Wouldn't it be useful if the TC generator could grab TOD clock & re-
> >>> jam (actual time) after a couple of hours in order to display accurate
> >>> TOD? Isn't this the way Boomrecorder generates TOD timecode?
> >>> Thanks,
> >>> Sergio
> >> Sergio,
>
> >> I am curious, what frame rate is you TC generator set to?
>
> >> ---Matt
>
> > Matt:
> > At this time is set to since the last project require that.
> > Do you think setting it at 30fps would drift the less?
>
> > Ben:
> > Wouldn't it drift anyways since the crystal would cause a 0,1 % drift
> > by 8 hours?
>
> > ~
> > S
>
> Sergio,
>
> That is exactly why the timecode is drifting from time of day. At
> , you are loosing 108 frames or approximately seconds an hour.
>
> This was the whole reason behind the development of Drop Frame code. It
> drops 108 frame numbers per hour to keep the timecode more or less in
> sync with time of day.
>
> Set your TC clock to any even frame rate (24,25,30) and it will stay in
> perfect sync with time of day.
>
> Oh, also that accuracy spec is .1 parts per million ( ) not .1%
> (.001)
>
> ---Matt
Right! I'll do that...
Thanks,
Sergio