UAD triggering 9171, 9172 errors?

[xq3js]

Hi
I have recently updated my UAD to 6.5.2 and using the new LA-2A plugs quite a lot.
Now I get those 917X errors when I put the new LA-2A on screen.
This is not consistant and doesn't happen all the time.

UAD is dsp dependent so it shouldn't affect the CPU load.
Maybe the graphics are causing spikes in the CPU usage?

I've experienced the MDW EQ (AAX) and some McDSP (AAX) to trigger the same errors when putting them on screen.

Has any of you here experiencing the same issue?
Does updating to 10.3.4 do any good?

Thanks for the help.

Pro Tools HD Native 10.3.3
Mac OS 10.7.4
Mac Pro 2x2.4 Quad 16GB RAM

[Drew Mazurek]

Sorry I can't be of any help except to say that I have a similar setup and I don't see these.

[xq3js]

Lexicon224 triggers the 9172 error as well.
Almost 100% of the times...
Updated PT to 10.3.4 but no difference.

[Darryl Ramm]

Originally Posted by xq3js

Lexicon224 triggers the 9172 error as well.
Almost 100% of the times...
Updated PT to 10.3.4 but no difference.

You've not really mentioned the interesting/useful stuff.

What exact UAD hardware do you have?

What are the Playback engine settings... esp. IO buffer size (but give them all...).

What sample rate? What else is going on in the session? How many native plugins? What type? How many total tracks? Are you using usual suspect things like any VIs in this session?

How many instances of these plugins are you tryign to run? And exactly what versions of these plugins are you running. e.g. note the significant load differences UAD spec for say LA-2A (analog classics) vs. LA-2A Gray (classics leveler collection).

What if you create a new session and try these plugs on a new track?

Now is time to double check you have all systems optimizations applied to your Mac. WiFi and blutooth turned off, spotlight fully disabled for every drive (not just the system drive), time machine disabled, etc. Make sure every last optimization is applied. Even if you have been though all this before go check again. The latency involved in UAD processing can make the system more sensitive to not doing these optimizations correctly.

How many physical and virtual cores does your Mac have? What GPU is in the Mac? Check if there are updated drivers for it.

Darryl

[xq3js]

yeah sorry about the lack of info.
I'm just too stuck with this PT10 giving me too much trouble.
really shuts off your creativity when errors keep stopping playback.

my uad is UAD OCTO with software ver 6.5.2
HD Native with HW buffer set to 512
14 processors with 90% limit
delay comp set to long
cache 8gb

for this particular session, it is 48k 32b
cpu(native) meter reads at about 60%
(pt becomes so unstable when the meter goes beyond 50%. that's one of the reason why i bought the uad)
no VIs in this session

now the EMT140 is triggering the error as well.
so not only the LA2As but ALL uad plugins i guess.
whenever i click open the GUI the 9172 shows up.

I'm guessing its probably my system or hardware config since no one else seems to have this problem.

Thanks anyway for the tips tho.
Really appreciate it.

[Darryl Ramm]

Can you provide all the other info asked for as well.

If you run at 1024 IO buffer does it get stable?

Remember that most of these problems are overlooking some little thing in systems optimizations. It may have been like that for ages, running on the edge and then one other small things changes and it all goes to hell.

You have a dual quad Msac Pro, presumably with hypetrthreading. So as always I'd try to force Pro Tools to not try to use the hyperthread cores and start with #CPU=#physical cores-1. .e.g set #CPU=7, and I usually just try 99%. You might also try #CPU=6. Leave it set there even if you still have problems, while you debug other things. For debugging its just important to try values well away from the 16 cores implied from hyperthreading.

Darryl

[xq3js]

Thanks
I'll try reducing the cores first

[crizdee]

Hi,

Is this definitely only happening with the UAD plugins?

Have you got the option for extra buffering selected in the UAD control panel?

I've got a quad and use the same UAD plugs you mention and have never seen this issue.

What troubleshooting steps have you taken with the UAD plugs and card?

Have you tried another PCIe slot?

Have you tried a complete uninstall and reinstall of the UAD software....

http://www.uaudio.com/support/uad/tr...stall-mac.html



Chris