It happens on the internal sound too.mgw38 wrote: ↑Tue Apr 30, 2019 8:05 pm The reports I‘ve read seem to indicate that the T2 chip bug is only relevant for setups with a USB 2.0 audio interface. The system is supposed to accidentally overload the USB with more information than the 2.0 connection can handle. But a USB3.0 or Thunderbolt audio interface should be fine.
From what I have seen so far there is more than one bug here. Many reports talk about Time and Location daemons but I had glitches caused by the SmartBatteryManager daemon spiking the first core every minute.