-9171 and -9172 errors Pro Tools 11 | HD

[Skwaidu]

Originally Posted by ArKay99

Have you voted on the ideascale bug report I made?
I have a feeling this will come down to a firmware update on the HDX card...IMHO the issue is with the FPGA mixer.

Could you tell more please?

[ArKay99]

Originally Posted by Skwaidu

Could you tell more please?

Just a hunch. If you run the software without the hardware, i.e. use the AVID Core Audio Manager and bypass the DSP the error doesn't manifest. Coupled with the fact that it doesn't manifest when buffer settings are 512 or higher.

[Skwaidu]

Originally Posted by ArKay99

Just a hunch. If you run the software without the hardware, i.e. use the AVID Core Audio Manager and bypass the DSP the error doesn't manifest. Coupled with the fact that it doesn't manifest when buffer settings are 512 or higher.

Well if it was possible with a FW upgrade that would be amazing. But we haven't heard from one and the bug has been around for a long time now...

[ArKay99]

Originally Posted by Skwaidu

Well if it was possible with a FW upgrade that would be amazing. But we haven't heard from one and the bug has been around for a long time now...

That's the way FPGA's work. When they are powered on the firmware that lives either in a separate section of the FPGA or a memory chip near it will 'set up' that chip for whatever the program is written to do.

But...agreed the bug has been around for a long time now.

[m4tune]

AAE -9172 says:
Audio processing could not complete due to conflicts with other CPU tasks…
I think all hardware related guessings, including AVID's own (…or a potential clocking issue. and so on…) are BS here.
The error occurs on all systems, no matter HDX, HD native or native only. And at all buffer settings.
I can't get it how this elementary error is constantly ignored by the company. They're even ignorant enough not to say a single word about it.
What kind of support is this?
It's getting absurd and I'm getting more and more pissed.

[Skwaidu]

Originally Posted by m4tune

AAE -9172 says:
Audio processing could not complete due to conflicts with other CPU tasks…
I think all hardware related guessings, including AVID's own (…or a potential clocking issue. and so on…) are BS here.
The error occurs on all systems, no matter HDX, HD native or native only. And at all buffer settings.
I can't get it how this elementary error is constantly ignored by the company. They're even ignorant enough not to say a single word about it.
What kind of support is this?
It's getting absurd and I'm getting more and more pissed.

Indeed. Thankfully I do mixing most of the time, not being able to record software synths without lag or CPU errors on a "professional production DAW" is incredibly frustrating.

[brianjanthony]

I was plagued constantly by this on my HDN system, esp with a co install on 10.8.

Honestly, since upgrading to Yosemite and ONLY installing 11 and not doing a co-install of 10, I haven't had the error since.

[Skwaidu]

Originally Posted by brianjanthony

I was plagued constantly by this on my HDN system, esp with a co install on 10.8.

Honestly, since upgrading to Yosemite and ONLY installing 11 and not doing a co-install of 10, I haven't had the error since.

Anyone able to confirm or second this?

[ArKay99]

Originally Posted by Skwaidu

Anyone able to confirm or second this?

I sold my HDX rig over this and other political reasons since about the time Brian posted. However, I've gone to a new Mac Pro trashcan with Yosemite and only an install of PT 12HD. No Core Audio, using the Apollo Thunderbolt drivers. Now I get a -6101 error. CPU spikes just like before and it goes away with a buffer of 512 or above, just like the -9171 or -9172.

BTW, I opened a support case over at IdeaScale for the -9171 and -9172 error, it got about 40 likes and then was removed...

[Skwaidu]

Originally Posted by ArKay99

I sold my HDX rig over this and other political reasons since about the time Brian posted. However, I've gone to a new Mac Pro trashcan with Yosemite and only an install of PT 12HD. No Core Audio, using the Apollo Thunderbolt drivers. Now I get a -6101 error. CPU spikes just like before and it goes away with a buffer of 512 or above, just like the -9171 or -9172.

BTW, I opened a support case over at IdeaScale for the -9171 and -9172 error, it got about 40 likes and then was removed...

Wow. What would it take for Avid to aknowledge this?

Tho "good" to know that it's not the old Mac Pro either, so no need for a new trashcan anytime soon...