<?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: Key Grip dust left in Final Cut Pro?</title>
	<atom:link href="http://www.scottsimmons.tv/blog/2006/12/04/key-grip-dust-left-in-final-cut-pro/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.scottsimmons.tv/blog/2006/12/04/key-grip-dust-left-in-final-cut-pro/</link>
	<description>A few words about non-linear editing, filmmaking and more ...</description>
	<lastBuildDate>Wed, 28 Jul 2010 17:40:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: editblog</title>
		<link>http://www.scottsimmons.tv/blog/2006/12/04/key-grip-dust-left-in-final-cut-pro/comment-page-1/#comment-2289</link>
		<dc:creator>editblog</dc:creator>
		<pubDate>Tue, 05 Dec 2006 18:41:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottsimmons.tv/blog/2006/12/04/key-grip-dust-left-in-final-cut-pro/#comment-2289</guid>
		<description>That&#039;s great to know. Coding an application as complicated as Final Cut Pro can&#039;t be an easy task. I respect these people greatly!</description>
		<content:encoded><![CDATA[<p>That&#8217;s great to know. Coding an application as complicated as Final Cut Pro can&#8217;t be an easy task. I respect these people greatly!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lewis</title>
		<link>http://www.scottsimmons.tv/blog/2006/12/04/key-grip-dust-left-in-final-cut-pro/comment-page-1/#comment-2256</link>
		<dc:creator>Lewis</dc:creator>
		<pubDate>Tue, 05 Dec 2006 10:04:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottsimmons.tv/blog/2006/12/04/key-grip-dust-left-in-final-cut-pro/#comment-2256</guid>
		<description>Yup - in older versions the Type code also started with KG, like KGPF for Key Grip Project File and so on.  And if you take a sample of the FCP process with Activity Monitor, or attach a debugger to it or whatever, you&#039;ll see that all the functions names begin with KG, KGMainEvent and suchlike.</description>
		<content:encoded><![CDATA[<p>Yup &#8211; in older versions the Type code also started with KG, like KGPF for Key Grip Project File and so on.  And if you take a sample of the FCP process with Activity Monitor, or attach a debugger to it or whatever, you&#8217;ll see that all the functions names begin with KG, KGMainEvent and suchlike.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Hodgetts</title>
		<link>http://www.scottsimmons.tv/blog/2006/12/04/key-grip-dust-left-in-final-cut-pro/comment-page-1/#comment-2239</link>
		<dc:creator>Philip Hodgetts</dc:creator>
		<pubDate>Tue, 05 Dec 2006 05:51:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottsimmons.tv/blog/2006/12/04/key-grip-dust-left-in-final-cut-pro/#comment-2239</guid>
		<description>You are correct. An application&#039;s creator code is set very early in the process and it&#039;s quite difficult to change it later. So KeyGrip will ever have it&#039;s tentacles on Final Cut Pro: you can change the name but the creator code is a constant.

Cheers

Philip</description>
		<content:encoded><![CDATA[<p>You are correct. An application&#8217;s creator code is set very early in the process and it&#8217;s quite difficult to change it later. So KeyGrip will ever have it&#8217;s tentacles on Final Cut Pro: you can change the name but the creator code is a constant.</p>
<p>Cheers</p>
<p>Philip</p>
]]></content:encoded>
	</item>
</channel>
</rss>
