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

[Ienjoyaudio]

Hi all. Just a quick update on this issue.

I finally got to installing 11.2. I also updated to ML 10.8.5. While I can't say that the issue is completely fixed. I DID notice an IMPROVEMENT in the 96k 24bit recording at 64 buffer on my HD native system.

My initial tests were 1 stereo instrument with SSD4
5 mono audio tracks each with Eleven.
1 Mono audio track with Waves GTR Bass

The best results came with the following settings:
Buffer: 64
Delay compensation: off
Dynamic plugin processing: off
Low Latency monitoring: off

Just running test tones and basic midi loops through the instruments the 9171 and 72 errors still came, but noticeably less frequent. As I said. Its an IMPROVEMENT but I don't think 64 buffer is ready to use for sessions or projects. But this was a step in the right direction.

The best and most usable settings were:
Buffer: 128
Delay Comp: Off
Dynamic Plugin Processing: Off
Low Latency Monitoring: On

Everybody else share your findings with 11.2

Thanks

[Boe Larsen]

Thanks for sharing. I don't see them that often anymore. But then again I run mostly with buffers above 1000...

[Mike496]

I'm getting this more and more now with post sessions. PT 11.2.1, HDX, 512 buffer, 2011 MBP, i7, 16 gigs of ram, ML. SSD BOOT drive, 2nd 7200 rpm internal drive for sessions.

[Mohur]

Which OS are you using

[Mike496]

I'm on Mountain Lion.

[Mohur]

Which version

[Mike496]

Greetings! ML 10.8.5

[jacko]

I used to run PT on OSX 10.8.x.
Here is my solution:

I installed OSX 10.6.8 on a new drive, then I installed PT 10.3.9 and all plugins, including the latest Waves V9.3 that are supported from 10.7 and above. Everything works super smooth and no more 9171 and 9172 errors.

10.6.8 works faster and better than 10.8.5 in many areas, including Pro Tools.

[neilvg]

Any latest with this, or over at the duc? I've been trying to speak with Avid Tech for a while and no real results and they hardly seem to acknowledge the issue. However, after much research I do NOT think that it is pro tools or HD|Native per se. I can get this to happen in Logic and with Internal Speakers/Audio set.

Also, my issue might be a little different, but I would definitely characterize it as CPU spiking.

Here is my system:
PT11HD
HD|Native
Mac pro 5,1 12 Core 3.06 (2012) 16gb RAM
11.2.1
Lynx Aurora (using HD Interface)

I can open slate VTM and just click SHOW/HIDE to display the tape machine graphic and get my CPU to hit 100% (or higher in Activity Mon) every time. If I'm playing audio, this will stop playback with an AAE error. VERY Odd. Switching instruments in VI's can cause this, and so does toggling record ARM repeatedly with several tracks with plugs on them grouped together at once.

I come recently from PTHD TDM where life was a bit limited but good. Now life is limited (in a different way) and not good at all.

I did DISABLE Hyperthreading (not use XCode but using a Sudo Command:
OFF: sudo nvram SMT=0
ON: sudo nvram -d SMT

This keeps it off even on reboot. It's obviously working because sys†em usage only shows 12 cores for me now. ***This makes quite a difference for the better! Another reason why I think it's OS based - or at least an interaction between multicore processing and a given software.

Like I said, I can get spikes to occur without using the HD|Native card and using a different software - one made by Apple.

Anybody else experiencing this Show/Hide CPU spike issue with VTM? It's an easy way to see it happening. When I called Slate, they weren't able to get this to happen but I've tried this on other machines and other vanilla installations - no difference - at least with AAX and AU.

But in general, even with my fast computer, I still get all sorts of CPU 'movement' on the monitors (activity mon and sys usage) without any real reason.

====

Does 10.6.8 work with 11HD? No?

[Benny_Cha_Cha]

Originally Posted by neilvg

Any latest with this, or over at the duc? I've been trying to speak with Avid Tech for a while and no real results and they hardly seem to acknowledge the issue. However, after much research I do NOT think that it is pro tools or HD|Native per se. I can get this to happen in Logic and with Internal Speakers/Audio set.

Also, my issue might be a little different, but I would definitely characterize it as CPU spiking.

Here is my system:
PT11HD
HD|Native
Mac pro 5,1 12 Core 3.06 (2012) 16gb RAM
11.2.1
Lynx Aurora (using HD Interface)

I can open slate VTM and just click SHOW/HIDE to display the tape machine graphic and get my CPU to hit 100% (or higher in Activity Mon) every time. If I'm playing audio, this will stop playback with an AAE error. VERY Odd. Switching instruments in VI's can cause this, and so does toggling record ARM repeatedly with several tracks with plugs on them grouped together at once.

I come recently from PTHD TDM where life was a bit limited but good. Now life is limited (in a different way) and not good at all.

I did DISABLE Hyperthreading (not use XCode but using a Sudo Command:
OFF: sudo nvram SMT=0
ON: sudo nvram -d SMT

This keeps it off even on reboot. It's obviously working because sys†em usage only shows 12 cores for me now. ***This makes quite a difference for the better! Another reason why I think it's OS based - or at least an interaction between multicore processing and a given software.

Like I said, I can get spikes to occur without using the HD|Native card and using a different software - one made by Apple.

Anybody else experiencing this Show/Hide CPU spike issue with VTM? It's an easy way to see it happening. When I called Slate, they weren't able to get this to happen but I've tried this on other machines and other vanilla installations - no difference - at least with AAX and AU.

But in general, even with my fast computer, I still get all sorts of CPU 'movement' on the monitors (activity mon and sys usage) without any real reason.

====

Does 10.6.8 work with 11HD? No?

Pretty sure PT 11 requires 10.8.4. Which OS version are you running?

Great tip on disabling hyperthreading. Thanks for that. Now I can retire my Automator action.