<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Jamie De Pould &#187; final cut</title>
	<atom:link href="http://blog.jamiedepould.com/category/final-cut/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jamiedepould.com</link>
	<description>Syracuse multimedia producer</description>
	<lastBuildDate>Fri, 02 Jul 2010 02:13:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>On video editing codecs</title>
		<link>http://blog.jamiedepould.com/2010/05/on-video-editing-codecs/</link>
		<comments>http://blog.jamiedepould.com/2010/05/on-video-editing-codecs/#comments</comments>
		<pubDate>Sat, 29 May 2010 13:52:27 +0000</pubDate>
		<dc:creator>Jamie De Pould</dc:creator>
				<category><![CDATA[final cut]]></category>
		<category><![CDATA[multimedia]]></category>
		<category><![CDATA[codecs]]></category>
		<category><![CDATA[compression]]></category>
		<category><![CDATA[prores]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">http://blog.jamiedepould.com/?p=163</guid>
		<description><![CDATA[Video compression is something of a black art. I&#8217;ve become something of a compression nerd over the past few months, partly because I was helping to plan the 2010 NPPA Multimedia Immersion, and partly because I&#8217;m a giant geek. I&#8217;m going to concentrate on editing codecs today. I don&#8217;t want to get into final output [...]]]></description>
			<content:encoded><![CDATA[<p>Video compression is something of a black art. I&#8217;ve become something of a compression nerd over the past few months, partly because I was helping to plan the <a href="http://multimediaimmersion.tumblr.com/">2010 NPPA Multimedia Immersion,</a> and partly because I&#8217;m a giant geek. I&#8217;m going to concentrate on editing codecs today. I don&#8217;t want to get into final output and compression.</p>
<p><a title="ImmersionThursday-08 by jdepould, on Flickr" href="http://www.flickr.com/photos/jdepould/4624239077/"><img src="http://farm4.static.flickr.com/3417/4624239077_52642296c8.jpg" alt="ImmersionThursday-08" width="500" height="328" /></a></p>
<p><span id="more-163"></span><br />
For the workshop we settled on Apple Intermediate as an editing codec. We were bringing in footage from a wide variety of cameras, mostly Canon and Nikon SLRs, but a handful of dedicated video cameras too. We wanted everyone to be on the same page.</p>
<p>For the Canon and AVCHD folks it was easy, we just set up the plugins for Apple Intermediate, then did a standard Log and Transfer. For the Nikon shooters, it was a little bit more complicated. There isn&#8217;t a Nikon plugin, so they had to use Compressor (or <a href="http://www.squared5.com/">MPEG Streamclip</a>) to transcode from Motion JPEG to Apple Intermediate.</p>
<h3>So &#8230; why not ProRes 422?</h3>
<p>The most obvious reason is storage. We had people using a wide variety of hard drives. Some were USB, some FireWire. Some were big, some were small. Apple Intermediate gave us good quality at reasonable file sizes. The main drive of the workshop was creating content for the web, which means it&#8217;s going to get compressed down quite a bit anyway. We weren&#8217;t going to be doing heavy color work, and we didn&#8217;t need alpha channels. So there you have it, Apple Intermediate. We could&#8217;ve very easily landed on ProRes LT (which has a similar data rate), but there were a handful of people using Final Cut Express, which uses Intermediate exclusively.</p>
<p>Like I said earlier, a lot of it comes down to storage and use. For HD video, ProRes 422 averages around 66GB per hour. The same footage encoded using Apple Intermediate comes in around 49GB per hour, and the quality is still excellent. When Apple released Final Cut 7, they also introduced several new ProRes flavors, including ProRes LT, which comes in at 46GB per hour. Intermediate and LT are also much nicer to laptops.</p>
<p>I haven&#8217;t done much experimenting with it, but I may start using LT for future projects. Apple designed the ProRes family with multicore Intel systems in mind, so you can go longer between renders, and footage renders faster. The advantage of LT over Apple Intermediate is the extra color information (4:2:2 vs. 4:2:0). The big caveat here is that Final Cut 6 can&#8217;t handle the new codecs, so you&#8217;re better off using Intermediate (or normal 422) if you&#8217;ve got to go back and forth.</p>
<p>For web use, ProRes 422 is generally overkill, especially if you&#8217;re not doing color work. If you need an alpha channel, however, then 422 it is.</p>
<p>If you&#8217;re mastering Blu-ray, then by all means, use 422, otherwise, save some drive space for your next project.</p>
<p>For more info about ProRes and other codecs, check out Larry Jordan&#8217;s <a href="http://www.larryjordan.biz/articles/lj_prores.html" target="_blank">site</a> and Apple&#8217;s <a href="http://www.apple.com/finalcutstudio/finalcutpro/apple-prores.html" target="_blank">ProRes page.</a></p>
<p><a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save"><img src="http://blog.jamiedepould.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a> </p>]]></content:encoded>
			<wfw:commentRss>http://blog.jamiedepould.com/2010/05/on-video-editing-codecs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Recutting my first multimedia</title>
		<link>http://blog.jamiedepould.com/2010/05/recutting-my-first-multimedia/</link>
		<comments>http://blog.jamiedepould.com/2010/05/recutting-my-first-multimedia/#comments</comments>
		<pubDate>Fri, 21 May 2010 18:17:14 +0000</pubDate>
		<dc:creator>Jamie De Pould</dc:creator>
				<category><![CDATA[final cut]]></category>
		<category><![CDATA[multimedia]]></category>
		<category><![CDATA[automotive]]></category>
		<category><![CDATA[cars]]></category>
		<category><![CDATA[final cut pro]]></category>
		<category><![CDATA[photography]]></category>
		<category><![CDATA[racing]]></category>

		<guid isPermaLink="false">http://blog.jamiedepould.com/?p=156</guid>
		<description><![CDATA[I re-edited my very first multimedia piece, an autobiography about racing.]]></description>
			<content:encoded><![CDATA[<p>I recently went back and re-editing the very first Final Cut piece I ever did. It was funny to go back and see how far I&#8217;ve come. It wasn&#8217;t a bad first attempt, but the edits weren&#8217;t very precise, I used way too many transitions, and it was a little too long. I did my copied the entire sequence over and removed all the image. I did several passes refining the audio, tweaking timing, levels and transitions. After that I added images, this time WITHOUT fade-to-black transitions between every frame (yikes).</p>
<p><object width="576" height="324"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=11361641&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=ffffff&amp;fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=11361641&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=ffffff&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="576" height="324"></embed></object>
<p><a href="http://vimeo.com/11361641">Then the hail started</a> from <a href="http://vimeo.com/jdepould">Jamie De Pould</a> on <a href="http://vimeo.com">Vimeo</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.jamiedepould.com/2010/05/recutting-my-first-multimedia/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Converting a QuickTime .mov to .flv</title>
		<link>http://blog.jamiedepould.com/2010/05/converting-quicktime-movs-to-flv/</link>
		<comments>http://blog.jamiedepould.com/2010/05/converting-quicktime-movs-to-flv/#comments</comments>
		<pubDate>Thu, 13 May 2010 02:50:17 +0000</pubDate>
		<dc:creator>Jamie De Pould</dc:creator>
				<category><![CDATA[final cut]]></category>
		<category><![CDATA[multimedia]]></category>
		<category><![CDATA[compression]]></category>
		<category><![CDATA[conversion]]></category>
		<category><![CDATA[flash]]></category>
		<category><![CDATA[flv]]></category>
		<category><![CDATA[mov]]></category>
		<category><![CDATA[quicktime]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">http://blog.jamiedepould.com/?p=135</guid>
		<description><![CDATA[ wrote this up after some of my students had problems uploading H.264 encoded video from Final Cut Express to VuVox. Their videos either didn't play back smoothly, or resized incorrectly--it seems VuVox only supports square pixels. So I tried converting the videos to .flv using Adobe Media Encoder, and it fixed all the problems we were having.]]></description>
			<content:encoded><![CDATA[<p>I wrote this up after some of my students had problems uploading H.264 encoded video from Final Cut Express to <a href="http://www.vuvox.com/">VuVox</a>. Their videos either didn&#8217;t play back smoothly, or resized incorrectly&#8211;it seems VuVox only supports square pixels. So I tried converting the videos to .flv using Adobe Media Encoder, and it fixed all the problems we were having.</p>
<p>First, export the videos using the File>Export>QuickTime Movie command. Create a folder on the desktop called &#8220;flv_convert&#8221; (or something like that), and export there. Make sure you check the box that says “Make Movie Self-Contained.”</p>
<p>Once that’s done, you can quit Final Cut.</p>
<p>Launch Adobe Media Encoder.<br />
<a href="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.33.00-PM.png"><img src="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.33.00-PM-188x122.png" alt="" title="Screen shot 2010-05-11 at 10.33.00 PM" width="188" height="122" class="alignleft size-medium wp-image-136" /></a><br />
<span id="more-135"></span><br />
￼Click the Add button on the right side of the Adobe Media Encoder window.<br />
<a href="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.38.39-PM.png"><img src="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.38.39-PM-494x390.png" alt="" title="Screen shot 2010-05-11 at 10.38.39 PM" width="494" height="390" class="alignleft size-large wp-image-138" /></a></p>
<p>￼Navigate to your flv_convert folder, select the .mov files, and click Open. The clips should show up in the queue.<br />
<a href="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.43.02-PM.png"><img src="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.43.02-PM-494x207.png" alt="" title="Screen shot 2010-05-11 at 10.43.02 PM" width="494" height="207" class="alignleft size-large wp-image-139" /></a></p>
<p>Select the first clip and click Settings, this should bring up the export settings menu.<br />
<a href="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.45.41-PM.png"><img src="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.45.41-PM-494x355.png" alt="" title="Screen shot 2010-05-11 at 10.45.41 PM" width="494" height="355" class="alignleft size-large wp-image-142" /></a></p>
<p>Use the following settings:</p>
<p><strong>Format</strong><br />
Format: FLV</p>
<p><strong>Video</strong><br />
Resize to 512&#215;288**<br />
Frame rate: <em>select the frame rate to match your footage</em><br />
Bitrate encoding: VBR<br />
Encoding passes: Two<br />
Bitrate: 900 kbps***<br />
Set keyframe distance: 15 frames <em>(More frequent keyframes give you higher quality, but with increased file size)</em><br />
Quality: Best</p>
<p><strong>Audio</strong><br />
Defaults should be fine</p>
<p><em>**NOTE: This is a good size for VuVox, but may not be the best size for other uses. More info about resizing video for flash <a href="http://labs.influxis.com/?p=6">here</a>.<br />
***NOTE: Larger sizes require higher bit rates, 900 kbps is plenty for this size, but is way too low for HD.</em></p>
<p>Click the floppy disk icon next to the preset name, this will allow you to save the preset.<br />
<a href="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.50.56-PM.png"><img src="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.50.56-PM.png" alt="" title="Screen shot 2010-05-11 at 10.50.56 PM" width="257" height="29" class="alignleft size-full wp-image-143" /></a></p>
<p>Name the preset, and click OK.<br />
<a href="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.52.55-PM.png"><img src="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.52.55-PM.png" alt="" title="Screen shot 2010-05-11 at 10.52.55 PM" width="371" height="174" class="alignleft size-full wp-image-144" /></a></p>
<p>￼Click OK again, and it should bring you back to the main window. Click the drop downs in the preset column, and change your other clips to the VuVox setting.<br />
<a href="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.54.24-PM.png"><img src="http://blog.jamiedepould.com/wp-content/uploads/2010/05/Screen-shot-2010-05-11-at-10.54.24-PM-494x68.png" alt="" title="Screen shot 2010-05-11 at 10.54.24 PM" width="494" height="68" class="alignleft size-large wp-image-145" /></a></p>
<p>￼Once you set all of your clips, click “Start Queue” on the right side of the screen. You should get a yellow progress bar along the bottom, and when it’s finished you’ll have shiny new .flv files in the flv_convert folder ready to upload.</p>
<p>You can also set a custom destination if you want the converted files to go somewhere else. You can also upload directly to an FTP server.</p>
<p><a rel="license" href="http://creativecommons.org/licenses/by-nc-nd/3.0/us/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-nc-nd/3.0/us/88x31.png" /></a><br /><span xmlns:dc="http://purl.org/dc/elements/1.1/" href="http://purl.org/dc/dcmitype/Text" property="dc:title" rel="dc:type">Converting a QuickTime .mov to .flv</span> by <a xmlns:cc="http://creativecommons.org/ns#" href="http://blog.jamiedepould.com/2010/05/converting-quicktime-movs-to-flv/" property="cc:attributionName" rel="cc:attributionURL">Jamie De Pould</a> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc-nd/3.0/us/">Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.jamiedepould.com/2010/05/converting-quicktime-movs-to-flv/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Final Cut: XML exports</title>
		<link>http://blog.jamiedepould.com/2010/03/final-cut-xml-exports/</link>
		<comments>http://blog.jamiedepould.com/2010/03/final-cut-xml-exports/#comments</comments>
		<pubDate>Sat, 06 Mar 2010 02:08:42 +0000</pubDate>
		<dc:creator>Jamie De Pould</dc:creator>
				<category><![CDATA[final cut]]></category>
		<category><![CDATA[multimedia]]></category>
		<category><![CDATA[editing]]></category>
		<category><![CDATA[final cut express]]></category>
		<category><![CDATA[final cut pro]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[video]]></category>
		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://blog.jamiedepould.com/?p=80</guid>
		<description><![CDATA[How to export a Final Cut sequence to XML.]]></description>
			<content:encoded><![CDATA[<p>There are any number of reasons to export a Final Cut sequence to XML. The biggest one I&#8217;ve run into recently is  students accidentally opening their project in Final Cut Pro when they should be using Final Cut Express.</p>
<p>You can also use an XML export to transfer a Final Cut Project to Adobe Premiere Pro, and from there to a program like After Effects or Photoshop. This cuts down on exporting intermediate files between FCP and other programs.</p>
<p>Whatever the reason, it&#8217;s a fairly simple process.</p>
<p>Open the project in Final Cut Pro, and click File&gt;Export&gt;XML</p>
<p><a href="http://blog.jamiedepould.com/wp-content/uploads/2010/03/file-export.jpg"><img class="size-medium wp-image-81 alignleft" title="file-export" src="http://blog.jamiedepould.com/wp-content/uploads/2010/03/file-export-287x300.jpg" alt="" width="287" height="300" /></a></p>
<p>From there, you&#8217;ll need to select an XML interchange format. I found that XML 4 works best when you&#8217;re transferring back to Final Cut Express. I haven&#8217;t tried it with Premiere, so experiment and see what works best.</p>
<p>I generally uncheck &#8220;include master clips outside selection,&#8221; because this gives you all the clips used in the timeline, but doesn&#8217;t include any clips in the browser but not in the timeline. I prefer to import all of my clips at once, rather than try to figure out which ones I&#8217;m missing.</p>
<p><a href="http://blog.jamiedepould.com/wp-content/uploads/2010/03/XML-format.jpg"><img class="size-medium wp-image-82 alignleft" title="XML-format" src="http://blog.jamiedepould.com/wp-content/uploads/2010/03/XML-format-300x155.jpg" alt="" width="300" height="155" /></a></p>
<p>I save the XML file in the same location as my .fcp files, and give it a clear name like JAMIEDEPOULD_EXAMPLEPROJECT-XML.</p>
<p><a href="http://blog.jamiedepould.com/wp-content/uploads/2010/03/saving.jpg"><img class="alignleft size-medium wp-image-83" title="saving" src="http://blog.jamiedepould.com/wp-content/uploads/2010/03/saving-300x248.jpg" alt="" width="300" height="248" /></a></p>
<p>Once that&#8217;s done, you can quit Final Cut Pro, and launch Express (or Premiere). From there, simply click File&gt;Import XML from iMovie. Navigate to the XML file you just created, select it, and Final Cut Express will prompt you to save the new project. I generally like to call it YOURNAME_PROJECTNAME-FCE.</p>
<p><a href="http://blog.jamiedepould.com/wp-content/uploads/2010/03/XML-import.jpg"><img class="alignleft size-medium wp-image-84" title="XML-import" src="http://blog.jamiedepould.com/wp-content/uploads/2010/03/XML-import-300x182.jpg" alt="" width="300" height="182" /></a></p>
<p>When it&#8217;s finished, you have your timeline, complete with edits, right there in front of you. Import your assets, and you&#8217;re ready to get back to editing. If you&#8217;re working on a machine with both Final Cuts Pro and Express, it&#8217;s best to control+click on your .fcp, and choose &#8220;Open With,&#8221; or drag the file onto the correct dock icon. That way, you won&#8217;t unwittingly convert a Final Cut Express file to Pro.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.jamiedepould.com/2010/03/final-cut-xml-exports/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
