AAE Error PT 12.3 UR44

[hue]

It's been two weeks. Just installed a new interface. Latest firmware/drivers. PT 12.3 Vanilla. I'm getting this error.(AAE Error -6117) I've searched the site. Only found similar threads with PT first. Holding N during start does nothing. Any help here?

[hue]

For the record, I also use Sonar Platinum, Sony Acid Pro 7 and Cubase 8(paid licenses thank you very much). All of these are working Properly. Only Pro Tools 12.3 and Pro Tools 10 do not load. What a waste of money this has turned out to be. Come on Avid. Help me out here. I guess it's time to make use of my one support phone call this month. It should NOT be an issue. But, here I am.

[hue]

Also, for what it's worth, I tried trashing the preferences. NADA!

[Blackers]

Well,wellcome aboard.This is protools 12.It seems they are still developing some thngs.Maybe still in 2015.Today i just change the music drive for a brand new one faster at all and NADA.The problem is still there AAE 6 error.I use for two weeks then there it is with no further xplanation.
Lets wait.

[hue]

This problem is old. It simply should not be. I am running THREE other DAWs, none of which are having trouble connecting to my hardware. WHAT GIVES? Can they not simply make an audio engine that works? They've already adopted the ASIO standard, make it work! Could it possibly be that difficult? Sony, Steinberg, Cakewalk don't seem to think so.

[take77]

This Windows sound config helped me troubleshoot the AAE error pop-up when trying to initialize my little M-Audio JamLab interface upon startup of PT12:

Right click speaker icon and do the following for both playback & recording.

1. Make sure the UR44 interface is NOT the default Windows device (right click for options).

2. With your UR44 selected in the list of devices (now labeled "ready"), go to Properties>Advanced tab and De-select both boxes under Exclusive Mode.Do this for both playback and recording advanced settings.

3. Now, go to the WINDOWS default device and do just the opposite by
ENABLING both Exclusive Mode options for the Windows default device*.

After months of thinking the Jamlab was incompatible, changing the default settings helped with the playback engine buffer switching functionality.
But I was still getting the AAE error when trying to manually initialize using the N key.
It wasn't until the Windows device and PT interface were configured to have OPPOSITE exclusive mode settings that I was finally able to initialize upon start up without any error code.

Hope this helps.

*For good measure, I selected these options for all other non-PT devices in the Windows device list as well.

[hue]

Nope. I've messed with the Windows sound config already. I managed to get PT to open by running as admin however I cannot record. "Protools was unable to initiate Steinberg UR ASIO". I think I need to do a clean install. It be messed up. Also, I don't have any other audio I/O other than the UR 44. So I have no choice but to use it as default. As well, enabling Exclusive mode disables audio for any other program on this comp. No go. CRAP coding.

[Wizzoboy]

Pt should always be run as Administrator. Also, though it can work, Avid do not recommend the use of Win 10 at this time. This may be the cause of not being able to initiate the Steinberg ASIO driver. Have you also done all the recommended optimisations? "Crap" coding could apply to Steinberg as well as Microsoft, not just Avid. For my part I have no problems running PT 12.3 under Win7.

[hue]

Your right. Acid, a very old DAW runs just fine but it's Steinberg and Microsoft's fault. Sonar and Cubase run just fine but it's Steinberg and Microsoft's fault. This isn't something that should be an issue. I had this problem with 9 on Windows 7. I always optimize my PC for DAW use. And for what it's worth 12.3 worked just fine until I upgraded my interface. It was the change that caused PT to go epileptic. So bloody fragile. I'm fairly sure a clean install will fix it. I just haven't the time to do it as of yet.

[Wizzoboy]

As your problem started after upgrading your interface, the driver would be at the top of my suspect list. I don't think PT is as fragile as you think. The driver for my Delta 1010 dates from March 2012 and never misses a beat.