Mike, It doesn't do much good to be "in-your-face" about clock synchronization issues to the receivers of signals which are off by too high a delta, because it's the sender that needs their clock adjusted, not the receiver.
However, your attention to the issue gives me an idea... If an instance of WSJT-X sees that most (90%) of remote signals it sees are too far off from its own, the chances are is that it's *the local user's* clock that needs adjusting, and that user could be alerted to sync their clock in that case. What do you think? -Dave W3DJS <https://www.qrz.com/db/W3DJS> On Mon, Jun 3, 2019 at 7:48 AM Black Michael via wsjt-devel < [email protected]> wrote: > Would probably be good if WSJT-X did what JTAlert has started > doing...highlighting DT values > 1.5 sec. > > For FT4 perhaps highlight > 0.5 seconds since if both sides are off -.5 > and 0.5 I assume that would be an unlikely decode. > This is what JTAlert does now. > Then, also put some help in the manual about time setting on common > platforms when people what to know why all of the DT values are being > colored. I've been notifying quite a few people about their clocks but a > lot of them don't even have email addresses on QRZ so can't be notified > easily. There needs to be something a bit more in-your-face about time > problems. > > [image: Inline image] > > > de Mike W9MDB > > > > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
