<?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: Resolving A Problem with Apple&#8217;s ProAps Update</title>
	<atom:link href="http://www.larryjordan.biz/app_bin/wordpress/archives/1071/feed" rel="self" type="application/rss+xml" />
	<link>http://www.larryjordan.biz/app_bin/wordpress/archives/1071</link>
	<description></description>
	<lastBuildDate>Fri, 20 Aug 2010 07:49:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stephen Gagne</title>
		<link>http://www.larryjordan.biz/app_bin/wordpress/archives/1071/comment-page-1#comment-5110</link>
		<dc:creator>Stephen Gagne</dc:creator>
		<pubDate>Fri, 19 Mar 2010 18:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.larryjordan.biz/app_bin/wordpress/?p=1071#comment-5110</guid>
		<description>Thanks for the info on SoundTrack Pro vs the ProKit update.

It got me thinking: would you consider some way of creating some sort of formal or even informal pro-editors experiences-tracking system for Apple editing software related updates?

Of course there are the Apple forums and such, but the signal-to-noise ratio tends to be pretty challenging in that context.

I’m well familiar with the “don’t update except between projects rule.” And the “wait Until a few weeks after release” rule to make sure a given update isn’t a lemon.

That aside, it’s still extremely useful to get a sense of which updates are fraught with peril, which have a relatively clean success to damage ratio, and which updates are worthwhile but only after Apple gets around to updating a related component.  (The many instances where a QuickTime update damaged some component in Final Cut Pro until the Final Cut team released an Pro-Apps update come to mind.)

 incidentally, I first posed a similar question a few minutes ago to Mike Curtis at the bottom of a recent blog entry of his, but after sending it it occurred to me that you seem better set up for this sort of thing, given your readership and your regular interaction with your readers.

Thanks, Stephen Gagné
Westwood Creek Productions

- - -

Stephen:

Thanks for the thoughts.  

We are working on something like this, which I hope to have ready by NAB.  Though not quite what you are asking for, I&#039;m hoping it comes close.

I&#039;ll let everyone know, via the newsletter, when it&#039;s ready.

Thanks,

larry
</description>
		<content:encoded><![CDATA[<p>Thanks for the info on SoundTrack Pro vs the ProKit update.</p>
<p>It got me thinking: would you consider some way of creating some sort of formal or even informal pro-editors experiences-tracking system for Apple editing software related updates?</p>
<p>Of course there are the Apple forums and such, but the signal-to-noise ratio tends to be pretty challenging in that context.</p>
<p>I’m well familiar with the “don’t update except between projects rule.” And the “wait Until a few weeks after release” rule to make sure a given update isn’t a lemon.</p>
<p>That aside, it’s still extremely useful to get a sense of which updates are fraught with peril, which have a relatively clean success to damage ratio, and which updates are worthwhile but only after Apple gets around to updating a related component.  (The many instances where a QuickTime update damaged some component in Final Cut Pro until the Final Cut team released an Pro-Apps update come to mind.)</p>
<p> incidentally, I first posed a similar question a few minutes ago to Mike Curtis at the bottom of a recent blog entry of his, but after sending it it occurred to me that you seem better set up for this sort of thing, given your readership and your regular interaction with your readers.</p>
<p>Thanks, Stephen Gagné<br />
Westwood Creek Productions</p>
<p>- &#8211; -</p>
<p>Stephen:</p>
<p>Thanks for the thoughts.  </p>
<p>We are working on something like this, which I hope to have ready by NAB.  Though not quite what you are asking for, I&#8217;m hoping it comes close.</p>
<p>I&#8217;ll let everyone know, via the newsletter, when it&#8217;s ready.</p>
<p>Thanks,</p>
<p>larry</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://www.larryjordan.biz/app_bin/wordpress/archives/1071/comment-page-1#comment-5109</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Mon, 15 Mar 2010 12:19:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.larryjordan.biz/app_bin/wordpress/?p=1071#comment-5109</guid>
		<description>Thanks for the info Larry! Glad you were able to track it down. 

- Thomas</description>
		<content:encoded><![CDATA[<p>Thanks for the info Larry! Glad you were able to track it down. </p>
<p>- Thomas</p>
]]></content:encoded>
	</item>
</channel>
</rss>
