<?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: Final Cut Pro projects won&#8217;t open when files are inaccessible</title>
	<atom:link href="http://www.ericbrodeur.com/blog/2008/03/11/final-cut-pro-projects-wont-open-when-files-are-inaccessible/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ericbrodeur.com/blog/2008/03/11/final-cut-pro-projects-wont-open-when-files-are-inaccessible/</link>
	<description>Perspectives on storytelling and digital cinema technology</description>
	<lastBuildDate>Wed, 23 Nov 2011 05:55:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Webspace of Eric Brodeur &#187; Resolving file type, file creator, and file path problems with Final Cut Pro</title>
		<link>http://www.ericbrodeur.com/blog/2008/03/11/final-cut-pro-projects-wont-open-when-files-are-inaccessible/comment-page-1/#comment-3344</link>
		<dc:creator>Webspace of Eric Brodeur &#187; Resolving file type, file creator, and file path problems with Final Cut Pro</dc:creator>
		<pubDate>Wed, 10 Jun 2009 18:09:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.ericbrodeur.com/wp/2008/03/11/final-cut-pro-projects-wont-open-when-files-are-inaccessible/#comment-3344</guid>
		<description>&lt;p&gt;[...] covered this issue before which is due to Final Cut Pro using absolute paths within the project [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] covered this issue before which is due to Final Cut Pro using absolute paths within the project [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: presscard</title>
		<link>http://www.ericbrodeur.com/blog/2008/03/11/final-cut-pro-projects-wont-open-when-files-are-inaccessible/comment-page-1/#comment-1421</link>
		<dc:creator>presscard</dc:creator>
		<pubDate>Wed, 30 Jul 2008 15:25:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.ericbrodeur.com/wp/2008/03/11/final-cut-pro-projects-wont-open-when-files-are-inaccessible/#comment-1421</guid>
		<description>&lt;p&gt;typically the error “this project is unreadable or may be too new for this version of Final Cut.” occurs when a project is created on a machine with a newer version of Final Cut Pro than the one it is trying to be opened on. it is reccommended that the user go to software update to see if there is the latest version of Final Cut Pro available or other pro apps updates.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>typically the error “this project is unreadable or may be too new for this version of Final Cut.” occurs when a project is created on a machine with a newer version of Final Cut Pro than the one it is trying to be opened on. it is reccommended that the user go to software update to see if there is the latest version of Final Cut Pro available or other pro apps updates.</p>]]></content:encoded>
	</item>
</channel>
</rss>

