the beauty of hardware buffer errors

  • Thread starter Thread starter iownrocknroll
  • Start date Start date
I

iownrocknroll

New member
Well...it's back and better then ever, good ol' error -9129 increase your hardware buffer size

Quad core intel 2.3Ghz
4 GB DDR2 6400
Windows XP SP3
Seagate SATA 1 TB 7200 RPM drive 32 MB Cache
2 UAD 1 cards.

on this sessions my UAD cards are running around 55%
RTAS is running around 30% disk around 4-10%
currently my hardware buffer size is set at 1024 on play back.
cpu limit 85%
cache level is 2,
DAE buffer normal
rtas processor is set to 4.
I have tried setting RTAS processor to 3, tried setting affinity to 3 then rtas to 2.

I'm not sure what to do. This happens after 1 minute and 7 seconds into bouncing a song down.

I'm not sure what the issue is, but I have been having nothing but constant hardware buffer errors with pro tools 8.

I am considering re-installing windows.

any more thoughts?
 
more info...

plugins on the session Wave API Bundle (pro tools 8 compatible)
47 tracks
 
have you recently installed or changed anything with your computer?
I had a guy who changed his anti-virus software up and he started getting buffer errors soon after. He disabled/closed it and it fixed things.


Try deleting prefs, cleaning up Windows, etc.
 
did all of the following
i'm going to reinstall

nothing but issues after upgrading for 6.4 on my digi 001 to the 003
 
Set the number of RTAS processors to 3.

Never use all 4.

What you're doing is actually reserving those processors for use with Pro Tools. This then means that no other processes can be run easily!!!

Try that and let me know if it helps.

EDIT - Ooops, having re-read your post, you've already done that. Not sure what else to suggest right now, but my advice still stands.
 
Last edited:
IMO you would have been better off going for a faster dual core instead of a slow quad. You're not utilizing all four cores.
 
iownrocknroll
Hey man i had the exact problem on a 38 track session at 44.1hz 24 bit
on a 32bit vista PTm8 at around 3 min every time at the same spot. I tracked down a carupt audio file that shot the cpu up to max on every pass the way i got around that is i printed that track up to the corupt point and then again after and cross faded them together then made the old track inactive ...
Hope this helps
 
stab in the dark,

is your audio on the system drive???

<edit> to michaelSHK, i disagree about the quad core thing,


even if <for arguments sake> protools could only use/access two cores,

the operating system itself is gonna be using the other two.

its like havin a core two duo for your system, and a whole other one for protools :)
 
no....i'm not sure what the problem is.
maybe just to many plugins?

I dunno
 
You must log in or register to reply here.
Back
Top