<?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: P2 Import with 5.1.2 is busted</title>
	<atom:link href="http://lfhd.net/2007/01/18/p2-import-with-5-1-2-is-busted/feed/" rel="self" type="application/rss+xml" />
	<link>http://lfhd.net/2007/01/18/p2-import-with-5-1-2-is-busted/</link>
	<description>Musings of an NLE ronin...</description>
	<lastBuildDate>Mon, 14 May 2012 16:07:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: free ps3</title>
		<link>http://lfhd.net/2007/01/18/p2-import-with-5-1-2-is-busted/comment-page-1/#comment-429</link>
		<dc:creator>free ps3</dc:creator>
		<pubDate>Sat, 15 Sep 2007 13:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://postfifthpictures.com/lfhd/2007/01/18/p2-import-with-5-1-2-is-busted/#comment-429</guid>
		<description>Thanks for the nice post!</description>
		<content:encoded><![CDATA[<p>Thanks for the nice post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: benlau</title>
		<link>http://lfhd.net/2007/01/18/p2-import-with-5-1-2-is-busted/comment-page-1/#comment-119</link>
		<dc:creator>benlau</dc:creator>
		<pubDate>Tue, 06 Feb 2007 09:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://postfifthpictures.com/lfhd/2007/01/18/p2-import-with-5-1-2-is-busted/#comment-119</guid>
		<description>knock on wood too, we&#039;ve yet to experience any abnormalities with our P2 workflow using 5.1.2, but I&#039;ve yet to hear of anybody who is following our workflow model.&lt;br /&gt;&lt;br /&gt;full P2 cards are delivered to a G4 PB connected to a 250GB external drive. from there, a disk image is made using disk utility, instead of a direct copy. the copy time is longer (about 15 minutes for a full 4GB card - which is all we have).&lt;br /&gt;&lt;br /&gt;at the end of the day, the drives are copied to both the local drive of our PowerMac, and our RAID 5 NAS. &lt;br /&gt;&lt;br /&gt;when i mount the disk image of a card from the local drive, FCP 5.1.2 immediately recognizes the P2 volume, and i can ingest clips without any problems.</description>
		<content:encoded><![CDATA[<p>knock on wood too, we&#8217;ve yet to experience any abnormalities with our P2 workflow using 5.1.2, but I&#8217;ve yet to hear of anybody who is following our workflow model.</p>
<p>full P2 cards are delivered to a G4 PB connected to a 250GB external drive. from there, a disk image is made using disk utility, instead of a direct copy. the copy time is longer (about 15 minutes for a full 4GB card &#8211; which is all we have).</p>
<p>at the end of the day, the drives are copied to both the local drive of our PowerMac, and our RAID 5 NAS. </p>
<p>when i mount the disk image of a card from the local drive, FCP 5.1.2 immediately recognizes the P2 volume, and i can ingest clips without any problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ti</title>
		<link>http://lfhd.net/2007/01/18/p2-import-with-5-1-2-is-busted/comment-page-1/#comment-116</link>
		<dc:creator>ti</dc:creator>
		<pubDate>Sat, 27 Jan 2007 22:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://postfifthpictures.com/lfhd/2007/01/18/p2-import-with-5-1-2-is-busted/#comment-116</guid>
		<description>Arrrggghhh,  what&#039;s going on with all the p2 craziness.  We&#039;ve had zero issues, but reading all the problems in threads at dvxuser, the cow, etc, makes me think that problems must be right around the corner for us!  fingers crossed.</description>
		<content:encoded><![CDATA[<p>Arrrggghhh,  what&#8217;s going on with all the p2 craziness.  We&#8217;ve had zero issues, but reading all the problems in threads at dvxuser, the cow, etc, makes me think that problems must be right around the corner for us!  fingers crossed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

