Meinberg, or others using Internet time to various servers, works well for local purposes, but not well for stations that are remotely located.

For FT8, for example, and even more important for other more fussy protocols, it is necessary to synchronize on the received signals.  The latency of a remotely operated station can be from 100 to 500 msec.  Those amounts of latency may not prevent you from decoding FT8 signals, but might be a problem if the receiving station also has clock errors.

TimeFudge allows you to manually adjust the time in selected increments to received signals and works well.  JTSync should work well if you use the feature that analyzes the received signals and automatically adjusts the clock, but not the default which is to synchronize with the NTP time.  I could not make the former part work yet.

Message: 1
Date: Sun, 14 May 2023 16:39:45 +0000
From: Howard Rensin <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [SFDXA] Computer time updates
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

I have used Meinberg NTP on all my PCs for a long time. It is written in assembler so it is very light on the OS. It runs in the background and easily installs and it's free.
Every time I check my PC against Time. Is it is always within. 06 seconds.
Strongly recommend this software for great time keeping.
Howard
KC3D