<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Avid&#8217;s &#8220;new thinking&#8221; &#8211; something for Digidesign and M-Audio?</title>
	<atom:link href="http://www.protoolerblog.com/2008/03/18/avids-new-thinking-something-for-digidesign-and-m-audio/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.protoolerblog.com/2008/03/18/avids-new-thinking-something-for-digidesign-and-m-audio/</link>
	<description>Pro Tools and pro audio blog</description>
	<lastBuildDate>Tue, 09 Mar 2010 15:37:30 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: stiff</title>
		<link>http://www.protoolerblog.com/2008/03/18/avids-new-thinking-something-for-digidesign-and-m-audio/comment-page-1/#comment-2992</link>
		<dc:creator>stiff</dc:creator>
		<pubDate>Tue, 25 Mar 2008 06:58:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.protoolerblog.com/2008/03/18/avids-new-thinking-something-for-digidesign-and-m-audio/#comment-2992</guid>
		<description>I&#039;ve expressed opinions close to that in the past. My thinking then was sort of  &quot;a more modular HD environment&quot;. I&#039;m not sure it&#039;s the BEST way, but it&#039;s most definitely a INTERESTING way,</description>
		<content:encoded><![CDATA[<p>I&#8217;ve expressed opinions close to that in the past. My thinking then was sort of  &#8220;a more modular HD environment&#8221;. I&#8217;m not sure it&#8217;s the BEST way, but it&#8217;s most definitely a INTERESTING way,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://www.protoolerblog.com/2008/03/18/avids-new-thinking-something-for-digidesign-and-m-audio/comment-page-1/#comment-2984</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Mon, 24 Mar 2008 20:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.protoolerblog.com/2008/03/18/avids-new-thinking-something-for-digidesign-and-m-audio/#comment-2984</guid>
		<description>My hope would be a single Pro Tools.  No more LE Vs. HD Vs. M.  If I need more power I should be able to purchase an accelorator.  If I need more I/O, I should be able to buy different interfaces...I would spend more then 10K for an I/O device with decent pre(s) and converters, but now I have to spend that on an HD I/O with...less then high quality converters and pre(s).  While Digidesign is at it they could fix the mac core audio bug in relation to Avid...</description>
		<content:encoded><![CDATA[<p>My hope would be a single Pro Tools.  No more LE Vs. HD Vs. M.  If I need more power I should be able to purchase an accelorator.  If I need more I/O, I should be able to buy different interfaces&#8230;I would spend more then 10K for an I/O device with decent pre(s) and converters, but now I have to spend that on an HD I/O with&#8230;less then high quality converters and pre(s).  While Digidesign is at it they could fix the mac core audio bug in relation to Avid&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Today&#8217;s Blogroll &#124; ControlRoom - Mixin' it with Dr. J</title>
		<link>http://www.protoolerblog.com/2008/03/18/avids-new-thinking-something-for-digidesign-and-m-audio/comment-page-1/#comment-2892</link>
		<dc:creator>Today&#8217;s Blogroll &#124; ControlRoom - Mixin' it with Dr. J</dc:creator>
		<pubDate>Tue, 18 Mar 2008 16:23:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.protoolerblog.com/2008/03/18/avids-new-thinking-something-for-digidesign-and-m-audio/#comment-2892</guid>
		<description>[...] Â Â Â Â Â Â Â Â Â Â Â Â  1.Â  Reactions to Digidesign&#8217;s &#8220;New Thinking&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Â Â Â Â Â Â Â Â Â Â Â Â  1.Â  Reactions to Digidesign&#8217;s &#8220;New Thinking&#8221; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
