Adobe Audition and UA Apollo Interface

I doubt whether he'll see this - the post is two and a half years old, and he shows very little forum activity.

But that said, I think that UA have just a bit of a cheek trying to blame Audition for something that sounds suspiciously like a driver failure. It got you off the phone, though... 😉

Ask yourself this; if just about every other interface on the planet works fine with Audition, both on Macs and PCs, why is it even likely to be Audition's fault? More interesting to ask which other ones don't, and why. The prime culprit here is M-audio - their drivers are primarily intended to run with ProTools, and their ASIO driver appears not to be up to scratch at all. What do UA recommend as a suitable DAW?

But the other thing is that it's Thunderbolt, and that's still slightly unknown territory. If you do a search, you'll find that plenty of people have had similar problems with UA interfaces - it's not that rare. Audition is notoriously good at recording exactly what's sent to it, but if, for any reason that gets compromised then we're in different territory. I've heard about one instance where turning off hyper-threading appears to have improved UA performance, but that seems to be a little extreme. 

It might be useful though to test the interface with some other software - preferrably ASIO-based just to see what happens. Whilst it's clearly not impossible for this to be Audition's fault, whatever it is still needs to be isolated, and that's going to need some more checking on your part, I'm afraid...