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

[DetroitT]

It has to be HDX. Firmware, Graphic related?...too may times I think i've narrowed it and eliminated it, it's back in a different scenario. (VI or no Vi's I get these.)
My 10.3.x TDM/magma systems have never had these errors.
They seem to ebb and tide here.

[therecordco]

Originally Posted by MARVINBASS

Hello and welcome to our nightmare!!
Make sure your H/W Buffer is 512 or higher. Let us know what happens then.

Thanks Marvin. "glad" to be here. It's been 512 or 1024 since the HDX install. Never below. Issues started and persisted at those buffer sizes.

[MixerGuy]

Originally Posted by psmworld

this will happen when the cpu usage reaches an amount. some rtas plugs use much cpu so it will increase usage sooner.

sometimes it will also happen on low cpu usage, when osx does some work in the background.

pls open digitest and tell me the fpga versions of your card (its under slot info)

FPGA Version R = 1.07 T = 1.02 (for both of them)


what exactly does this mean? (just curious why you asked)

thanks

[MixerGuy]

Originally Posted by MARVINBASS

What Hardware Buffer size are you on??
Try 512
Also put the processors to 6 and try it again.

I was on 512.

I will switch to 1024 and 6 processors - and see if i get any errors

thanks

[psmworld]

Originally Posted by MixerGuy

FPGA Version R = 1.07 T = 1.02 (for both of them)


what exactly does this mean? (just curious why you asked)

thanks

i want to know if our hdx cards are on the same firmware!

[ronwasserman]

From Console right at 9171 error:


12/10/12 10:09:52.020 PM sandboxd[2085]: ([2063]) mdworker(2063) deny file-read-data /Library/Application Support/VSL/libveproshared.1.0.0.dylib (import fstype:hfs fsflag:4A09000 flags:200000056 diag:0 uti:com.apple.quicktime-movie plugin:/Library/Spotlight/CoreMedia.mdimporter - find suspect file using: sudo mdutil -t 2438167)
12/10/12 10:09:52.041 PM sandboxd[2085]: ([2063]) mdworker(2063) deny file-read-data /Library/Application Support/VSL/libveproshared.1.0.0.dylib (import fstype:hfs fsflag:4A09000 flags:200000056 diag:0 uti:com.apple.quicktime-movie plugin:/Library/Spotlight/CoreMedia.mdimporter - find suspect file using: sudo mdutil -t 2438167)
12/10/12 10:30:03.426 PM WebProcess[2181]: Can't open input server /Library/InputManagers/QuicKeysIM
12/10/12 10:30:03.636 PM Safari[2180]: Can't open input server /Library/InputManagers/QuicKeysIM
12/10/12 10:30:11.807 PM PluginProcess[2188]: Can't open input server /Library/InputManagers/QuicKeysIM
12/10/12 10:31:15.000 PM kernel[0]: Sandbox: sandboxd(2195) deny mach-lookup com.apple.coresymbolicationd
12/10/12 10:31:16.362 PM sandboxd[2195]: ([2177]) mdworker(2177) deny file-read-data /Library/Application Support/East West/Frameworks/QtCore.framework/Versions/4/QtCore (import fstype:hfs fsflag:4A09000 flags:200000056 diag:0 utiublic.mpeg-4 plugin:/Library/Spotlight/CoreMedia.mdimporter - find suspect file using: sudo mdutil -t 2352903)
12/10/12 10:31:16.410 PM sandboxd[2195]: ([2177]) mdworker(2177) deny file-read-data /Library/Application Support/VSL/libveproshared.1.0.0.dylib (import fstype:hfs fsflag:4A09000 flags:200000056 diag:0 utiublic.mpeg-4 plugin:/Library/Spotlight/CoreMedia.mdimporter - find suspect file using: sudo mdutil -t 2352903)
12/10/12 10:31:16.422 PM sandboxd[2195]: ([2177]) mdworker(2177) deny file-read-data /Library/Application Support/VSL/libveproshared.1.0.0.dylib (import fstype:hfs fsflag:4A09000 flags:200000056 diag:0 utiublic.mpeg-4 plugin:/Library/Spotlight/CoreMedia.mdimporter - find suspect file using: sudo mdutil -t 2352903)
12/10/12 10:31:16.434 PM sandboxd[2195]: ([2177]) mdworker(2177) deny file-read-data /Library/Application Support/VSL/libveproshared.1.0.0.dylib (import fstype:hfs fsflag:4A09000 flags:200000056 diag:0 utiublic.mpeg-4 plugin:/Library/Spotlight/CoreMedia.mdimporter - find suspect file using: sudo mdutil -t 2352903)
12/10/12 10:31:16.441 PM sandboxd[2195]: ([2177]) mdworker(2177) deny file-read-data /Library/Application Support/VSL/libveproshared.1.0.0.dylib (import fstype:hfs fsflag:4A09000 flags:200000056 diag:0 utiublic.mpeg-4 plugin:/Library/Spotlight/CoreMedia.mdimporter - find suspect file using: sudo mdutil -t 2352903)
12/10/12 10:31:21.112 PM Console[2198]: Can't open input server /Library/InputManagers/QuicKeysIM

----
Does this mean anything? Should we be posting this kind of info? (apparently there is some characters in there that cause a smiley face.....don't know how to change that.)

[MARVINBASS]

Hi Ron,
I know they need the .dlog files that are in
~>Library>Logs>AvidLogFiles

Maybe Tech Supprt can chime in and give you an email to send them to.

Cheers!

[MixerGuy]

buffer at 1024
processors at 6

no errors today.

[DetroitT]

How do you read Library>Logs>AvidLogFiles?
In Console it's just ???fonts (.dlog)

[Andy R]

I've been doing pretty some testing, using this as a guide.

http://avid.force.com/pkb/articles/e...ve-errors-9071

I found these unlisted factors causing -9171 and -9172 errors:

- idle, non-sleepable, Firewire 800s drive make 'write' sound, error occurs
- Using Structure
- Using VI


-------------

Because this appears to be a buffer issue, I'll report these additional behaviors.


1 - In an effort to stop -9171 and -9172 errors in an audio only cached 120 voice film mix, I raised the buffer from 512 to 1024. This resulted in my dialogue being out of sync, and what sounded like a 2 sample discrepancy in bussed tracks that was causing phase cancelation.

I saved the session with the new buffer setting (PT retains session buffer settings), and restarted. Problem went away.

2 - Despite the above session being cached (14gig) and at max H/W Buffer, playback start causes intermittent -9171 and -9172 errors, accompanied by a split second of garbled phase-y audio.

3 - When changing the buffer settings in a MIDI and audio session, Avid VI's exhibited a 100 sample offset, while VEP5 remained perfectly in time. (cause is RTAS non-adaptive delay comp?)

Saving as the new buffer and restart did not fix it.

--------

Note: The film session had basically no CPU load at all, HDX was nowhere near overtaxed, and the MIDI/Audio sessions reported zero CPU spikes.

Hope this helps in the debug process.