Cellular forums Home > Archive > GPS > April 2006 > Re: Clock accuracy & auto setting : digital television does a crap job of providing time servic









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Re: Clock accuracy & auto setting : digital television does a crap job of providing time servic
G-squared

2006-04-29, 2:48 am


Max Power wrote:[color=darkred
]
>
> No I am not suggesting this.
> 64 extra bits can help futureproof a signal however...
> ================
>
> Turing NTP into a very high precision signal is possible -- but I advocate
> split versions of the signal.
> Otherwise, for consumers the extra 64 bits could be used for other time
> related services and futureproofing.
> ================
>
> NTP does have its origins with Unix Time, and Unix / Linix / Minix ... need
> to be upgraded to account for 64 bit time [to help avert the 2038 crisis] --
> but not NTP time. However, Unix Time and NTP have always had near perfect
> interoperability for at least 2 decades...
> ================
>
> This 'time ignorance' socally acceptable now, but bad public policy.
> Lack of use of UTC is a bad policy, but this is an ATSC problem -- not a
> DVB-T problem.
> HDTV is very late Beta -- but when HDTV is omnipresent the lack of accurate
> time avalability should not be the case.
> Your HDTV set should be able to sync its own clock after being turned on for
> 5 minutes.
> HDTV sets shoul be able to set the clocks of other devices [VCR's, DVD's,
> set top boxes] using whatever [TV] connection technology that will exist in
> future.
> Commerical stations not providing an accurate time signal [to within 1.0s]
> should be punished (based on transmitter power) -- the ethics of this being
> that that keeping broacast clock accuracy requires virturally no cost
> overehead and provides a public service function. A lot of ATSC transmission
> energy goes into sending 'empty packets' or 'nulls' -- replacing 1% {per
> hour} of nulls with time signal packets would yield instant time sync.
> I am considering the UK, Erie, Australia, NZ and Canada in my point -- not
> just the US.
> ================

You actually think broadcasters DON'T know what time it is? They know
better than nearly anyone else precisely what time it is. The fact that
they don't make an effort for the 25 of us actually watching the
digital feeds means what? You don't remember last months thread about
DTV being a sideline?

http://groups.google.com/group/alt....> 5cf5b6d6f8c77

Be patient. They'll get to it as it gets closer to analog cutoff. I'm
sure you can sort out what time it is on your own. Maybe this will help
in the meantime.

http://www.time.gov/timezone.cgi?Pacific/d/-8/java

Perhaps the fines should be on the people out here who can't figure out
what time it is. Just what broadcasters need. More regulations.

GG

LinkBot





Other Archives: Real Estate forum archive | Web Design archive | Software support archive | PC Hardware reviews archive | Medical topics archive

Copyright 2004 - 2008 cellphonetopics.com