Locked Re: WSJT-X No Decode
I do not see how this would help much. If at start timeis tells you that you are too far off you still have to fix it. I have used dimension 4 and cannot remember the last time any of 3 computers were off by more than 50 milliseconds. If you are a user of something as complex as WSJTX then it seems you are more than competent to be sure that your time is correct. I also do mot want more than one time sync app trying to fight with another which could happen.
Outlook Laptop Gil W0MN Hierro candente, batir de repente 44.08226N 92.51265W EN34rb
From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Matt Gumbley
Sent: Saturday, January 11, 2020 04:22 To: WSJTX@groups.io Subject: Re: [WSJTX] WSJT-X No Decode
This is such a common problem... I wonder whether the maintainers of https://time.is would permit WSJT-X to make use of their API, so that on startup, and periodically thereafter, WSJT-X could show you how close to ‘correct’ time you are?
“ Time.is is made for humans. Automatic refresh and any usage from within scripts and apps is forbidden. If you need time synchronization for your app, please contact us about our API.” I’m thinking of just notifying you of the time difference on startup, not automatically synchronising.. The alternative could be to embed an NTP client in WSJT-X (and configuring a set of common ‘pool’ servers). This would be much more involved; time.is is likely to have a relatively straightforward REST API, versus the complexity of the NTP protocol. 73 Matt M0CUV
Matthew J. Gumbley
-- W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop |
|