Either way I can not find a fix to save my life.
Nothing changed except for now I may have changed things with the research I did on the Internet. I re set it so it wasn’t the default and now I can’t get playback in my Pro-tools. The only thing I did was set the Scarlett as my default audio out so I could hear the Key Lab in my monitors. Today I was trying to set up a new Arturia Keylab 49 and had the program “Analog Lab” open. I don’t understand why because yesterday I was using my Scarlett 2i2 and all was well with no issues. I hate to post in such an old thread but I’m having this issue myself now. I've googled them, but couldn't find much.Īny help would be greatly appreciated because I don't know what's causing the problem or how to fix it and it's been going on for two days now.Īlso, if I use ASIO4ALL instead of the Focusrite USB 2.0 Audio Driver then Pro Tools works fine, but I still need to be able to use the 2i2.
I've also gotten AAE error -6001 and AAE error -6009. Please make sure that the device has been configured correctly." I've gotten various messages, one saying Pro Tools is unable to reacquire hardware." and another saying "Pro Tools could not initialize the Focusrite USB 2.0 Audio Driver. When I launch Pro Tools everything seems ok, but when I try and start a session Pro Tools crashes or my whole PC auto restarts. I thought it was that it wasn't drawing enough power from the PC after some googling, but updating the driver ended up fixing it. I then noticed that my Scarlett 2i2 preamp was having problems. I just upgraded to 12.7.0 after I got the hard drive on my PC replaced (the old one was failing) and reinstalled everything. Just pointing out that there's an easy fix if something bad were to happen).Hello everyone, I just made this account because I've been having some problems and I can't seem to find a solution. (In 20+ years of cleaning the registry I've never had to restore one because of a botched cleanup job. The only thing I suggest users learn to do is backup the registry beforehand. You don't have to know a thing about how it works - only how to run it. I get that some folks are leery of anything to do with the registry, but a registry cleaner is just another tool. Also, by leaving the old drivers in there, you never know if they'll cause a problem again down the road. After a reboot, all the old driver bits are gone! This ensures a thorough fix as opposed to installing on top of the corrupted code and hoping it all works out. You don't even have to go into the registry editor if you have a utility like JVPowertools or CCleaner, which searches for and cleans up all unused registry entries. It's not hackery, but rather cleaning up bits of leftover code. Petemus That's what I did, and it went well, without registry hackery or such.
0 kommentar(er)
