Why not run ntpd and keep your clock in sync all the time instead of once an hour :) Jim, K6JWN On Thu, Feb 17, 2011 at 01:09:17AM -0600, Chuck Henderson <rpt2@chuck.midlandsnetworking.com> said:
When I started using this software I noticed the audio issues in my test environment. I tried a dozen different mothertboard/CPU combinations and 3 different USB fobs. I found that the faster the system the less noticeable the issues but even a 3.4 GHZ quad core still had the issues. I experimented with a lot of variables and several things made some difference but the single most significant thing that reduced the issue was stopping ntpd. I now run ntpdate 40 seconds after the hour, every hour. This keeps the date and time close enough and greatly reduces the audio glitch like sounds that I was noticing. Also I found that when the system is not under test and is using real hand held and mobile stations working through the repeater that the remaining audio glitch like sounds are indistinguishable from typical normal radio noise hits. By the way, my final choice for a system board is the D510MO. While I do not know for sure, I suspect that when ntpd makes tiny adjustments to the system time, this results in tiny glitches in the processing in the USB sound system. I am clueless how to track it down any further, and do not see any need. Chuck