<?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>Chip Murphy Films Blog</title>
	<atom:link href="http://chipmurphy.com/blog/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://chipmurphy.com/blog</link>
	<description>Post Production</description>
	<lastBuildDate>Fri, 01 Jul 2011 22:13:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>Goodbye FCP, Hello Premiere Pro.</title>
		<link>http://chipmurphy.com/blog/?p=58</link>
		<comments>http://chipmurphy.com/blog/?p=58#comments</comments>
		<pubDate>Fri, 01 Jul 2011 21:09:58 +0000</pubDate>
		<dc:creator>chipmurphy</dc:creator>
				<category><![CDATA[Avid]]></category>
		<category><![CDATA[Final Cut Pro]]></category>
		<category><![CDATA[Premiere Pro]]></category>

		<guid isPermaLink="false">http://chipmurphy.com/blog/?p=58</guid>
		<description><![CDATA[With the pending demise of FCP7, Adobe Premiere Pro is positioning itself to be the replacement to Final Cut. <a href="http://chipmurphy.com/blog/?p=58">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><span style="color: #ffffff;">It&#8217;s a week and a half after the debut of FCPx and it&#8217;s evident that it isn&#8217;t, and quite frankly, will never be ready for professional, collaborative use.</span></p>
<p><span style="color: #ffffff;">This entry isn&#8217;t about X, if you want to see why it isn&#8217;t ready for primetime, check out <a title="this post" href="http://www.biscardicreative.com/blog/2011/06/were-not-throwing-the-baby-out-with-the-bathwater/">this post</a> and <a title="this post" href="http://www.biscardicreative.com/blog/2011/06/apple-x-faqs-confirmation-our-move-away-is-the-right-one/">this post</a> by Walter Biscardi.</span></p>
<p><span style="color: #ffffff;">This post is about the future of editing and post production and which platform will replace FCP7. Cutting to the chase, I believe it will be Premiere Pro CS5.5, and here&#8217;s why.</span></p>
<p><strong><span style="color: #ffffff;">1. Striking Similarity to FCP7 </span></strong></p>
<p><span style="color: #ffffff;">Both applications have extremely similar GUIs and follow the same workflow premise. The viewer in FCP is the same as the &#8220;Source&#8221; window in Premiere where you can set your in and out point. Effects work the same with the tab in the source window, and the same track structure as FCP. Sound Syncing is easy with CS5.5 by using the merge function with clips in the timeline. Any FCP editor could pick up on the premise of Premiere in 2 hours, max.</span></p>
<p><strong><span style="color: #ffffff;">2. 64 Bit, direct support for RED, XDCAM EX, and H.264 right out of the box</span></strong></p>
<p><span style="color: #ffffff;">The neat thing about Premiere is that it retains the same structure of FCP7, yet under the surface it&#8217;s far more advanced. For starters, it&#8217;s 64 bit, which means it&#8217;ll harness all the RAM your system has to offer.</span></p>
<p><span style="color: #ffffff;">With FCP, you&#8217;re stuck downloading lots of plugins to get it to work with your footage, not so much with Premiere. On top of that, one has to re-transcode H.264, NXCAM, XDCAM, AVC-Intra, DVCPROHD, and RED to appropriate quicktime codecs. While XDCAM may not take long, it doubles the amount of space needed for your material. NXCAM and Canon DSLR, on the other hand, requires a full transcode to ProRes which takes a substantial amount of time.</span></p>
<p><span style="color: #ffffff;">With Premiere, you just navigate to the BPAV or RED .RDM and simply import the files from that location, no re-wrap needed. It just.. works.</span></p>
<p><span style="color: #ffffff;">Final Cut sucked with RED. No Metadata control within FCP for quick grading and lackluster debayer support. Premiere essentially gives you the &#8220;Red Tab&#8221; from Color and addes FLUT control. It also allows you to choose your playback quality from within the App.</span></p>
<p><span style="color: #ffffff;">DSLR/EX series slow motion shooters will welcome the &#8220;interpret footage&#8221; option. instead of having to use Cinema Tools to retime 720p60 footage to playback in slow motion in a 720p24 timeline, you can just change the playback rate from within Premiere.</span></p>
<p><strong><span style="color: #ffffff;">3. Hardware/Legacy Support</span></strong></p>
<p><span style="color: #ffffff;">AJA Kona, Matrox MXO/MXO2, Blackmagic Decklink and probably many more are supported with Premiere, unlike Avid&#8217;s miniscule support (MXO2 mini and AJA IO express). This means facilities geared for FCP can make a switch will most of their hardware supported. Drexel would only have 1 of 4 suites operable with Avid for example. </span></p>
<p><span style="color: #ffffff;">Another cool part of Premiere is that you can &#8220;Import FCP XML&#8221; and get your FCP project into Premiere. </span></p>
<p><strong><span style="color: #ffffff;">4. Deep CS5.5 integration</span></strong></p>
<p><span style="color: #ffffff;">Final Cut Pro was the pandora&#8217;s box of output options. Sure, I could export via compressor, but it was a crapshoot if it would work. Premiere has direct support for Adobe Media Encoder for fast and efficient output. Have to push out a iPad H.264, do it direct from Premiere while harnessing all of the cores of your mac (try that &#8220;Via Compressor&#8221;). No more 4K master needed to show a cut of your RED project.</span></p>
<p><span style="color: #ffffff;">I love Adobe Media Encoder and haven&#8217;t used Compressor in months. Out of the box it supports all your cores and will suck up every drop of processing power your workstation has to offer. The only department it lacks in is multi-computer clusters and the occasional XDCAM EX bug, but other than that, it&#8217;s rock solid.</span></p>
<p><span style="color: #ffffff;">One can send projects directly to After Effects from Compressor. Check out the <a title="workflow" href="http://tv.adobe.com/watch/customer-stories-video-film-and-audio/postproduction-on-the-social-network/">workflow</a> <em>The Social Network</em> utilized.</span></p>
<p><span style="color: #ffffff;">And you can send Premiere Timelines directly to Adobe Encore, which is Adobe&#8217;s answer to DVD Studio Pro (which allows you to create complete menus with buttons directly in photoshop).</span></p>
<p><strong><span style="color: #ffffff;">5. There&#8217;s a reason shops had FCP7 and didn&#8217;t have Avid&#8230;</span></strong></p>
<p><span style="color: #ffffff;">This is purely opinion here. You&#8217;ve been warned. </span></p>
<p><span style="color: #ffffff;">Why would a facility that previously chose FCP7 now revert to Avid if there is an extremely similar option to make the switch to?</span></p>
<p><span style="color: #ffffff;">Facilities will probably be turned off at the $2,000 price point for just the NLE and &#8220;Avid Studio&#8221; (which isn&#8217;t that great), where as you can get Adobe Production Premium for $1.600. And you get</span></p>
<p><span style="color: #ffffff;">-Photoshop, Illustrator, Adobe Media Encoder, Adobe Encore, After Effects, Premiere, OnLocation, and Audition.</span></p>
<p><span style="color: #ffffff;">My point is, if a facility already avoided Avid and chose FCP, why would they turn to Avid? It just doesn&#8217;t make sense.</span></p>
<p><span style="color: #ffffff;">Peace out Final Cut. You have been replaced with the Adobe Suite on my Dock. Hmm.. but should I buy a PC next time for half the price of a Mac Pro&#8230;</span></p>
<p><span style="color: #ffffff;">&#8212;</span></p>
<p><span style="color: #ffffff;">What do you think? Add some comments below</span></p>
]]></content:encoded>
			<wfw:commentRss>http://chipmurphy.com/blog/?feed=rss2&#038;p=58</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fonts &amp; iDVD</title>
		<link>http://chipmurphy.com/blog/?p=39</link>
		<comments>http://chipmurphy.com/blog/?p=39#comments</comments>
		<pubDate>Sun, 19 Dec 2010 07:55:50 +0000</pubDate>
		<dc:creator>chipmurphy</dc:creator>
				<category><![CDATA[Final Cut Pro]]></category>

		<guid isPermaLink="false">http://chipmurphy.com/blog/?p=39</guid>
		<description><![CDATA[iDVD and the Lucinda Grande font in FCP are bad. Be Bold. <a href="http://chipmurphy.com/blog/?p=39">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Use iDVD and the &#8220;Lucida Grande&#8221; font in FCP if you want to look like an amateur.</p>
<p>Lots of people have been nagging me to install iDVD onto the computers in the Drexel editing labs lately, and here&#8217;s why it&#8217;s not happening.</p>
<p>You&#8217;re all film majors. You pay $35k+ a year to go to film school, so learn to use a real app like DVD Studio Pro, or Adobe&#8217;s solution, Encore. I know everyone isn&#8217;t a post production guru, so that&#8217;s why i wrote the book on post production (it&#8217;s the PDF on the desktop). Anyone who can read a simple PDF can create a menu-less first play DVD that will use a good render engine, Compressor or Adobe Media Encoder, instead of the god awful iDVD one. At the very least, everyone in the program should know how to author a basic DVD using DVDSP.</p>
<p>If iDVD was on there, the crappy template menus would be used to death, both for in-class use, and more horrifyingly, client use.</p>
<p>Put on your client&#8217;s shoes for a second. If you were paying good money for a job, wouldn&#8217;t you want the person you hired to use the best software out there? It&#8217;s horrible quality and the client will see right through it. It&#8217;s like showing up to a wedding using a flip-cam or PD-170. Also, the argument &#8220;I don&#8217;t know how to use DVDSP&#8221; doesn&#8217;t work on client ; learn it.</p>
<p>In the same veign, CHANGE YOUR DAMN FONTS IN FINAL CUT. I&#8217;m working on remixing the content for the TV in the UCross lobby and litterally half of the projects have &#8220;Lucinda Grande&#8221; for the credits, or the intro title card (over black naturally with FCP&#8217;s notorious not-centered default).</p>
<p>I&#8217;m guilty of it, I&#8217;ve outputted masters with it. But I regret it on multiple levels. It just screams amateur/youtube/themasses/filmstudent/nocreativity. It also lets everyone know you cut in on FCP, which can be a good or bad thing.</p>
<p>But more importantly it shows (educated) viewers that you didn&#8217;t think everything through and you&#8217;re cool with cookie cutter template designs (same deal as iDVD menus).</p>
<p>Don&#8217;t be plain and boring. Mix it up.</p>
<p>Oh, and if you&#8217;re feeling especially dangerous at the time, pick a serif font. Mix up your fonts, make it personal, I tend to use Gill Sans.</p>
]]></content:encoded>
			<wfw:commentRss>http://chipmurphy.com/blog/?feed=rss2&#038;p=39</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

