rec.arts.movies.production.sound

On Thu, 29 Nov 2007 12:28:36 -0600, Matt Mayer
schreef:

>You are correct. Other than the inital jam of clock time, there is no
>way in the 7 Series to use the TOD clock as the master reference. Drop
>Frame would correct for the difference between TOD and timecode.
>
>Sound Devices has posted a Sound Note about the differences between the
>Timecode and TOD clocks here:
>
> /notes/recorders/time-code/tc-clock-accuracy/
>
>---Matt (from the lazy second portion of the planet..)

Maybe i can explain it better in a more simple way for those who think
Wtf is he talking about..

This whole thing is if you are talking about a recorder with basically
2 clocks on board..The RTC clock (1) is generated by a onboard chip/IC
, and the TC part (2) has another chip that generates it. ( yes, the 2
might have a hardware based relation, for those who what to argue ,
but that's not relevant, imo. )
So, the RTC clock (1) has the stability like let's say the average
cheapo watch one can buy, but the TC clock (2) is something rather
different...it has some more hardware ( some with a crystal ) to stay
stable in the 8 hours, compared to some ext running TC unit as in
slates, or camera's.

For example, the Cantar has an Int. Clock (1) that runs time of day,
always. I can Jam my Cantars int. TC gen (2 ) to that int clock(1)
by pushing jam. Meaning the TC clock (2) jams to the int clock (1) (
or RTC clock as i call it ) but after that jamming the TC clock (2) is
on it's own, and is stable for 8 hours, with % up or down
difference or drift, and according to the specs.

To be short, the int. RTC clock ( 1 ) can drift whatever it likes, it
would never influence the stability of the TC part (2) of the
recording, or Recorder.

R ( prefers the NDF part of the planet, and they still shoot hang the
guy who invented the lazy second, even post mortem )





--
E&OE Http:// /