<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Final-Cut on WELLINGTON ROAD Pictures</title>
    <link>https://wellys.org/wellysblog/tags/final-cut/</link>
    <description>Recent content in Final-Cut on WELLINGTON ROAD Pictures</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 03 Aug 2009 17:59:28 +0000</lastBuildDate>
    <atom:link href="https://wellys.org/wellysblog/tags/final-cut/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>FCP 7 and ProRes</title>
      <link>https://wellys.org/wellysblog/posts/fcp-7-and-prores/</link>
      <pubDate>Mon, 03 Aug 2009 17:59:28 +0000</pubDate>
       <guid isPermaLink="false">http://www.wellys.org/wellysblog/?p=146</guid> 
      <description>&lt;p&gt;FCP 7 introduces a 3 new HD codecs for production work, ProRes 4444, ProRes 422 (LT) and ProRes 422 (Proxy). With these additions, this brings to five versions of HD codecs Â available for production work. I did a simple comparison of Flip H.264 transcoding to all 5 versions, knowing full well that I wasn&amp;rsquo;t starting with the best source material.&lt;/p&gt;
&lt;p&gt;The only version where I could see a difference was with ProRes 422 (Proxy). There were artifacts and a loss of detail. LT looked great, with no perceptible differences on up to 4444. Which means given the source, the best I could use is LT. That said, I did have striking differences in gamma between the new codecs looking identical to the source material and the &amp;ldquo;older&amp;rdquo; codecs, 422 and 422 (HQ) being much darker and losing details in the shadows.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Thanks, Norman!</title>
      <link>https://wellys.org/wellysblog/posts/thanks-norman/</link>
      <pubDate>Mon, 27 Jul 2009 00:34:53 +0000</pubDate>
       <guid isPermaLink="false">http://www.wellys.org/wellysblog/?p=142</guid> 
      <description>&lt;p&gt;I was thinking this, and was going to write about it but I didn&amp;rsquo;t have the depth of experience to make the point as clear as &lt;a href=&#34;http://normanhollyn.com/2009/07/23/final-cut-pro-baby-steps-into-the-future/&#34; title=&#34;Final Cut Pro 7 comments &#34;&gt;Norman does&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In his blog, &lt;a href=&#34;http://normanhollyn.com/&#34; title=&#34;Norman Hollyn&#39;s blog&#34;&gt;Hollyn-wood (Norman, that is)&lt;/a&gt;, Norman makes the point that the price cuts and the focus on ease of use sets this upgrade to Final Cut Pro/Studio as a significant push by Apple towards the low-end side of video editing. He doesn&amp;rsquo;t mean that Apple took features away or that Final Cut Pro isn&amp;rsquo;t capable of editing high-end feature films, what Apple did do was to introduce ways of helping the not-so-good be a lot better or sometimes, good-enough. AND, they dropped the price.&lt;/p&gt;</description>
    </item>
    <item>
      <title>iMovie 09 and Flip Ultra HD</title>
      <link>https://wellys.org/wellysblog/posts/imovie-09-and-flip-ultra-hd/</link>
      <pubDate>Sun, 21 Jun 2009 16:17:33 +0000</pubDate>
       <guid isPermaLink="false">http://www.wellys.org/wellysblog/?p=118</guid> 
      <description>&lt;p&gt;There seem to be a few questions as to the compatibility of the Flip Ultra HD and iMovie 09. Â The Flip Ultra HD and iMovie work great together! The latest version of iMovie 8.0.3 added the ability to &lt;a href=&#34;http://www.unlockingimovie.com/2009/06/imovie-v803-more-than-meets-eye.html&#34;&gt;optimize video.&lt;/a&gt; I started with 8.0.3, so I&amp;rsquo;m unsure on what I couldn&amp;rsquo;t do before .0.3 was released. A couple of quick points:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The Flip Ultra HD comes bundled withÂ FlipShare. It seems to work well enough for trimming and emailing videos but when you have iMovie at your fingertips, FlipShare is a bit lacking. FlipShare requires the 3ivx MPEG decoder. This decoder is included in the FlipShare software. If it isn&amp;rsquo;t installed, FlipShare will ask to install it.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;FlipShare can trim video and &amp;ldquo;create a movie&amp;rdquo; by linking videos together, adding a title and credits, and a music clip. No great shakes but its free and is easy to use AND it comes on the camera so you can use it anywhere.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Compressor (and multiple cores) is your friend</title>
      <link>https://wellys.org/wellysblog/posts/compressor-and-multiple-cores-is-your-friend/</link>
      <pubDate>Tue, 05 May 2009 03:23:43 +0000</pubDate>
       <guid isPermaLink="false">http://www.wellys.org/wellysblog/?p=54</guid> 
      <description>&lt;p&gt;This is a big deal.&lt;/p&gt;
&lt;p&gt;In addition to what this note says &lt;a href=&#34;http://www.digitalrebellion.com/blog/posts/using_compressor_with_multiple_cores.html&#34;&gt;note says&lt;/a&gt;, you can use other computers to render your files. It has taken me a little while to figure this out. This tutorial describes just using one computer but you can do the same for multiple computers. I did try this on a Dual 1GHz G4 and it slowed things down, so make sure that the additional computers have sufficient power.&lt;/p&gt;</description>
    </item>
    <item>
      <title>FCP&#39;s DV Compatibility issues</title>
      <link>https://wellys.org/wellysblog/posts/fcp-s-dv-compatibility-issues/</link>
      <pubDate>Mon, 04 May 2009 01:56:45 +0000</pubDate>
       <guid isPermaLink="false">http://www.wellys.org/wellysblog/?p=50</guid> 
      <description>&lt;p&gt;While creating the previous post on iMovie 09, I ran across a very &lt;a href=&#34;http://pogue.blogs.nytimes.com/2009/04/10/camcorder-conflicts-with-final-cut/&#34;&gt;interesting post&lt;/a&gt; by David Pogue, related to his desire to combine Flip footage with footage from a high end Canon HD camera.&lt;/p&gt;
&lt;p&gt;He was attempting to combine two vastly different video file types; Flip&amp;rsquo;s H.264 and Canon&amp;rsquo;s AIC. Final Cut Pro was re-rendering every time he did an edit, causing his workflow to slow dramatically.&lt;/p&gt;
&lt;p&gt;His solution was to ensure that both files were rendered to the same format before continuing to edit.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
