Walking around the TV section of a large department store recently, SWMBO noticed that the TVs all seemed to be showing the same channel at slightly different times - some were a good second out.
That is due to the TV's internal delays in decoding the digital signal plus maybe differences in the time the TV's were powered up (not sure on that last).
No surprise there. given it's all done in software now.
It isn't hard to make one and they are standard in the small weather LCD display monitor devices sold in the likes of Aldi, Lidl and Maplin.
The hard part is buying the bits in one off quantities for a sensible price. The fully built products are from about £10 on Amazon. You are probably better off buying one and taking it apart for the modules.
Regards, Martin Brown
Or gain it. The only thing guaranteed is that there is a small dependence on temperature and a smaller one on battery voltage. Most are not properly trimmed and so drift +/- 15s/day worst case.
Some time sync software will show you the log of adjustments.
Who knows. It is more common for old games that disable PC interrupts for long periods of time to make the main system clock run slow.
The typical daily drift on an untrimmed RTC chip from a 32kHz xtal is about 15s or worse if the designers fail to put the right loading capacitors round it. Depends a bit on ambient temperature.
I do find it annoying that some very expensive computer based kit does not have correctly trimmed xtal RTC built in. The manufacturers fix for this was to add GPS so that the unit can get a correct time as it boots!
Regards, Martin Brown
Not reaction time. People are much better at hitting things to time when they know the beat in advance than they are at reacting. An undergraduate teaching (ie not serious) experiment tried to measure reaction times using a regular flashing light. I could hit the button within a few milliseconds of the light coming on once I got the rhythm.
In article , Mark writes
To be more accurate, it's a SNTP (simple NTP) client which not all NTP servers support.
Which sounds like its dumb and may not attempt to apply linear corrections to the system clock, rather just relying on resetting the clock periodically.
It's an MS program, what do you think?
In article , Tim Watts writes
Pretty sure it is, so anyone wanting greater accuracy could use one of the NTP clients mentioned in this thread. Being able to specify more than one server is also an advantage.
Only if you use analogue reception. On DAB or FreeView they are well out. 'Internet' reception too, I'd guess.
Big Ben is broadcast several time a day on R4. But it is not accurate most of the time.
Could tweet for it. ;-)
AFAIK it's based on SNTP on Windows 2000 but NTP on later OSs.
The default settings are not great (check once per day and always use time.windows.com). By configuring to check more frequently and by using a better server, the accuracy can be pretty good.
nope. Its purely how much buffering they do on the signal. Decoding a compressed video always takes some time, and to an extent,the more time it takes the better a job you can do.
Our Sonyt STBS are about a second and a half out of synch with 'real time' and the DTB adapter on this computer is more like 15 seconds.
The wifes DTB on her Mac is about 5 seconds delayed
On Tuesday, August 21, 2012 10:32:07 PM UTC+1, The Natural Philosopher wrot= e:
[ntpd]You say designed in but ntpd is not a built-in part of any 'operating syste= m' but rather a 3rd party tool that is optionally installed. Few, if any, d= istributions install ntpd as part of their base install, not least because = the benefits of its use are severely limited on machines that don't stay co= ntinuously on.
If anything it is more common to find ntpdate installed and is usually invo= ked once at startup. Now that ntpd can perform these 'one-shot' time sets n= tpdate will eventually be retired however so we may start to see ntpd insta= lled by default but perhaps not automatically run as a daemon.
Mathew
I heard, during the Olmypic refering to Usain Bolt that it takes a human 0.=
1 second to respond to a sound, so that makes all clocks with sound as indi= cation out by 100ms according to the true time, unless you use software to = 'pip' 100ms beforehand the true time is reached. =20
The Windows Time Service is not guaranteed to be more accurate than the nearest second, even if it is a full NTP implementation in Vista and later.
well in that case you could argue that nothing except the linux kernel is part of linux.
Not even X-windows or a window manager. Nothing. Not even bash or sh.
In fact ALL of linux is '3rd party' because there is no 'Linux company' that 'supplies one monolithic product'
hardly.
whatever..
Anything digital is always behind real time. Due to the way it is sampled. Even digital microphones, compared to analogue ones. Which makes it impossible to use a mix of the two. Hence there are very few around - the exception being some radio mics.
And any processing after that initial sampling may slow things down further.
HomeOwnersHub website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.