<?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: Studio Upgrades</title>
	<atom:link href="http://www.richardcleaver.com/2006/10/22/studio-upgrades/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.richardcleaver.com/2006/10/22/studio-upgrades/</link>
	<description>the journey</description>
	<lastBuildDate>Mon, 30 Jan 2012 17:14:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Richard Cleaver</title>
		<link>http://www.richardcleaver.com/2006/10/22/studio-upgrades/comment-page-1/#comment-11309</link>
		<dc:creator>Richard Cleaver</dc:creator>
		<pubDate>Sat, 28 Oct 2006 01:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardcleaver.com/?p=1174#comment-11309</guid>
		<description>I&#039;ll reserve judgement on PT egocentricity :-)

There was a major change in the PT platform architecture and some of the plugins had to be updated.

Looks like the same will eventually be true for VST users and some older vst plugins. 

From the Steinberg website:

* What is VST3?
      VST3 is the next major revision of Steinberg’s Virtual Studio Technology and follows VST 2.4, which is the latest current version of VST. VST3 is a plug-in standard, not a product or host application. In order to run VST3 plug-ins or instruments, the host application must also support VST3.

* Can I still use my existing plug-ins and instruments?
      Yes. Existing VST 2.4 plug-ins and instruments are fully compatible with Cubase 4. Any plug-in or instrument older than VST 2.4 must be tested and potentially updated.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll reserve judgement on PT egocentricity <img src='http://www.richardcleaver.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>There was a major change in the PT platform architecture and some of the plugins had to be updated.</p>
<p>Looks like the same will eventually be true for VST users and some older vst plugins. </p>
<p>From the Steinberg website:</p>
<p>* What is VST3?<br />
      VST3 is the next major revision of Steinberg’s Virtual Studio Technology and follows VST 2.4, which is the latest current version of VST. VST3 is a plug-in standard, not a product or host application. In order to run VST3 plug-ins or instruments, the host application must also support VST3.</p>
<p>* Can I still use my existing plug-ins and instruments?<br />
      Yes. Existing VST 2.4 plug-ins and instruments are fully compatible with Cubase 4. Any plug-in or instrument older than VST 2.4 must be tested and potentially updated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose</title>
		<link>http://www.richardcleaver.com/2006/10/22/studio-upgrades/comment-page-1/#comment-11281</link>
		<dc:creator>Jose</dc:creator>
		<pubDate>Fri, 27 Oct 2006 03:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardcleaver.com/?p=1174#comment-11281</guid>
		<description>Well, me being a pc user I find that weird. Once I install and register any vst plugin, it works well almost everywhere. There was once a compatibility issue with waves plugins and Sonar 5 that was fixed in Sonar 5.2 and improved in 6, but the plugins are the same. I guess PT is too egocentric.</description>
		<content:encoded><![CDATA[<p>Well, me being a pc user I find that weird. Once I install and register any vst plugin, it works well almost everywhere. There was once a compatibility issue with waves plugins and Sonar 5 that was fixed in Sonar 5.2 and improved in 6, but the plugins are the same. I guess PT is too egocentric.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Cleaver</title>
		<link>http://www.richardcleaver.com/2006/10/22/studio-upgrades/comment-page-1/#comment-11280</link>
		<dc:creator>Richard Cleaver</dc:creator>
		<pubDate>Fri, 27 Oct 2006 00:59:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardcleaver.com/?p=1174#comment-11280</guid>
		<description>Hey Matt,

I will post a review of the Korg. Bottom line? Great keyboard.

And the Lonestar is still a favourite.</description>
		<content:encoded><![CDATA[<p>Hey Matt,</p>
<p>I will post a review of the Korg. Bottom line? Great keyboard.</p>
<p>And the Lonestar is still a favourite.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Cleaver</title>
		<link>http://www.richardcleaver.com/2006/10/22/studio-upgrades/comment-page-1/#comment-11279</link>
		<dc:creator>Richard Cleaver</dc:creator>
		<pubDate>Fri, 27 Oct 2006 00:58:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardcleaver.com/?p=1174#comment-11279</guid>
		<description>Jose: yes, you need to ensure that your plugins are compatible with 7.x. Some are, some aren&#039;t.

You can see the full list of plugins and the supported versions by Pro Tools platform &lt;a href=&quot;http://www.digidesign.com/index.cfm?langid=1&amp;navid=71&amp;itemid=4767&amp;action=news_details&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;. Most of my plugins had to be upgraded. 

As you can see from the list, upgrading from 6.x to 7.x is not trivial.

Lots of little details to work through.</description>
		<content:encoded><![CDATA[<p>Jose: yes, you need to ensure that your plugins are compatible with 7.x. Some are, some aren&#8217;t.</p>
<p>You can see the full list of plugins and the supported versions by Pro Tools platform <a href="http://www.digidesign.com/index.cfm?langid=1&#038;navid=71&#038;itemid=4767&#038;action=news_details" rel="nofollow">here</a>. Most of my plugins had to be upgraded. </p>
<p>As you can see from the list, upgrading from 6.x to 7.x is not trivial.</p>
<p>Lots of little details to work through.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose</title>
		<link>http://www.richardcleaver.com/2006/10/22/studio-upgrades/comment-page-1/#comment-11278</link>
		<dc:creator>Jose</dc:creator>
		<pubDate>Thu, 26 Oct 2006 23:43:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardcleaver.com/?p=1174#comment-11278</guid>
		<description>I don&#039;t understand. If you upgrade Protools, you need to upgrade plugins too to work specially  with the upgraded version of PT?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t understand. If you upgrade Protools, you need to upgrade plugins too to work specially  with the upgraded version of PT?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt S</title>
		<link>http://www.richardcleaver.com/2006/10/22/studio-upgrades/comment-page-1/#comment-11192</link>
		<dc:creator>Matt S</dc:creator>
		<pubDate>Sun, 22 Oct 2006 22:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardcleaver.com/?p=1174#comment-11192</guid>
		<description>Ouch!! Technology woes :(


Can we expect a review of the Korg soon?

And by the way...how is that mesa lonestar special treating you?</description>
		<content:encoded><![CDATA[<p>Ouch!! Technology woes <img src='http://www.richardcleaver.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>Can we expect a review of the Korg soon?</p>
<p>And by the way&#8230;how is that mesa lonestar special treating you?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

