Quote:
Originally Posted by Darryl Ramm
ASIO4ALL is not a real solution, you have interfaces with good ASIO drivers, you should not need ASIO4ALL, and it certainly will perform worse than the proper driver.
Have you contacted UAD support? Or tried a clean Windows install? There is not much rocket science here, so I would quickly expect your machine is just messed up and a clean install of everything is the way to go.
Sent from my iPad using Tapatalk
|
Yeah, I know ASIO4ALL is not a "real solution", I know it will perform worse. However, I need a solution in order to work with PT, and right now, this is what I have. Unfortunately, PT was so far unable to provide any other "real" solution.
I didn't contact UAD tech support, but you just throw so many assumptions in the air. Here are the facts: My machine is brand new. The Windows 10 installation on it is as old as the system (so new as well). It only has audio related software and drivers installed on it (it's my studio computer). And most importantly - Windows AND Cubase recognize and work flawlessly with my Apollo. Only PT doesn't. So what do you think UAD support will tell me? "Obviously, there is no problem with your Apollo device, it's a PT issue, contact PT support" - and they will be right. The issue is ONLY WITH PRO TOOLS. So it's not my system that's messed up, it's PT.
I contacted Avid support already, and they're not much help by email. They told me to uninstall and re-install my drivers and PT. I did, didn't help. I told them that, and until now they failed to answer. I will have no choice but to contact them over the phone now. I do hope they can offer better solutions than that. I see absolutely no reason why I need to re-install Windows just to see IF PT will work then - and according to what I said above, this probably won't work as well. Someone in the know from Avid will have to tell me exactly what this "line 1693" means. Also, please note that I'm not the only one having this issue, not at all, even people who used to have it working cannot make it work after the 12.8.3 update. This is DEFINITELY a PT issue.