The headache that is H/W Buffer Size and Pro Tools
It's always good to know that someone reads what you right, so today I thought I'd help out a reader with a Pro Tools question that they have.
Joe wrote:
I posted here for help with pro tools crashing and I was helped so I thought I’d try again. I don’t know if this is the right place for this question but, when I try to record with pro tools I receive an error message saying I need to reduce the H/W Buffer size. Then I reduce it and try to record and it tells me to increase the buffer size. Basically this is keeping me from being able to record anything at all. Please someone help me with this issue. Thanks
 |
Digidesign Audiomedia III PCI Audio Card |  |
 |
US $123.91 | 47m |
 |
Pscy - Goa Trance Synth Loops for Digidesign Pro Tools | |
|
US $17.95 | 1h 43m |
This was a problem that plagued me the first time I tried running and installing Pro Tools on my old Dell system. This error, among others, led me to giving up on Pro Tools for a while. Anyway, on to the question.
The first thing you need to understand is the meaning of "H/W Buffer size". In basic terms, Pro Tools allows you to control, to some degree, the amount of stress you put your computer under. These related settings are called 'buffers'. In many ways, you could say that the buffer size determines how far ahead your computer is looking at the audio.
To adjust the hardware buffer size in Pro Tools:
1. Choose Setups --> Playback Engine.
The Playback Engine dialog box opens.
2. Select the setting that you want from the H/W Buffer Size drop-down list.
3. Click OK to accept the setting and close the dialog box.
As a general rule, when you are recording (and particularly when you're recording over dubs), you want to keep the H/W Buffer Size as low as possible. Low buffer size equals lower latency (or delay between what you play and when you hear it). Higher buffer size equals higher latency, meaning a delay between what you play and when you play it.
If your system struggles with processing, you may find that you need to increase the buffer size when you're mixing and mastering. Latency is not really an issue here, and you can put that extra processing power to use by running plug-ins.
It sounds as though that, when running Pro Tools, Joe's computer is being pushed to the limit, and does not have enough processing power to draw from. This could be because the specifications of his computer are not high enough to run the software effectively. It could also mean that there are a number of other programs and utilities running in the background.
Programs that load and run by default, such as anti-virus software, MSN Messenger, spyware, automatic updates, will all draw from you computers CPU, diverting processing power away from Pro Tools. Even things like screen savers can drag power away. This is why many people run their recording software on a dedicated audio computer, that runs the bare bones. Obviously a dedicated audio computer is a luxury not everyone can afford, but in saying that, if you want to start seriously recording, it will be difficult to run any audio software and hardware through a computer that doubles as your every day machine.
So, where to from here?
You could try disabling all non essential programs, utilities, updates etc., rebooting and giving ProTools a try then. If everything works fine, you could try implementing dual configurations or something, one for recording and one for everyday use. Long term though, you may want to think seriously about a dedicated machine. Before you buy, make sure you triple check the Digidesign website to make sure the machine is fully compatible with Pro Tools.
How did I solve the problem when it was happening to me? Well, you may not like the answer, but after weeks of screwing around with buffer settings and XP tweaks to reduce CPU load, the errors and latency issues drove me nuts. A short while after I took the plunge and picked up a second hand Apple PowerMac G5. Since doing this I've never received the H/W buffer size message and latency has never been an issue.
I'm not sure that answers your question Joe, or whether it helps. But if you are able to post you full system specs here, we may be able to give something more to work with.
Thank you for reading this post. You can now Read Comments (7) or Leave A Trackback.
Post Info
This entry was posted on Sunday, July 22nd, 2007 and is filed under ProTools, Tips and Tricks.You can follow any responses to this entry through the Comments Feed. You can Leave A Comment, or A Trackback.
Previous Post: Programming drums using Impulse and Ableton Live »
Next Post: Create your own mash up from scratch »
- The power of Ableton Live and Kid Beyond
- Programming drums using Impulse in Ableton Live
- Ibanez APEX 2 first impressions
- First thoughts on the AKAI MPD32
- Up to 50% off guitars in April from MusiciansFriend
- Close up of Tom Morello’s guitar gear
- Looks like the Akai MPD32 is the one for me
- How to create a song in Reason in less than 20 mins
- The AKAI MPD24 or the M-Audio Trigger Finger?
- Two new Fender Telecaster Signature models
July 23rd, 2007 17:33
hello. Me again. Thanks for posting this up I feel like a digitalburn celebrity. Here’s the system specs. If this helps you at all figure out my specific problem that’d be great. Thanks
July 23rd, 2007 23:11
See, this is the great/sucky thing about running Pro Tools. You know it is going to use your system to its fullest to produce the best recording possible. Great on a Mac and sucky on Windows.
On a mac, the OS only opens what you tell it to open on start up. And you can look at the dock to see what is running. You don’t have a bunch of background programs running that slow you system down without letting you know they are there. Also, Mac machines are standardized. A Macbook is a macbook is a macbook. Their software is set up for the specific hardware. No issues with finicky drivers.
I personally believe this is why Macs were, and arguably still are, the de facto computing system to choose when you have to do creative workings. Graphic Design, Music Recording, Video Editing, Photo Editing all take advantage of a system built to access all of the power built in.
If the gaming industry were to discover this, computer gaming would be awesome on a Mac.
July 24th, 2007 00:41
Joe - The system spec’s haven’t appeared in your comment, can you try reposting, or just cut and paste them into the comment form as text?
Spaceman Spiff - I agree with you on the Mac thing. I guess this is the reason why a majority of pro grade studios favor Macs. I notice a lot are still using the Powermac G4’s, which goes to show that if it works for you there’s no point in upgrading for the sake of it.
August 7th, 2007 19:29
I agree with Joe. Mac’s are so much better for creative software. Graphic designs applications to music producing software generally work better on Mac’s.
January 8th, 2008 18:35
So, here’s the thing. Like what you had to say and I did the same pc to mac switch-a-roo back in 06 to get my m-box to work without issues (whole n’other story with that one). Now, I just bought a factory 003 console with a new alumi-mac (complete with glare-screen) in the hopes that I could upgrade a working system, to system that works a little bit better. I will now report that the out-of-the-box system is about ready to go back into the box! There are many factors I can rant about but I will try to stay focused to your above comments. In short, can’t run pro-tools on Leopard, so I did the bootcamp thing, installed window sp2 and continued to install the gazillion pro-tools packs and plug-ins and serial numbers and, and, and… I can’t even record one stinkin’ track before the old buffer blowout occurs. Before you rain down on my already shattered “chrismas gift to me” high hopes, I’ve doctored this version of windows to be bare bones. Nothing is running in the background that doesn’t need to be. System: iMac intel duo, 2.4ghz, 2.0 ram, 500gig h/d with seperate 500gig external. The system shows a 2% usage when the crash occurs. I don’t know if I am looking for advise or willing to share this info as a fare warning to those who are thinking of doing the same. All is not lost, as I will first re-install Tiger over Leopard, all the while holding out for pro-tools to release a version compatable to Leopard. If that fails, to the land-fill we go! Thanks for listening, looking forward to comments.
January 20th, 2008 04:30
Man I got to be the dumest mother@#*%? on planet earth,I just sold my brand new mac to one of my home boys.No wonder he tried so hard to convince me that my toshiba windows xp would work just as good as the mac or better for this stupid protools M-BOX.I’ll never catch another mac for the price I got that one,know his studio is up and running and I’m still haveing h/w buffer nightmares.Does any body want to buy a toshiba,heck I’m willing to swap it out for a mac if thats cool with you.
February 6th, 2008 19:42
Joe,
I had the exact problem. I first resolved it by turning off Dual Core in the bios, I was able to return to Dual core mode by installing the hotfix for xp sp2 from here http://support.microsoft.com/kb/896256