-9171 and -9172 errors with Pro Tools HD 10.3 on HDX

[SHIRK]

EastWest Play v2.x
Synthogy Ivory v1.x
BFD 2

[Cliffy_Boy]

As Shirk said:

"I've noticed a HUGE improvement in the stability of my HDX system since cleaning up some plugin redundancies that had between .dpm and .aax plugins a few weeks ago. I went through and removed any .dpm plugin that had an .axx substitute. "

my foirst day since 10.3.2. on 10.8.2 with HDX with no 9171 or 9172. had to reboot in safe mode to make the other 9xxx go away.

One full day of tracking and mixing without a stop.

Here's keeping my fingers crossed.

Thank you Shirk and the other "beta" testers who are doing AVID's job well.

[Boe Larsen]

Originally Posted by Andy R

@SHIRK / Boe / psmworld - Are you guys using any Avid, or 3rd party VI?

Thanks in advance.

Hm - using VIs now - and it's back - but not as bad.
Boe

[Andy R]

Well... I'm an idiot... lol. I only looked at the PT10 compatibility docs and assumed HDX was compatible with Mountain Lion. It's not.

I've created a new 10.7.4 boot drive, deleted any AAX dups, and will be testing the new AAX versions of VEP5, Vienna Instruments, RX2, and Kontakt 5 (as well as Avid's RTAS VI). I'll keep you posted.

Sorry for any confusion I may have created.

[crizdee]

Originally Posted by Andy R

Well... I'm an idiot... lol. I only looked at the PT10 compatibility docs and assumed HDX was compatible with Mountain Lion. It's not.

I've created a new 10.7.4 boot drive, deleted any AAX dups, and will be testing the new AAX versions of VEP5, Vienna Instruments, RX2, and Kontakt 5 (as well as Avid's RTAS VI). I'll keep you posted.

Sorry for any confusion I may have created.

Hi,

I'm sure from 10.3 HDX it is compatible with Mountain Lion.

The compatibility page you viewed was probably for 10.2 september update.


Chris

[Andy R]

I am, like,the spreader of misinformation... ^_^

I would be bummed that I spent all that time creating the new boot drive... BUT I'm getting no -9171 and -9172 errors with 10.7.5. (sorry, 5 not 4)

No stops at all, with sessions that were a train wreck in Mountain Lion.

[SHIRK]

Originally Posted by Andy R

... BUT I'm getting no -9171 and -9172 errors with 10.7.5. (sorry, 5 not 4)

No stops at all, with sessions that were a train wreck in Mountain Lion.

What buffer settings are you working at?

I started overdubs yesterday on an 88.2k session and left the buffer at 128 (the lowest setting for 88.2k and up, I believe) At 128 I couldn't get the system to even begin playback. I kept getting the "automation data is too dense.." message (or something to that effect). I quickly changed the buffer to 512 and all was fine. Not a single glitch the rest of the session. I skipped the 256 buffer setting just to play it safe, but perhaps I need to give that a look as well for testing purposes.

[Andy R]

With respect to H/W buffers and latency…

In my experience, HDX is equal to, or worse than HD. Under any version, and even with a modest native load, HDX only plays back at the two highest buffer settings.

Example— a session running on both HDX & Natively.

Native 96k session at H/W Buffer 1024 - CPU (Native) = 30-32%. Change the H/W Buffer 512 - refuses to play back. (-9171 and -9172)

Same session, HDX 96k session at H/W Buffer 1024 - CPU (Native) = 20-22%. Change the H/W Buffer 512 - refuses to play back. (-9171 and -9172)

This happens with PT 10.3.2 in either Lion or Mountain Lion.


On a related issue, some people at Gearslutz are saying putting a VI into record mode defaults to low latency. I'm not finding that, and I've measured the VI latency, so I'm not expressing opinion.
Anyone seeing what they're reporting?

Interestingly, in Mountain Lion, when you record enable to merge MIDI onto existing VI MIDI, the H/W Buffer latency is suddenly reflected in the existing MIDI (delay comp is disabled?). In 10.7.4, this does not happen.

I wonder if HDX is inferior to Native when using VI? I'd love for Avid to chime in on that. I'd buy a Native card to use for composing, and use HDX track intensive stuff.

Finally, I'd like to point out that, with all the 3rd party AAX & RTAS, it's got to crazy difficult to offer support... For example, I run a lot of Lexicon PCM, maybe that's part of my issue. In future, I will run everything but Avid VI in VEP5.

Either way, I'm sure Avid, and the their many experienced Beta guys are doing their best to address these issues.

Okay, back to work...:thumbsup:

[BigMeany]

Originally Posted by SHIRK

I've noticed a HUGE improvement in the stability of my HDX system since cleaning up some plugin redundancies that had between .dpm and .aax plugins a few weeks ago. I went through and removed any .dpm plugin that had an .axx substitute.

Doing this might make backwards compatibility difficult for some if you need to open older sessions that used .dpm plugins. (Maybe I'm wrong on that and PT10 will automatocally know to use the aax version instead) Anyhow, this has dramatically decreased my -9171 and -9172 errors. In fact I haven't had one in a few weeks. Not one. (knock on wood).

I had pretty much parked the buffer at 512 for the last month and this was a big help as well. Today while mixing a 44.1k session, I decided to knock the buffer down to 128. Not a single error all day. Let's see what tomorrow brings...maybe I'll try 64.

Hopefully this helps some of you out.

This didnt work for me.

[DigiTechSupt]

Pro Tools 10.3.3 has just been released and includes improvements that should help with these errors. Please let us know your results, and thank you again for your patience!

http://avid.force.com/pkb/articles/e...-3-3-Downloads