HD Native -9219 Errors

[johnnyz]

Started getting 9219 errors last nite,very disappointed ,after spending all the money for it,i am wondering if moving to hd10 will solve the issue or should i just upgrade to hdx and call it a day.The funny thing is it won't happen for a while ,and then bam there it is again,jz

[johnnyz]

Well i am going to update the firmware on the native card and see if that helps.jz

[tomhartman]

Originally Posted by johnnyz

Started getting 9219 errors last nite,very disappointed ,after spending all the money for it,i am wondering if moving to hd10 will solve the issue or should i just upgrade to hdx and call it a day.The funny thing is it won't happen for a while ,and then bam there it is again,jz

Welcome to native, whether it's Pro Tools, Logic, or Dave's Great Sequencer App.

Save for HDX.

Assured performance (unless you are talking about VI's).

TH

[johnnyz]

Well i did the firmware update ,and today all is well,in the meantime i will start savin for hdx.

[mgoorevich]

Latest everything here.
Still have 9219 errors, still muting phenomena on audio tracks.

[TimNielsen]

For many of us, the problem seems to be a combination of the Mac 2.8 GHz Harpertown processor Mac Pro and the HD native card. There appears to be a bug with this combination that causes constant CPU errors. There maybe other reasons to get this error, but this is a well-known bug between this particular model of Mac and the HD native card.

avid has been working on the problem although they have been reluctant to chime in here.

The error can manifest itself as either 9092, 9094, 9126, or 9129 errors, but All have the exact same text in the error message.

We are hoping that ProTools 10.2 fixes this error. At least I am.

It is still not fixed in ProTools 10.1.1

[lampmusic]

just wanted to chime in here and share my recent experiences.

Had a great opportunity through my local avid / digi dealer (that I've been working with for about 12 years) to upgrade both of our mac pro's (gen 3.1 - 2.8 octocore with 6gram / 10g ram respectively)

We were also disappointed with the random error situation with HD Native. I guess coming from the rock solid performance of our HD2 pcie systems kind of spoiled us when migrating to native.

In our experiences it was very frustrating to get an error in the middle of a bounce, printing a VI, etc. In our situation I narrowed it down to not being able to multi-task ie: no web browsing, no adobe photoshop, it seemed that doing something else would consistently get the various 9000 errors.

So for the past few months I would just leave the computer alone when it was doing some critical pro-tools processing

As of this past weekend we have been running HD native latest version 10.1.1 on 10.7.3 and not seeing the errors at all. I am now currently running 2 HD native systems on 2 Mac Pro's system 1: is the 2.4 8-core / 20g ram. system 2 is the 2.8 4-core 16g ram.

IMHO: HD Native is a totally different experience on the newer Mac pro's. It really feels like I'm back in the HD TDM PCIe world again.

I was reluctant to upgrade the mac pro's (ours were only about 3 yo) but I made the judgement call and got around $1500 ea for a trade in allowance. With new Mac pro's around the corner I knew the value would drop on our previous generation units.

Hope this information helps

[tomhartman]

Yes I'm using PT HD software with a Duet 2, and it's the same...you can't browse or do ANYTHING while PT is busy.

[mgoorevich]

Originally Posted by lampmusic

As of this past weekend we have been running HD native latest version 10.1.1 on 10.7.3 and not seeing the errors at all. I am now currently running 2 HD native systems on 2 Mac Pro's system 1: is the 2.4 8-core / 20g ram. system 2 is the 2.8 4-core 16g ram.

Open an audio suite plugin such as RX2 spectral repair or WNS or W43. Move the fader or change the parameter in this plugin, promptly hit play.
I have in 90% a 90xx error. Now, if I increase a buffer size from 128 to 256 to 512 it gets better, but still at some point I reach the error again.
Look at my system - it's a superior machine! I see no reason other than a hidden teaser to buy HDX. That's why Avid cannot fix it.
Same story as with G5 and Digi 002 when it came first.
Avid, ok I will buy hdx as soon as I sell my HD3 Accel...meanwhile please, fix the HDN. Please!

[tomhartman]

Originally Posted by mgoorevich

Open an audio suite plugin such as RX2 spectral repair or WNS or W43. Move the fader or change the parameter in this plugin, promptly hit play.
I have in 90% a 90xx error. Now, if I increase a buffer size from 128 to 256 to 512 it gets better, but still at some point I reach the error again.
Look at my system - it's a superior machine! I see no reason other than a hidden teaser to buy HDX. That's why Avid cannot fix it.
Same story as with G5 and Digi 002 when it came first.
Avid, ok I will buy hdx as soon as I sell my HD3 Accel...meanwhile please, fix the HDN. Please!

This is why I ditched Native. I get all the same performance as far as tracks, etc out the Duet 2 (I'm using the HD software) without any errors. Sucks though because the Duet 2 works only at 128, which is too high for comfort when tracking, so you have to use the Maestro thing. But it doesn't matter how good the latency figures are on Native if you have to deal with errors all day.

Of course this means you can't use the new Avid interfaces, which are great. But it just seems like more problems than it's worth. HDX is the way to go, you just have to win Lotto I guess.

TH