<?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: LOADER &#8211; FROM DIGITAL HEAVEN</title>
	<atom:link href="http://lfhd.net/2008/10/15/loader-from-digital-heaven/feed/" rel="self" type="application/rss+xml" />
	<link>http://lfhd.net/2008/10/15/loader-from-digital-heaven/</link>
	<description>High definition editing from the trenches...</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:26: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: Dylan Reeve</title>
		<link>http://lfhd.net/2008/10/15/loader-from-digital-heaven/comment-page-1/#comment-1047</link>
		<dc:creator>Dylan Reeve</dc:creator>
		<pubDate>Thu, 16 Oct 2008 01:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://postfifthpictures.com/lfhd/2008/10/15/loader-from-digital-heaven/#comment-1047</guid>
		<description>That&#039;s great. I like FCP&#039;s quick import of media, but it does introduce the problem of organisation. After one long drawn out project earlier this year I was left with various elements in a range of different places, it was a pain to try and tidy it all up to backup. This is a much much better solution.&lt;br/&gt;&lt;br/&gt;I&#039;d like to see something can go the other way well, look at an FCP project and gather all the imported media elements into one place sensibly.</description>
		<content:encoded><![CDATA[<p>That&#8217;s great. I like FCP&#8217;s quick import of media, but it does introduce the problem of organisation. After one long drawn out project earlier this year I was left with various elements in a range of different places, it was a pain to try and tidy it all up to backup. This is a much much better solution.</p>
<p>I&#8217;d like to see something can go the other way well, look at an FCP project and gather all the imported media elements into one place sensibly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://lfhd.net/2008/10/15/loader-from-digital-heaven/comment-page-1/#comment-1046</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 16 Oct 2008 00:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://postfifthpictures.com/lfhd/2008/10/15/loader-from-digital-heaven/#comment-1046</guid>
		<description>The basic premise is easy to implement in xml .... but hoo boy they&#039;ve made this thing pretty darn slick.  Kudos for the DH team for not only having such a good idea but for turning that idea into something that looks so nice to work with!  They&#039;ve done a bang up job with this one, and the price point is excellent.&lt;br/&gt;&lt;br/&gt;For what its worth tho ... it doesn&#039;t automatically copy stuff to your Capture Scratch as it doesn&#039;t (and can&#039;t) know where that is.  You have to specify the &quot;media destination&quot; folder before you start using it.&lt;br/&gt;I really wish Apple would address that, either directly in their XML support (with a an import option flag to copy the import media to the Capture Scratch) or by putting the Capture Scratch info into a unencoded plist preference file so that developers can access it.</description>
		<content:encoded><![CDATA[<p>The basic premise is easy to implement in xml &#8230;. but hoo boy they&#8217;ve made this thing pretty darn slick.  Kudos for the DH team for not only having such a good idea but for turning that idea into something that looks so nice to work with!  They&#8217;ve done a bang up job with this one, and the price point is excellent.</p>
<p>For what its worth tho &#8230; it doesn&#8217;t automatically copy stuff to your Capture Scratch as it doesn&#8217;t (and can&#8217;t) know where that is.  You have to specify the &#8220;media destination&#8221; folder before you start using it.<br />I really wish Apple would address that, either directly in their XML support (with a an import option flag to copy the import media to the Capture Scratch) or by putting the Capture Scratch info into a unencoded plist preference file so that developers can access it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken S.</title>
		<link>http://lfhd.net/2008/10/15/loader-from-digital-heaven/comment-page-1/#comment-1045</link>
		<dc:creator>Ken S.</dc:creator>
		<pubDate>Wed, 15 Oct 2008 17:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://postfifthpictures.com/lfhd/2008/10/15/loader-from-digital-heaven/#comment-1045</guid>
		<description>Why didn&#039;t I think of that?</description>
		<content:encoded><![CDATA[<p>Why didn&#8217;t I think of that?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

