Locked Re: Missing decodes #AudioIssues

Tim Dawson

That has been the "normal" ntpd behaviour on advanced platforms for decades! The issue has been that Windows has been such a blunt instrument, that it did not support drift adjustments for those same decades, and *I think* just started supporting it recently.

This has not been by adding *any* "corrections" when running in a stable state (boot may jump correct), but by either speeding up or slowing down the clock accordingly to bring it into sync, and then applying a correction factor to keep it there and prevent future drift, since clock errors are pretty consistent ("tickadj").

On October 8, 2022 5:22:36 AM CDT, Chuck Gelm <nc8q-aredn@...> wrote:
On 10/7/22 22:40, Robert Rose via groups.io wrote:
Just for completeness, I note that I was using using Meinberg on my Mac, and the time differential was 2.1 to 2.3 seconds. I switched to an Apple server in Cupertino (I am in San Diego) and the difference dropped to 0.1 seconds.

I believe the WSJT-X User Guide recommends that you use the closest time server. It takes 0.13 seconds for light to circumnavigate the earth. Add in time for hops and switches, and this sounds like good advice.

IIRC, my NTP client monitors RTT latency with multiple time servers and adjusts the time accordingly.
Time adjustments are done  s l o w l y  in adjustments of thousandths of seconds,
not as an 'at once' synced jump.

It seems to me that MS-Windows users should either:

* use a NTP client that maintains their computer clock or
* use a time sync client immediately before starting WSJT-X.

73, Chuck

Sent from my Android device with K-9 Mail. Please excuse my brevity.

Join {main@WSJTX.groups.io to automatically receive all group messages.