It might be useful though to test the interface with some other software - preferrably ASIO-based just to see what happens. 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. ![]() 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. If you do a search, you'll find that plenty of people have had similar problems with UA interfaces - it's not that rare. What do UA recommend as a suitable DAW?īut the other thing is that it's Thunderbolt, and that's still slightly unknown territory. 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. ![]() It got you off the phone, though.Īsk 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. I doubt whether he'll see this - the post is two and a half years old, and he shows very little forum activity.īut 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |