Need help! AAE error 6 / AAE Error 6040

[demanmetdeneus]

Hello everyone,

I am in pretty deep trouble here. I made the move from Apple this year and am now on Windows 10 with ProTools 12.8.2. Everything was working very well up until last week. Something happened, I have no idea what.

I get AAE Error 6 messages after which I have to restart my computer to get the session working again. But if this happens once, the ProTools file seems to be corrupted somehow, because afterwards it's just a question of minutes before it happens again.

I tried rebuilding sessions by exporting and then importing Midi and stems. Did this several times. This solves the problem... for a couple of hours.

Furthermore I get very strange behaviour occasionally. Sometimes all of a sudden the file or the session backup won't safe because "the file is allready in use by another program". Afterwards if I look into the sessionfolder ProTools added these weird folders with names like: 'GGujnjoXynI'. Very alarming too me, seems like something is really really wrong here.

I consider myself to be pretty smart with computers, but I cannot seem to fix this because I have no clue where to start. Here's what I tried...

- Export everything and rebuilding the session from scratch.
- Disable all plugins and activating them one by one. (Spectrasonics Trillian, Keyscape, Addictive Drums 2, Plugin Alliance stuff, Melodyne (I'm suspecting this one is causing some issues, but I am not really sure...)
- Increasing buffer size, activating 'ignore errors during playback'
- Move the session to different disks, internal and external.

Here's my system, I built it myself, and it has been working very well for a couple of months: Gigabyte Aorus GA-Z270X, i7-7700K, 16GB Corsair DDR4-2400, Samsung 960 EVO, Asus Rog Strix GTX1070.
I am using an RME Fireface 801 interface.

The problems got really big after updating to 12.8.2 but they were there before also.

I am assuming that it has something to do with disk permissions, but here my inexperience with Windows 10 is coming into play (I moved to Mac in 2004 from Win XP).

Anyone?

[mjslakeridge]

Are your sessions on a separate HDD or SSD from the operating system? You mentioned that you tried moving the session to different disks, internal and external. Generally, sessions should not be on an external disk (with the exception of old Firewire connected external disks), in an old system like mine, I have been able to use an external Firewire drive as a session drive.

Assuming you are recording to an internal HDD, is it at least 7,200 RPM? 5,400 RPM is too slow for Pro Tools.

[Wizzoboy]

Have you made sure that the Fireface is NOT selected as the default Windows audio device? Control Panel-Sound-Playback and Record tabs.

[The Weed]

Don't disable plug-ins, move them to the Unused folder. Then bring them back one or a few at a time. Just having a "rogue" plug-in in the Plug-In folder can cause issues.

Have you tried trashing Preferences and Databases, emptying the Recycle Bin and rebooting? Use guitardom's Trasher Utility for that.

Have a look at the "Help Us Help You" link at the top of the forum, try the suggestions and optimizations. Also have a look at this thread to see if there is more that may help.

Post a Sandra Report too.

HTH

[jjnssn]

Try removing all Plugin Alliance Plugs from your plugin folder. If this fixes your AAE-6 issues contact PA.


Sent from my iPhone using Tapatalk Pro

[demanmetdeneus]

Originally Posted by mjslakeridge

Are your sessions on a separate HDD or SSD from the operating system? You mentioned that you tried moving the session to different disks, internal and external. Generally, sessions should not be on an external disk (with the exception of old Firewire connected external disks), in an old system like mine, I have been able to use an external Firewire drive as a session drive.

Assuming you are recording to an internal HDD, is it at least 7,200 RPM? 5,400 RPM is too slow for Pro Tools.

I tried working from my system disk, which is a Samsung 960EVO. Very fast. I am surprised it doesn't work. On my Mac computers I never expierienced issues while running sessions from the sytem disk.

External disks are all 7200rpm on USB3

Installed a second SSD just a minute ago, NVMe, see if that helps.

Thanks for the reply!

[demanmetdeneus]

Originally Posted by Wizzoboy

Have you made sure that the Fireface is NOT selected as the default Windows audio device? Control Panel-Sound-Playback and Record tabs.

Now this I didn't try. Thanks...
However, it was always running Windows audio alongside ProTools. And it worked before...

[demanmetdeneus]

Originally Posted by The Weed

Don't disable plug-ins, move them to the Unused folder. Then bring them back one or a few at a time. Just having a "rogue" plug-in in the Plug-In folder can cause issues.

Have you tried trashing Preferences and Databases, emptying the Recycle Bin and rebooting? Use guitardom's Trasher Utility for that.

Have a look at the "Help Us Help You" link at the top of the forum, try the suggestions and optimizations. Also have a look at this thread to see if there is more that may help.

Post a Sandra Report too.

HTH

Thank you! Will try this. First I'm gonna check if the second SSD helps.
Then I will try and create a Sandra report... It's a whole new world, this Windows thing.

Thanks everyone.

[justohelp]

I found this aftear reading it had something to do with brainworx somewhere.

https://www.plugin-alliance.com/en/support.html

ProTools gives “AAE” errors when using PA’s AAX plugins on Windows
Some Windows users have reported that ProTools gives the error message “AAE error -6” in sessions containing our plugins. Please try this list of workarounds, and if they don’t help, please contact technical support.

Make sure your audio interface's drivers are fully up-to-date.
Remove any connected USB flash drives from your system.
Remove the file named WaveCache.wfm from the session folder of your current session, and also remove it from this directory: Users/public/Pro Tools.
For users of antivirus software, try disabling real-time scanning.
Contact technical support and request legacy versions of the plugins, from before the April 2015 update (if available).

Hope it works for you.