<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: The headache that is H/W Buffer Size and Pro Tools</title>
	<atom:link href="http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/</link>
	<description>Electronic Music Production</description>
	<pubDate>Fri, 25 Jul 2008 06:24:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Ben</title>
		<link>http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-515</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Wed, 06 Feb 2008 19:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-515</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>Joe,<br />
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 <a href="http://support.microsoft.com/kb/896256">http://support.microsoft.com/kb/896256</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: larry</title>
		<link>http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-490</link>
		<dc:creator>larry</dc:creator>
		<pubDate>Sun, 20 Jan 2008 04:30:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-490</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>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&#8217;ll never catch another mac for the price I got that one,know his studio is up and running and I&#8217;m still haveing h/w buffer nightmares.Does any body want to buy a toshiba,heck I&#8217;m willing to swap it out for a mac if thats cool with you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-469</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Tue, 08 Jan 2008 18:35:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-469</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>So, here&#8217;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&#8217;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&#8217;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&#8230; I can&#8217;t even record one stinkin&#8217; track before the old buffer blowout occurs.  Before you rain down on my already shattered &#8220;chrismas gift to me&#8221; high hopes, I&#8217;ve doctored this version of windows to be bare bones.  Nothing is running in the background that doesn&#8217;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&#8217;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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry</title>
		<link>http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-130</link>
		<dc:creator>Barry</dc:creator>
		<pubDate>Tue, 07 Aug 2007 19:29:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-130</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>I agree with Joe.  Mac&#8217;s are so much better for creative software.  Graphic designs applications to music producing software generally work better on Mac&#8217;s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: digitalburn</title>
		<link>http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-107</link>
		<dc:creator>digitalburn</dc:creator>
		<pubDate>Tue, 24 Jul 2007 00:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-107</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>Joe - The system spec&#8217;s haven&#8217;t appeared in your comment, can you try reposting, or just cut and paste them into the comment form as text?</p>
<p>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&#8217;s, which goes to show that if it works for you there&#8217;s no point in upgrading for the sake of it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: - Spaceman Spiff -</title>
		<link>http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-106</link>
		<dc:creator>- Spaceman Spiff -</dc:creator>
		<pubDate>Mon, 23 Jul 2007 23:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-106</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>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.  </p>
<p>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&#8217;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.</p>
<p>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.  </p>
<p>If the gaming industry were to discover this, computer gaming would be awesome on a Mac.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-105</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Mon, 23 Jul 2007 17:33:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalburn.org/the-headache-that-is-hw-buffer-size-and-pro-tools/#comment-105</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>hello. Me again. Thanks for posting this up I feel like a digitalburn celebrity. Here&#8217;s the system specs. If this helps you at all figure out my specific problem that&#8217;d be great. Thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.311 seconds -->
