Apple's T2 proving troublesome for some professional audio interface users
Macs equipped with Apple's T2 coprocessor are causing serious problems for some people using Thunderbolt and USB professional audio interfaces, whether for sound or video work.

Those affected by the issue are encountering dropouts, pops, and other similar issues with gear brands like Apogee, Focusrite, Native Instruments, Yamaha, RME, and MOTU, according to complaints on Reddit, Logic Pro Help, Apple's support forums, and elsewhere. USB interfaces have been the most commonly impacted, but trouble may manifest to a lesser extent with Thunderbolt hardware.
Apple is reportedly aware of the glitch, as are manufacturers like RME, which have linked the problem to macOS. The cause could have something to do with macOS' system time daemon, "timed," as some people have reported success by unloading it. The daemon returns once a Mac is rebooted, however.
For audio professionals the issue may make a Mac difficult to use in recording, and simply unusable for live performances. It isn't clear at present how many are impacted by the issue, as it does not manifest universally.
The T2 chip controls a variety of Mac subsystems, including boot and security functions. It has already been blamed for some other troubles, including kernel panics, Mojave installation errors, and interfering with third-party repairs.
Macs with the T2 chip include the iMac Pro and 2018 models of the Mac mini, MacBook Air, and MacBook Pro. AppleInsider has reached out to hardware vendors and Apple regarding the matter, and has not as of yet received a response.

Those affected by the issue are encountering dropouts, pops, and other similar issues with gear brands like Apogee, Focusrite, Native Instruments, Yamaha, RME, and MOTU, according to complaints on Reddit, Logic Pro Help, Apple's support forums, and elsewhere. USB interfaces have been the most commonly impacted, but trouble may manifest to a lesser extent with Thunderbolt hardware.
Apple is reportedly aware of the glitch, as are manufacturers like RME, which have linked the problem to macOS. The cause could have something to do with macOS' system time daemon, "timed," as some people have reported success by unloading it. The daemon returns once a Mac is rebooted, however.
For audio professionals the issue may make a Mac difficult to use in recording, and simply unusable for live performances. It isn't clear at present how many are impacted by the issue, as it does not manifest universally.
The T2 chip controls a variety of Mac subsystems, including boot and security functions. It has already been blamed for some other troubles, including kernel panics, Mojave installation errors, and interfering with third-party repairs.
Macs with the T2 chip include the iMac Pro and 2018 models of the Mac mini, MacBook Air, and MacBook Pro. AppleInsider has reached out to hardware vendors and Apple regarding the matter, and has not as of yet received a response.
Comments
It's too early to tell specifically what's going on here, and this isn't the first time that an OS update has changed how audio gear works -- or doesn't.
Truth is, the lack of problems like this is why for decades the Mac has been the go to computer for audio production.
I can imagine many people will be staying with pre T2 Macs until this is sorted out and solved, if it is indeed solvable.
Regarding hubs, a poorly designed hub, pinched on bandwidth, like most USB 3.1 type C gen 1 hubs are, are indeed problematic, and the manufacturers don't spell this out well to the users. Thunderbolt 3 ones have sufficient lanes, and pass-through bandwidth across TB3 for everything to work.
And when it does its really unworkable (of no practical use). Just like formally verified software (its maybe correct, but of no practical value).
A normal OS should be perfectly able to support uninterrupted data streams, and have extreme low latency, even when multitasking to the max.
Remember that at 4GHz the world around us is at a complete standstill, and even sampling a sound wave of 20KHz gives us 200000 instructions to look at the matter (is it low, is it high, wait lets first calculate the first 200000 prime numbers and look after that ...).
So thats why computers are mostly idle (running, nothing of importance (NOP) instructions all the time) and why servers make (some) sense.
The problem reported has probably to do with a device causing a massive rate of interrupts (T2) and harming performance in the extreme, or causing heavy high latency interrupts (like executing ‘tmutil delete localsnapshots’) also harming the system.
In any way a big fuck up so it seems.
Then Apple finally updated the mini, making it a viable option for professional work, and released the iMac Pro, which even for those who won't actually ever buy one was a sign from above that Apple is taking the production community seriously again. Goodwill started to regenerate.
Now this.
It seems like Mojave has been a real bitch for third-party hardware and software developers. Even Pro Tools, the Photoshop of the audio production and post world, still isn't approved for Mojave. Admittedly Avid is always slow to adapt, but I've noticed 10.14 is notably absent from some other vendors' Approved OS lists too. Is there something special about Mojave that's causing trouble?