<?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: MOVING BETWEEN FINAL CUT PRO AND AFTER EFFECTS: THE SCRIPTING OPTION</title>
	<atom:link href="http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/</link>
	<description>Sharing tips, scripts and hacks for your creative workflow.</description>
	<lastBuildDate>Thu, 11 Mar 2010 13:52: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: Dale</title>
		<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/comment-page-1/#comment-5768</link>
		<dc:creator>Dale</dc:creator>
		<pubDate>Sat, 11 Aug 2007 00:45:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/#comment-5768</guid>
		<description>Hey Michael,

Thanks for the heads up! I&#039;ll have to take a look at that problem, but it doesn&#039;t suprise me too much. Like you said, slashes are a big deal when it comes to paths, but I should be able to escape them if I make a special check for them.

Dale</description>
		<content:encoded><![CDATA[<p>Hey Michael,</p>
<p>Thanks for the heads up! I&#8217;ll have to take a look at that problem, but it doesn&#8217;t suprise me too much. Like you said, slashes are a big deal when it comes to paths, but I should be able to escape them if I make a special check for them.</p>
<p>Dale</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/comment-page-1/#comment-5765</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Fri, 10 Aug 2007 22:47:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/#comment-5765</guid>
		<description>Hey Dale,
Your work on this is awesome. I&#039;ve been needing something like this forever. I have run across a strange bug though. Actually, it&#039;s not really a bug, but I thought I would mention it in case anybody else experienced the same problem.

It seems that if there are slashes in the name, it errors on import saying &quot;unable to import footage, including placeholder&quot;. I know slashes in a name is a bad thing, but I got a bunch of footage from somebody and they had put a bunch of slashes in all the names. It was a pain to get through. But at least you can just rename in final cut and then select all the files and say rename/file to match clip.

Anyway, keep up the good work. I don&#039;t understand what you are doing, but I like it.</description>
		<content:encoded><![CDATA[<p>Hey Dale,<br />
Your work on this is awesome. I&#8217;ve been needing something like this forever. I have run across a strange bug though. Actually, it&#8217;s not really a bug, but I thought I would mention it in case anybody else experienced the same problem.</p>
<p>It seems that if there are slashes in the name, it errors on import saying &#8220;unable to import footage, including placeholder&#8221;. I know slashes in a name is a bad thing, but I got a bunch of footage from somebody and they had put a bunch of slashes in all the names. It was a pain to get through. But at least you can just rename in final cut and then select all the files and say rename/file to match clip.</p>
<p>Anyway, keep up the good work. I don&#8217;t understand what you are doing, but I like it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale</title>
		<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/comment-page-1/#comment-4654</link>
		<dc:creator>Dale</dc:creator>
		<pubDate>Wed, 11 Jul 2007 12:50:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/#comment-4654</guid>
		<description>Hey Jan,

That&#039;s a relatively easy task to extract that info from Final Cut XML although I haven&#039;t written any scripts or tools for that.

You might take a look at:

http://www.spherico.com/filmtools

There are a lot of freeware and reasonably priced tools there for dealing with FCP-XML. I&#039;m always writing tools and scripts also so I&#039;ll add your request to the list and hopefully come up with something you&#039;d find useful.

Thanks for the kind words...

Dale</description>
		<content:encoded><![CDATA[<p>Hey Jan,</p>
<p>That&#8217;s a relatively easy task to extract that info from Final Cut XML although I haven&#8217;t written any scripts or tools for that.</p>
<p>You might take a look at:</p>
<p><a href="http://www.spherico.com/filmtools" rel="nofollow">http://www.spherico.com/filmtools</a></p>
<p>There are a lot of freeware and reasonably priced tools there for dealing with FCP-XML. I&#8217;m always writing tools and scripts also so I&#8217;ll add your request to the list and hopefully come up with something you&#8217;d find useful.</p>
<p>Thanks for the kind words&#8230;</p>
<p>Dale</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan</title>
		<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/comment-page-1/#comment-4639</link>
		<dc:creator>Jan</dc:creator>
		<pubDate>Wed, 11 Jul 2007 04:47:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/#comment-4639</guid>
		<description>Hi Dale.   Great site.   I&#039;m an editor and really don&#039;t want to learn any coding.   I would, however, like to find someone who can parse fcp xml.   I&#039;ve logged an 86 reel documentary with many clip markers, as well as standard fields such as master comments, log notes, etc.

Since FCP searches do not include markers &amp; marker comments, I&#039;d like to get them from the xml, along with all of the normal &quot;edl&quot; type fields.

These could all be opened in a simple program like Filemaker pro, where I could do a word search that would check EVERY field, thusly locating all that I&#039;m looking for.   I can&#039;t believe I just said &quot;thusly&quot;.   

Suggestions?

Jan</description>
		<content:encoded><![CDATA[<p>Hi Dale.   Great site.   I&#8217;m an editor and really don&#8217;t want to learn any coding.   I would, however, like to find someone who can parse fcp xml.   I&#8217;ve logged an 86 reel documentary with many clip markers, as well as standard fields such as master comments, log notes, etc.</p>
<p>Since FCP searches do not include markers &amp; marker comments, I&#8217;d like to get them from the xml, along with all of the normal &#8220;edl&#8221; type fields.</p>
<p>These could all be opened in a simple program like Filemaker pro, where I could do a word search that would check EVERY field, thusly locating all that I&#8217;m looking for.   I can&#8217;t believe I just said &#8220;thusly&#8221;.   </p>
<p>Suggestions?</p>
<p>Jan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Creative Workflow Hacks &#187; Blog Archive &#187; Final Cut Pro to After Effects Scripting without the hassle</title>
		<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/comment-page-1/#comment-2537</link>
		<dc:creator>Creative Workflow Hacks &#187; Blog Archive &#187; Final Cut Pro to After Effects Scripting without the hassle</dc:creator>
		<pubDate>Mon, 16 Apr 2007 02:35:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/#comment-2537</guid>
		<description>[...] One of the most popular pieces of content here is Moving Between Final Cut Pro and After Effects: The Scripting Option. I think the idea of using scripting to move between Final Cut Pro and After Effects resonated with people working in a production environment. Unfortunately, the post was more of a tech demo of the kinds of things that were possible with After Effects scripting and less of a practical demonstration for non-technical users. I still urge non-technical folks to dip their toes into the scripting waters, it can be really rewarding, but the challenges presented in &#8220;rolling your own&#8221; in this situation may be a bit much. [...]</description>
		<content:encoded><![CDATA[<p>[...] One of the most popular pieces of content here is Moving Between Final Cut Pro and After Effects: The Scripting Option. I think the idea of using scripting to move between Final Cut Pro and After Effects resonated with people working in a production environment. Unfortunately, the post was more of a tech demo of the kinds of things that were possible with After Effects scripting and less of a practical demonstration for non-technical users. I still urge non-technical folks to dip their toes into the scripting waters, it can be really rewarding, but the challenges presented in &#8220;rolling your own&#8221; in this situation may be a bit much. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/comment-page-1/#comment-2371</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Mon, 02 Apr 2007 16:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/#comment-2371</guid>
		<description>Hey Dale -- I get the &quot;error 63&quot; error as well. Can&#039;t wait to see the new script -- there&#039;s a million salivating FCP+AE users out there who can&#039;t afford AD, and this solution would be perfect!</description>
		<content:encoded><![CDATA[<p>Hey Dale &#8212; I get the &#8220;error 63&#8243; error as well. Can&#8217;t wait to see the new script &#8212; there&#8217;s a million salivating FCP+AE users out there who can&#8217;t afford AD, and this solution would be perfect!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eugen</title>
		<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/comment-page-1/#comment-1670</link>
		<dc:creator>eugen</dc:creator>
		<pubDate>Wed, 07 Feb 2007 17:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/#comment-1670</guid>
		<description>sir! id like to say that you are rocking ! 
thnx so far ... in the meantime ill finish my project like a good old farmer .. plugging seeds by hand .. .</description>
		<content:encoded><![CDATA[<p>sir! id like to say that you are rocking !<br />
thnx so far &#8230; in the meantime ill finish my project like a good old farmer .. plugging seeds by hand .. .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale</title>
		<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/comment-page-1/#comment-1669</link>
		<dc:creator>Dale</dc:creator>
		<pubDate>Wed, 07 Feb 2007 16:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/#comment-1669</guid>
		<description>Update...

so eugen sent me the files he was having problems with and I think I see where the path problems might be arising for at least some of the folks posting comments. I&#039;ll need a bit to prepare a fix, but I&#039;ll be sure and post the updated script here and make it obvious there is an update.

Dale</description>
		<content:encoded><![CDATA[<p>Update&#8230;</p>
<p>so eugen sent me the files he was having problems with and I think I see where the path problems might be arising for at least some of the folks posting comments. I&#8217;ll need a bit to prepare a fix, but I&#8217;ll be sure and post the updated script here and make it obvious there is an update.</p>
<p>Dale</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale</title>
		<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/comment-page-1/#comment-1668</link>
		<dc:creator>Dale</dc:creator>
		<pubDate>Wed, 07 Feb 2007 16:12:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/#comment-1668</guid>
		<description>Hey Eugene,

no problem. just put your code between &lt;pre&gt;&lt;/pre&gt; tags and it should work. 

So, this is useful, the second path in the json you pasted is empty, &quot;path&quot;:&quot;&quot;
can you send me the original fcp-xml and the json file you created to dale(at)creative-workflow-hacks(dot)com? That might be the source of your problem.</description>
		<content:encoded><![CDATA[<p>Hey Eugene,</p>
<p>no problem. just put your code between &lt;pre&gt;&lt;/pre&gt; tags and it should work. </p>
<p>So, this is useful, the second path in the json you pasted is empty, &#8220;path&#8221;:&#8221;"<br />
can you send me the original fcp-xml and the json file you created to dale(at)creative-workflow-hacks(dot)com? That might be the source of your problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eugen</title>
		<link>http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/comment-page-1/#comment-1667</link>
		<dc:creator>eugen</dc:creator>
		<pubDate>Wed, 07 Feb 2007 15:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.creative-workflow-hacks.com/2006/03/09/moving-between-final-cut-pro-and-after-effects-the-scripting-option/#comment-1667</guid>
		<description>SORRY I MUST HAVE SMASHED YOUR LAYOUT  ! my apollogies !</description>
		<content:encoded><![CDATA[<p>SORRY I MUST HAVE SMASHED YOUR LAYOUT  ! my apollogies !</p>
]]></content:encoded>
	</item>
</channel>
</rss>
