Error Message

[psft001]

Tried to use a Behringer UCA222 to input bass & guitar via my PC into Pro Tool (ver 2018.1) couldn't get it to recognise so looking on here saw post re' ASIO driver download - tried this still nothing - now I'm getting the following error message whenever I try to run Pro Tools . . .

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

uninstalled the ASIO driver, rebooted - nothing, same error. Uninstalled Pro Tools then reinstalled - still getting error message!

Possibilty that the ASIO driver has left a crap entry in registry?

Any help appreciated

Paul

[Wizzoboy]

PT needs an ASIO driver even if you are using your computers internal soundcard. Try downloading and installing the free Asio4all.

[Wizzoboy]

http://www.asio4all.org/

[64GTOBOY]

There is a thread somewhere where someone was having problems with a behringer interface http://duc.avid.com/showthread.php?t...ight=Behringer

[psft001]

Have already tried that - even uninstalled Pro Tools & the ASIO driver and did fresh install - still the same unfortunately!

[junkgear]

Have you tried trashing your preferences?

After trashing, try holding down the N key while PT starts. This will force a hardware refresh and will hopefully bring you to the Playback Engine settings, where you can choose the ASIO4ALL driver.

[psft001]

hi

yep - tried that - when starting PT & holding N it just crashes. Trying to start normally and get the error message!

[The Weed]

Had that error last night with my RME UFX along with completely distorted recording once I got PT open. Tried a different mic and different pre, same distortion issues. Holding the "N" key during PT launch either crashed the program or just brought up the Assertion error. Finally got PT to open and work and, during recording PT "burped" and then continued on okay.

Once I got done what needed to be recorded and sent out, I updated iLok License Center, Trashed Preferences and Databases, uninstalled PT 2018.1.0 using the third/clean option, rebooted, ran CCleaner until the Registry Cleaner ran clear, reinstalled PT 2018.1.0 and everything seems to be okay - I hope.

To the OP, you need a driver for your interface, either ASIO or Asio4All if you want it to work with Pro Tools. That said, you should contact Behringer support and ask if PT is supported with your interface.

[psft001]

Hi Peeps

did a full uninstall of ASIO drivers & Pro Tools - went through the Registry and removed any traces of ASIO - reboot - fresh install of everything and all working OK now! (3rd attempt!).

Many thanks for peoples comments/advice - much appreciated.

Fingers crossed all keep working now ;-)

[The Weed]

Originally Posted by The Weed

Had that error last night with my RME UFX along with completely distorted recording once I got PT open. Tried a different mic and different pre, same distortion issues. Holding the "N" key during PT launch either crashed the program or just brought up the Assertion error. Finally got PT to open and work and, during recording PT "burped" and then continued on okay.

Once I got done what needed to be recorded and sent out, I updated iLok License Center, Trashed Preferences and Databases, uninstalled PT 2018.1.0 using the third/clean option, rebooted, ran CCleaner until the Registry Cleaner ran clear, reinstalled PT 2018.1.0 and everything seems to be okay - I hope.

To the OP, you need a driver for your interface, either ASIO or Asio4All if you want it to work with Pro Tools. That said, you should contact Behringer support and ask if PT is supported with your interface.

Went back to 12.8.3 with a full uninstall/install, had the same Assertion error and completely distorted audio. Avid says in a knowledgebase article that it's a mismatch with the audio interface and to toggle between interfaces and/or set a correct buffer size. This did fix the issue in 12.8.3, although in 2018.1.0 I couldn't use the "N" key to get to the Playback dialogue, PT just crashed. In 12.8.3 I just toggled between my RME UFX and WASAPI within the affected session and could carry on. But, in either 12.8.3 or 2018.1.0, I know that my interface is correctly set and so is the buffer. I do remote recordings and can't see my screen when I do. Sure hope this doesn't happen during a session.