<?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: Building a Project Studio for $1000 or Less, Part II</title>
	<atom:link href="http://blog.shure.com/shure-notes/building-a-project-studio-for-1000-or-less-part-ii/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.shure.com/shure-notes/building-a-project-studio-for-1000-or-less-part-ii/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=building-a-project-studio-for-1000-or-less-part-ii</link>
	<description>Legendary Performance</description>
	<lastBuildDate>Fri, 24 May 2013 11:42:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Building a Project Studio for $1000 or Less, Part I &#124; Shure Blog</title>
		<link>http://blog.shure.com/shure-notes/building-a-project-studio-for-1000-or-less-part-ii/#comment-218</link>
		<dc:creator>Building a Project Studio for $1000 or Less, Part I &#124; Shure Blog</dc:creator>
		<pubDate>Thu, 10 Jan 2013 18:33:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.shure.com/?p=6476#comment-218</guid>
		<description><![CDATA[[...] Building a Project Studio for $1000 or Less, Part II  In the second of our two-part series, we’ll look at the remaining six project studio fundamentals – from considering all-important acoustics to choosing gear that will see you through your sophomore effort and beyond. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Building a Project Studio for $1000 or Less, Part II  In the second of our two-part series, we’ll look at the remaining six project studio fundamentals – from considering all-important acoustics to choosing gear that will see you through your sophomore effort and beyond. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
