Pro Tools First Crashes at the time of opening in Windows 10

[iamharivpillai]

Finally, some progress.
@JoelG thanks for suggesting the Behringer driver install.
After installing the driver, the PTF is no longer crashing.

However, it now gives me this error message upon opening.
"your audio is configured with a unsupported audio buffer size.
Please choose 32,64,128,256,512,1024 or 2048."

Per your suggestion, I did disable the Interface by going into Control Panel, Sounds, and disabled - to be sure Windows isn't going to try to output anything to it.


Also, did the following things mentioned in the Optimization Guide:
http://avid.force.com/pkb/articles/t...0-Guide#run_as


1.) Update Graphics Drivers

2.) Update Network Adapter Driver

3.) Adjust Power Options

4.) Supplemental: Disable USB Power Management (USB interfaces only)

[JoelG]

Glad you're getting somewhere. There should be a control panel for the Behringer (I haven't used any of their interfaces, so not familiar with it) that would allow you to set the buffer size and sample rate, try setting that before opening Pro Tools.

Joel

[iamharivpillai]

@JoelG Unfortunately, I am still unable to figure out how to access the Behringer Control Panel. I do not see anything like that in the Installed Programs. Looking for suggestions on how we can correct this error "your audio is configured with a unsupported audio buffer size.
Please choose 32,64,128,256,512,1024 or 2048."

[iamharivpillai]

I was able to find the Behringer Interface's Control Panel. All this while I was searching my Computer for the keyword "Behringer" and only accidentally did I see an unfamiliar icon in the Task Bar Tray that read "UMC Control Panel". Changed the Audio Buffer to 1024. PTF stopped showing that message again!

The funny part, again, is that I am presented with another error now, which reads like below:

Could not complete your request because Assertion in "..\ Source\ AAX\ CFicAAXWidget.cpp", line 822.

[JoelG]

I had that error on a buddy's computer. Running CCleaner and going through this KB article got it going: http://avid.force.com/pkb/articles/e...t-cpp-line-822

Joel

[iamharivpillai]

Thanks @JoelG

Yea, I was able to get around that error and PT finally got launched for the first time!

I tried navigating around for some time.

Created a Project. (It got saved in the cloud)
Tied Importing a .aif file into the Project. But I keep getting this error:
"AAE error 6 was encountered"

Looking up the Internet, came to know this is a notorious error with PT with many users facing it. With me being in PTF, is there a limitation with importing .aif file into a Project? Anyone knows the solution to this issue?

[Mahieu]

Hi, have you solved your problem?
Because I'm in the same situation today with my new laptop:
Pro Tools First 2019.6 / Windows 10
Dell laptop Inspiron 17'' 3793 bought in May 2020.
i7 1065G7 8Go NVMe 512 Geforce MX 230 USB 2.0 & 3.1
Realtek + Behringer 202HD
All drivers are up to date.
This setup crashes while it perfectly runs under my old computer Asus S200 i3 Windows 10 bought in 2010!
The crashes happen when I use Asio4All as well as when I use native drivers. I have tested all your hints and reinstalled the system, etc.
Each time the software exits after 10 seconds because the hardware seems to disappear. The messages are frequently (translated from French version):
"The hardware is used by another program", "hardware cannot be found" or "assertion CficAAXWidget.cpp line 994". Depending on the drivers set.

I'm wondering if it is not a problem of conflict between PT and another program. Indeed the only difference between my new and old computers is the additional software: Cortina, Skype phone, Voice assistance, etc. I have uninstalled Cortina and Skype but doesn't solve the problem.
I'm totally blocked, thank you for your kind help.

[JoelG]

I'd recommend disabling the Behringer interface in Control Panel\Sounds - both for playback and recording. This will keep Windows and other normal software from touching the interface and trying to take it over. You should still be able to select the ASIO driver in Pro Tools or any other DAW to use for recording.

Joel

[Mahieu]

Thank you Joel, but unfortunately your solution doesn't work.
I have tested my Dell 3793 i7 1065G7 in a standalone basis with only the embedded Realtek (drivers are up to date). Pro Tools still automatically crashes.
It is even worse when the Behringer 202HD is connected (Realtek deactivated or not).
In a word: blocking issue for me.
I must stop my work on this new computer (May 2020).