<?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: Inaccurate Scopes in Final Cut Pro Workaround?</title>
	<atom:link href="http://www.creative-workflow-hacks.com/2006/09/15/inaccurate-scopes-in-final-cut-pro-workaround/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.creative-workflow-hacks.com/2006/09/15/inaccurate-scopes-in-final-cut-pro-workaround/</link>
	<description>Sharing tips, scripts and hacks for your creative workflow.</description>
	<lastBuildDate>Fri, 19 Mar 2010 15:31:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Creative Workflow Hacks &#187; Blog Archive &#187; New FCP-XML Version Offers Exciting Project Management Possibilities</title>
		<link>http://www.creative-workflow-hacks.com/2006/09/15/inaccurate-scopes-in-final-cut-pro-workaround/comment-page-1/#comment-515</link>
		<dc:creator>Creative Workflow Hacks &#187; Blog Archive &#187; New FCP-XML Version Offers Exciting Project Management Possibilities</dc:creator>
		<pubDate>Wed, 27 Sep 2006 15:26:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/09/15/inaccurate-scopes-in-final-cut-pro-workaround/#comment-515</guid>
		<description>[...] Apple released Final Cut Pro 5.1.2 which addresses a lot of the problems that I&#8217;ve been running into lately. I want to take a bit of time to dig into the extensive bug fixes, and folks are already doing just that, but one change that I was not expecting really caught my eye. A  new version of the Final Cut XML interchange format introduced some new elements. [...]</description>
		<content:encoded><![CDATA[<p>[...] Apple released Final Cut Pro 5.1.2 which addresses a lot of the problems that I&#8217;ve been running into lately. I want to take a bit of time to dig into the extensive bug fixes, and folks are already doing just that, but one change that I was not expecting really caught my eye. A  new version of the Final Cut XML interchange format introduced some new elements. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Curtis</title>
		<link>http://www.creative-workflow-hacks.com/2006/09/15/inaccurate-scopes-in-final-cut-pro-workaround/comment-page-1/#comment-513</link>
		<dc:creator>Mike Curtis</dc:creator>
		<pubDate>Tue, 26 Sep 2006 14:44:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/09/15/inaccurate-scopes-in-final-cut-pro-workaround/#comment-513</guid>
		<description>I just blogged a link to this, and threw in some other issues I&#039;ve been hearing about in terms of clipping during export from FCP, clipping as a default behavior in AE, etc.

I don&#039;t know that I have all my facts straight on this issue, so anybody who wants to chime in (here or in comments on my site or email me directly) please do so, esp. if I have something wrong.</description>
		<content:encoded><![CDATA[<p>I just blogged a link to this, and threw in some other issues I&#8217;ve been hearing about in terms of clipping during export from FCP, clipping as a default behavior in AE, etc.</p>
<p>I don&#8217;t know that I have all my facts straight on this issue, so anybody who wants to chime in (here or in comments on my site or email me directly) please do so, esp. if I have something wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale</title>
		<link>http://www.creative-workflow-hacks.com/2006/09/15/inaccurate-scopes-in-final-cut-pro-workaround/comment-page-1/#comment-496</link>
		<dc:creator>Dale</dc:creator>
		<pubDate>Sun, 17 Sep 2006 00:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/09/15/inaccurate-scopes-in-final-cut-pro-workaround/#comment-496</guid>
		<description>quoting

The only way I fully trust right now is Kona -&gt;hardware scope -&gt; deck -&gt; monitor, all via SDI. The only problem is the price, especially for HD.


That&#039;s been exactly my experience to this point. The only option I see is to stay current with software/firmware/drive updates until some of this shakes out. If anybody has additional insight I&#039;d love to hear it.

Dale</description>
		<content:encoded><![CDATA[<p>quoting</p>
<p>The only way I fully trust right now is Kona ->hardware scope -> deck -> monitor, all via SDI. The only problem is the price, especially for HD.</p>
<p>That&#8217;s been exactly my experience to this point. The only option I see is to stay current with software/firmware/drive updates until some of this shakes out. If anybody has additional insight I&#8217;d love to hear it.</p>
<p>Dale</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: austin</title>
		<link>http://www.creative-workflow-hacks.com/2006/09/15/inaccurate-scopes-in-final-cut-pro-workaround/comment-page-1/#comment-495</link>
		<dc:creator>austin</dc:creator>
		<pubDate>Sat, 16 Sep 2006 19:35:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/09/15/inaccurate-scopes-in-final-cut-pro-workaround/#comment-495</guid>
		<description>we&#039;ve been having some of the same problems.  Throw Scopo Gigio into the mix of variable results.

A few days ago, I did a network render of a comp and had color shifts from frame to frame in my targa sequence!  yikes is right.

The only way I fully trust right now is Kona -&gt;hardware scope -&gt; deck -&gt; monitor, all via SDI.  The only problem is the price, especially for HD.

In theory,   we&#039;re already doing Shane&#039;s workaround in After Effects by rendering to Quicktime, no?  Doesn&#039;t really help if the problem doesn&#039;t show up until the render though...</description>
		<content:encoded><![CDATA[<p>we&#8217;ve been having some of the same problems.  Throw Scopo Gigio into the mix of variable results.</p>
<p>A few days ago, I did a network render of a comp and had color shifts from frame to frame in my targa sequence!  yikes is right.</p>
<p>The only way I fully trust right now is Kona -&gt;hardware scope -&gt; deck -&gt; monitor, all via SDI.  The only problem is the price, especially for HD.</p>
<p>In theory,   we&#8217;re already doing Shane&#8217;s workaround in After Effects by rendering to Quicktime, no?  Doesn&#8217;t really help if the problem doesn&#8217;t show up until the render though&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
