I have it working but it is really touchy. I had to open it from the macOS file. I must have a problem with other software loaded it does not like.Chronycontrol works correctly on my Apple Silicon macs with Sonoma.
I have it working but it is really touchy. I had to open it from the macOS file. I must have a problem with other software loaded it does not like.Chronycontrol works correctly on my Apple Silicon macs with Sonoma.
Trust me, there's nothing wrong with ChronyControl on macOS Sonoma on Apple Silicon.I have it working but it is really touchy. I had to open it from the macOS file. I must have a problem with other software loaded it does not like.
Yes I have it running. However it does not load as I expect it too. There is an issue with My machine and CC's Config file. I had to load the software from the macOS, ChronyCrone File. If I try to load the utility from its icon it doesn't exactly lock up my computer but it continually cycles in and out. I am unable to restart normally and I physically have to reboot my machine. I have expectations on how software should run and at least on my machine ChronyCrone does not meet those standards. But it is running,Trust me, there's nothing wrong with ChronyControl on macOS Sonoma on Apple Silicon.
![]()
![]()
Good luck with that. I’ll be interested to see how it goes after a few days.I am not going to have an issue with my time base because I never shut down my computers they run 24/7 and they go on standby after a couple of hours.
Over the many years on macOS I learned, that more people know and work to "fix" macOS, bigger problem they cause. MacOS should simply work and if we have to do what you seem to be doing (I assume you are starting app from inside bundle), more troubles we get into.Yes I have it running. However it does not load as I expect it too. There is an issue with My machine and CC's Config file. I had to load the software from the macOS, ChronyCrone File. If I try to load the utility from its icon it doesn't exactly lock up my computer but it continually cycles in and out. I am unable to restart normally and I physically have to reboot my machine. I have expectations on how software should run and at least on my machine ChronyCrone does not meet those standards. But it is running,
I found out that my favorite Zip opening software has a Mac version. "UnZip One". I used it to open ChronyContro's zip file and this is what it reported.
View attachment 2299585
And I'll say again, good luck with that.I finally deleted Chrony Control I have no idea why it is not opening correctly. It turns out resetting everything in the Date and Time section did the trick I don't need any external time management software. In my self education I did learn about the troubles people have with earlier macOS on time keeping. It would seen that Sonoma is doing a good job of managing the clock on My Mac Studio.
I have no idea what you're doing and how you're trying to run ChronyControl but it really should be as simple as downloading it, unzipping it and chucking the .app file into your applications folder. You shouldn't have to be faffing about to make it run.Trying to open this application normally invokes the configuration file and that causes the weirdness I looked at this webpage it isted what CC was loading on the Mac. I realized these were the files contained in the macOS folder. I installed each one separately a terminal window opened on each one indicating a successful installation.
Other that being somewhat new to macOS I have been using computer since about 1970. I have been through years of machine language when the dreaded "syntax" error would pop on in your coding. These days with all of the years of writing GUI's it is not up to me to scope out why something does not load properly. So what is happening it is not my fault. It isn't anything I am doing. If this was My Windows machine I have a sub-routine that reports what the problem is but I don't think Apple has anything like that.And I'll say again, good luck with that.
From Big Sur onwards, the way macOS synchronises the time has changed. If you leave your Mac asleep, occasionally, when it wakes up, the time will be far enough off that FT4/FT8 will not work properly. The native OS will bring the clock back in but it will take a while, it's not instant.
ChronyControl DOES work on Apple Silicon. I have no idea what you're doing to stop it working but comments like this make no sense to me.
I have no idea what you're doing and how you're trying to run ChronyControl but it really should be as simple as downloading it, unzipping it and chucking the .app file into your applications folder. You shouldn't have to be faffing about to make it run.
What @Honza1 says above is absolutely spot on.
Oh, the rabbit hole you can dive into on macOS is deep and full of useful tools. It is, in the end, UNIX system with most bells and whistles you may be used to from Linux. You can start app in terminal session (I mean both GUI app as well as executable from the bundle) and watch the messages to terminal, if they exist. You can always watch messages in Console and try to decipher those. Good luck, documentation for app messages is generally non existent...Other that being somewhat new to macOS I have been using computer since about 1970. I have been through years of machine language when the dreaded "syntax" error would pop on in your coding. These days with all of the years of writing GUI's it is not up to me to scope out why something does not load properly. So what is happening it is not my fault. It isn't anything I am doing. If this was My Windows machine I have a sub-routine that reports what the problem is but I don't think Apple has anything like that.
NTP is the "standard" protocol for time sync. You can get to at least 100 milliseconds of accuracy over WiFi. With much effort, you can get to better than 1 millisecond.I am setting up my MacStudio to operate on the amatuer radio digital mode, FT-4, and FT-8. One of the requirements is precise time syncing. My Windows machines are awful in maintaining the precise time needed. There was a earlier thread about this subject on this issue and I seems the Mac has a similar issue. We are talking about fractions of a second needed for smooth packet exchanges. Chrony Control was suggested. I tried to load in on my Mac Studio and it locked up the Mac in a continual loop thing I had to physically turn the computer off, and restart to stop. Is there anything else. So Far I have not found a solution. The applications I have on My Windows machines are set to resync every couple of minutes, no doubt overkill but it does this in the background so why not.
Yes I know all of this. Until I discovered Official US Time and its "Device Check" I did not have a handle on how accurate the clock is sync is maintained on at least with Sonoma, apparently this was not the case with macOS's that preceded this one, High Sierra being singled out. I come from the decades of living in the MicroSoft OS world. It's time keeping seemed to get worse as each successive OS waddled onto the stage.NTP is the "standard" protocol for time sync. You can get to at least 100 milliseconds of accuracy over WiFi. With much effort, you can get to better than 1 millisecond.
NTP is already part of MacOS, Windows and Linux and every OS I've used in the last 20+ years. It is universal. Usually, on a desktop system, it runs once at boot up. What you want is to run it continuously in the background. You need to install the full-up NTP system from either MacPorts of "home-brew". Then let it run for an hour or so and you will see that you system close is within some tens of milliseconds of the actual time.
NTPd runs continuously. It never "jumps" the time. What it does it slowly adjust the RATE of the system clock, slwing it a very tiny amount if the clock is fast. It can use a large number of Internet time servers and will select the "best" servers. How to choose the "best"? The ones that give the same time are assume "good" and outliers "not good". Which is uses depends on where in the world you are and the connection quality to each server.
NTP ha been the standard way this is done for at least 40 years.
Do you know how the web page calculates the offset? For me (in Australia) it is showing my clock in error by around 140mS.Until I discovered Official US Time and its "Device Check" I did not have a handle on how accurate the clock is sync is maintained on at least with Sonoma, apparently this was not the case with macOS's that preceded this one, High Sierra being singled out.
sntp time.apple.com
+0.002171 +/- 0.072773 time.apple.com 17.253.66.125