- PRO TOOLS 12.8.3 UA APOLLO INSTALL
- PRO TOOLS 12.8.3 UA APOLLO DRIVERS
- PRO TOOLS 12.8.3 UA APOLLO WINDOWS 10
Someone in the know from Avid will have to tell me exactly what this "line 1693" means. 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. I do hope they can offer better solutions than that. I will have no choice but to contact them over the phone now. I told them that, and until now they failed to answer.
PRO TOOLS 12.8.3 UA APOLLO DRIVERS
They told me to uninstall and re-install my drivers and PT. I contacted Avid support already, and they're not much help by email. So it's not my system that's messed up, it's PT. 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. And most importantly - Windows AND Cubase recognize and work flawlessly with my Apollo. It only has audio related software and drivers installed on it (it's my studio computer).
PRO TOOLS 12.8.3 UA APOLLO WINDOWS 10
The Windows 10 installation on it is as old as the system (so new as well). Here are the facts: My machine is brand new. I didn't contact UAD tech support, but you just throw so many assumptions in the air.
Unfortunately, PT was so far unable to provide any other "real" solution. However, I need a solution in order to work with PT, and right now, this is what I have.
Yeah, I know ASIO4ALL is not a "real solution", I know it will perform worse.
PRO TOOLS 12.8.3 UA APOLLO INSTALL
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. I really do hope to find a solution, and obviously I can't buy the software before I know it can work on my hardware at all).ĪSIO4ALL 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. (I gotta admit it's kind of disheartening to see many such posts opening here recently, specifically regarding Pro Tools First and the audio engine issues. I tried it with Asio4All (though I shouldn't have to, I do have a dedicated interface), and when it comes to initialize audio PT just crashes for me with this driver.Īlso, when trying to open a new project, it first tells me my audio properties changed, then tells me the Xpand!2 plugin doesn't exist in my plugins folder (it should be there actually, as it was installed), and finally, after it seems the project is about to open, I get this error message:Ĭould not save as "0000" because Assertion in ".\ Document\ UProjectBundleMgr.cpp", line 1693. Perhaps needless to say, there is no problem with Cubase, and also everything is fine with playing audio in Windows in general. I just updated to the latest UAD drivers (9.4) - no dice. I installed Pro Tools First, and the Playback Engine menu simply does not show my Apollo Twin USB as an option. I'm on Windows 10 with the latest Fall Creator's Update.
0 kommentar(er)
