Could not complete your request because Assertion in...

[MetalGarret]

I'm at my wits end with this one.

I open Pro Tools 12 (up to date) and I get this error message:

Could not complete your request because Assertion in "E:\ Code\ 223110\ ProTools\ AAE\ Source\ AAX\ CFicAAXWidget.cpp", line 851.

And I've tried every option here: http://avid.force.com/pkb/articles/e...t-cpp-line-822

I had this working just fine until one day it just stopped working with my Axe-FX II USB interface. I literally changed nothing up until that point. I figured it was time to upgrade my computer anyway so I built a new machine hoping that in the process this error would cease. It didn't.

I don't know what to do here. I tried creating a Sandra report too but I'm getting error messages for that as well.

My specs are as follows:

Intel i9 9900k processor
Asus ROG Maximus XI Hero (WI-FI) Motherboard (Intel Coffee Lake chipset)
32gb DDR4 RAM
1TB solid state drive
Windows 10

If you need anymore info let me know and I'll try to get it.

[TOM@METRO]

Do you get this error without attempting to load a session?

[MetalGarret]

I get this error no matter what I do when it involves the Axe-FX II. I've tried updating the USB drivers and the firmware and still get the same error. I've done a reinstallation of PT12. Same error happens. I did a reinstallation of Windows 10 and it still happens. I did a complete CLEAN install (formatting the hard drive) of Windows 10 and it still happens. I can get now at least get my Mackie 820i to work with PT12 now. But I like to use my Axe-FX as an interface because of the reamping ability. And I've been using it as an interface for years and I was doing just fine with PT12 since I upgraded to it where out of nowhere it just crapped out on me. I didn't run any update of any kind. I was completely blindsided by this.

And I know it has something to do with the playback engine not being configured properly since that's what Avid's notes say on the 851 assertion error. But for the life of me I don't know how this could be since they've been on the same settings I've always used and there's not that many options to configure in the USB settings for the Axe-FX.

[MetalGarret]

Ok. So apparently, my sessions got corrupted and I have to make new ones with the Axe's playback engine then import the audio from the old session. Works now I guess.

[Becharax]

Originally Posted by MetalGarret

Ok. So apparently, my sessions got corrupted and I have to make new ones with the Axe's playback engine then import the audio from the old session. Works now I guess.

It's a bug in Pro Tools 2018.12 but so far no one is admitting so ...

I am a long time user since Pro Tools 6 and always installed every other update

for the .12 it's a first time I get those Assertion errors without any reason whatsoever ... Clean Install, Clean Format, Nothing to question this behavior except a bug ....

[Southsidemusic]

If it’s a ”Bug” then more than a handful people would report this issue and so far there are way too few posts about it to be labeled a Bug ..

These Assertion errors usually pops up when the computer changed the playback engine to HDMI or Aggregate etc and that is definitely bug-like behavior so reset of the playback engine seem to solve that for most people.

[Becharax]

Originally Posted by Southsidemusic

If it’s a ”Bug” then more than a handful people would report this issue and so far there are way too few posts about it to be labeled a Bug ..

These Assertion errors usually pops up when the computer changed the playback engine to HDMI or Aggregate etc and that is definitely bug-like behavior so reset of the playback engine seem to solve that for most people.

Hey Dear,

we have to check how many actually did upgrade to .12 I don't think there are many here who did take the plunge ... a lot are still happy with the .7
I am having different kind of assertion errors for no reason trust me I know my way around a mac 18 years until today

[K Roche]

My system is running without any issue or error, for 2 weeks now. I note the two guys with issue are running 3rd party interfaces. I wonder could that indicate a 3 rd party driver issue ?

[Becharax]

My Latest Assertion error was this: Pro Tools was unable to Auto Backup your session.

If your session is on a read-only drive, you must disable "AutoSave" by unchecking "Enable Session File Auto Backup" (located in the Operations tab of the Pro Tools Preferences dialog) to avoid this error.

(Error was: Permission denied (13) )

Ok I know that my Audio External Drive is Read and Write and not Read Only and I never changed anything from before so this error could happen ...

It has nothing to do with the playback engine here I guess