<?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: Sony EX-1/EX-3 and Final Cut Pro, What&#8217;s Your Workflow?</title>
	<atom:link href="http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/</link>
	<description>Post Production Technology, Reviews, Experiences &#38; Opinion from the Edit Suite.</description>
	<lastBuildDate>Sat, 17 Dec 2011 09:18:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Anonymous</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-6/#comment-319</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 10 May 2011 01:32:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-319</guid>
		<description>Uncompressed or ProRes. Always go uncompressed if possible when keying, it
can make all the difference. The EX-1 is especially good at shooting for
keying if you record the output via SDI uncompressed.
On Mon, May 9, 2011 at 12:51 PM, Echo &lt;
js-kit-m2c-LBPM2L3EI1S8K1764MRJ7118UFOCG8UDPLF7P5BJBIMGH31TJPE0@reply.js-kit.com
</description>
		<content:encoded><![CDATA[<p>Uncompressed or ProRes. Always go uncompressed if possible when keying, it<br />
can make all the difference. The EX-1 is especially good at shooting for<br />
keying if you record the output via SDI uncompressed.<br />
On Mon, May 9, 2011 at 12:51 PM, Echo &lt;<br />
<a href="mailto:js-kit-m2c-LBPM2L3EI1S8K1764MRJ7118UFOCG8UDPLF7P5BJBIMGH31TJPE0@reply.js-kit.com">js-kit-m2c-LBPM2L3EI1S8K1764MRJ7118UFOCG8UDPLF7P5BJBIMGH31TJPE0@reply.js-kit.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fe Tornaghi</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-6/#comment-316</link>
		<dc:creator>Fe Tornaghi</dc:creator>
		<pubDate>Mon, 09 May 2011 17:50:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-316</guid>
		<description>What if you&#039;re exporting an edited short video with choma to be keyed in Adobe After Effects?
What&#039;s the best edited format to deliver it to After Effects for keying?
</description>
		<content:encoded><![CDATA[<p>What if you&#8217;re exporting an edited short video with choma to be keyed in Adobe After Effects?<br />
What&#8217;s the best edited format to deliver it to After Effects for keying?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tonygay</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-5/#comment-166</link>
		<dc:creator>tonygay</dc:creator>
		<pubDate>Thu, 26 Nov 2009 07:05:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-166</guid>
		<description>Cheers, great overview of the process, just have a new EX3 in my hands and getting my head around workflows, your insights are great.&lt;br&gt;&lt;br&gt;Tony</description>
		<content:encoded><![CDATA[<p>Cheers, great overview of the process, just have a new EX3 in my hands and getting my head around workflows, your insights are great.</p>
<p>Tony</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hdproductions</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-5/#comment-110</link>
		<dc:creator>hdproductions</dc:creator>
		<pubDate>Wed, 26 Aug 2009 02:04:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-110</guid>
		<description>Hi Thomas love your post, as for card labeling this something I to advice to my clients that I train using XDcam EX workflow.&lt;br&gt;&lt;br&gt;James Wood&lt;br&gt;HD Productions</description>
		<content:encoded><![CDATA[<p>Hi Thomas love your post, as for card labeling this something I to advice to my clients that I train using XDcam EX workflow.</p>
<p>James Wood<br />HD Productions</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: macguitarman</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-5/#comment-86</link>
		<dc:creator>macguitarman</dc:creator>
		<pubDate>Sun, 12 Jul 2009 00:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-86</guid>
		<description>Also, just my 2 cents, but with all the formats out there, why use XDCAM?, which is MPEG-2 Long GOP&lt;br&gt;&lt;br&gt;And why buy this camera at 10K&lt;br&gt;&lt;br&gt;To me the camera to get is clearly a Panasonic HPX-170, DVCPRO HD, with HD-SDI out. $6K&lt;br&gt;&lt;br&gt;Then get the new secret box, the AJA Ki Pro, and record Apple Pro Res 422 natively on a 250 GB HD&lt;br&gt;&lt;br&gt;Several  issues solved:&lt;br&gt;&lt;br&gt;- Goodbye MPEG-2 Long GOP as an acquisition codec, and hello Apple ProRes 422, a full raster codec, very important&lt;br&gt;&lt;br&gt;- Goodbye long transcodes in Final Cut Pro from MPEG-2 (a playback codec, an obsolete one IMO)&lt;br&gt;&lt;br&gt;- Goodbye expensive P2 cards or SxS cards, a joke really. The Ki Pro 250 GB hard drive is 500 bucks or so, but beats the heck out of $700 16 GB P2 card or SxS card.&lt;br&gt;&lt;br&gt;To me this is the new, great workflow, HD-SDI out, Apple ProRes 422 recorded in the KI Pro, walk over to your Mac and drag the ProRes files into a Final Cut Pro ProRes 422 timeline and start editing. Output to H.264. Done. Can even play the outputted ProRes file from the Ki Pro itself to a large screen, in a digital theatre, no more expensive film transfers. IMO this is where the industry is not only going, but already started.&lt;br&gt;&lt;br&gt;6K + 3K for the KI Pro</description>
		<content:encoded><![CDATA[<p>Also, just my 2 cents, but with all the formats out there, why use XDCAM?, which is MPEG-2 Long GOP</p>
<p>And why buy this camera at 10K</p>
<p>To me the camera to get is clearly a Panasonic HPX-170, DVCPRO HD, with HD-SDI out. $6K</p>
<p>Then get the new secret box, the AJA Ki Pro, and record Apple Pro Res 422 natively on a 250 GB HD</p>
<p>Several  issues solved:</p>
<p>- Goodbye MPEG-2 Long GOP as an acquisition codec, and hello Apple ProRes 422, a full raster codec, very important</p>
<p>- Goodbye long transcodes in Final Cut Pro from MPEG-2 (a playback codec, an obsolete one IMO)</p>
<p>- Goodbye expensive P2 cards or SxS cards, a joke really. The Ki Pro 250 GB hard drive is 500 bucks or so, but beats the heck out of $700 16 GB P2 card or SxS card.</p>
<p>To me this is the new, great workflow, HD-SDI out, Apple ProRes 422 recorded in the KI Pro, walk over to your Mac and drag the ProRes files into a Final Cut Pro ProRes 422 timeline and start editing. Output to H.264. Done. Can even play the outputted ProRes file from the Ki Pro itself to a large screen, in a digital theatre, no more expensive film transfers. IMO this is where the industry is not only going, but already started.</p>
<p>6K + 3K for the KI Pro</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: macguitarman</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-5/#comment-85</link>
		<dc:creator>macguitarman</dc:creator>
		<pubDate>Sun, 12 Jul 2009 00:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-85</guid>
		<description>My guess, I&#039;ll chime in,&lt;br&gt;&lt;br&gt;XDCAM HQ is 35 Mb / sec (megbit, not megabyte). &lt;br&gt;&lt;br&gt;MB = megabyte&lt;br&gt;&lt;br&gt;Mb = megabit&lt;br&gt;&lt;br&gt;Have to be aware of that&lt;br&gt;&lt;br&gt;To get megabytes from megabits, divide by 8, so 35 / 8 = 4.35 MB, so this is totally correct&lt;br&gt;&lt;br&gt;ProRes HQ is 220 Mb, 220/8 = 27.5 MB&lt;br&gt;&lt;br&gt;ProRes is 145 Mb, 145/8 = 18.12 MB&lt;br&gt;&lt;br&gt;From what I hear and have seen in the industry concerning ProRes 422, it is hard to discern ProRes HQ and ProRes. I just use ProRes.&lt;br&gt;&lt;br&gt;&lt;a href=&quot;mailto:macguitarman@mac.com&quot; rel=&quot;nofollow&quot;&gt;macguitarman@mac.com&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>My guess, I&#39;ll chime in,</p>
<p>XDCAM HQ is 35 Mb / sec (megbit, not megabyte). </p>
<p>MB = megabyte</p>
<p>Mb = megabit</p>
<p>Have to be aware of that</p>
<p>To get megabytes from megabits, divide by 8, so 35 / 8 = 4.35 MB, so this is totally correct</p>
<p>ProRes HQ is 220 Mb, 220/8 = 27.5 MB</p>
<p>ProRes is 145 Mb, 145/8 = 18.12 MB</p>
<p>From what I hear and have seen in the industry concerning ProRes 422, it is hard to discern ProRes HQ and ProRes. I just use ProRes.</p>
<p><a href="mailto:macguitarman@mac.com" rel="nofollow">macguitarman@mac.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sleepwagon</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-5/#comment-79</link>
		<dc:creator>sleepwagon</dc:creator>
		<pubDate>Mon, 06 Jul 2009 00:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-79</guid>
		<description>Why does FCP state in the project window that my XDCAM Data Rate is 4.3MB/sec? Isn&#039;t XDCAM HQ 35MB/sec? When I go to capture scratch it says the clips are 35MB/sec so why does FCP do this? And why when I bring in ProRes422 HQ does it list its data rate at 22.5MB/sec?&lt;br&gt;Thanks&lt;br&gt;Andrew</description>
		<content:encoded><![CDATA[<p>Why does FCP state in the project window that my XDCAM Data Rate is 4.3MB/sec? Isn&#39;t XDCAM HQ 35MB/sec? When I go to capture scratch it says the clips are 35MB/sec so why does FCP do this? And why when I bring in ProRes422 HQ does it list its data rate at 22.5MB/sec?<br />Thanks<br />Andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sleepwagon</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-4/#comment-78</link>
		<dc:creator>sleepwagon</dc:creator>
		<pubDate>Mon, 06 Jul 2009 00:10:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-78</guid>
		<description>Why does FCP state in the project window that my XDCAM Data Rate is 4.3MB/sec? Isn&#039;t XDCAM HQ 35MB/sec? When I go to capture scratch it says the clips are 35MB/sec so why does FCP do this? And why when I bring in ProRes422 HQ does it list its data rate at 22.5MB/sec?&lt;br&gt;Thanks&lt;br&gt;Andrew</description>
		<content:encoded><![CDATA[<p>Why does FCP state in the project window that my XDCAM Data Rate is 4.3MB/sec? Isn&#39;t XDCAM HQ 35MB/sec? When I go to capture scratch it says the clips are 35MB/sec so why does FCP do this? And why when I bring in ProRes422 HQ does it list its data rate at 22.5MB/sec?<br />Thanks<br />Andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: suitetake</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-4/#comment-70</link>
		<dc:creator>suitetake</dc:creator>
		<pubDate>Fri, 19 Jun 2009 23:01:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-70</guid>
		<description>I would suggest that you take a look at a post I did on the LTO drive we use. In addition to covering the LTO, it shows how we maintain a long term archival system for everything that we shoot and edit. &lt;br&gt;&lt;br&gt;Hard drives are not good for the long term, take my word for it!&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.suitetake.com/2009/04/06/nab-preivew-cache-a-lto-4-archive-drive-for-video-pros/&quot; rel=&quot;nofollow&quot;&gt;http://www.suitetake.com/2009/04/06/nab-preivew...&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I would suggest that you take a look at a post I did on the LTO drive we use. In addition to covering the LTO, it shows how we maintain a long term archival system for everything that we shoot and edit. </p>
<p>Hard drives are not good for the long term, take my word for it!</p>
<p><a href="http://www.suitetake.com/2009/04/06/nab-preivew-cache-a-lto-4-archive-drive-for-video-pros/" rel="nofollow">http://www.suitetake.com/2009/04/06/nab-preivew&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steveret30</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-4/#comment-69</link>
		<dc:creator>steveret30</dc:creator>
		<pubDate>Fri, 19 Jun 2009 22:49:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-69</guid>
		<description>Hi, &lt;br&gt;&lt;br&gt;I don&#039;t know if you are still monitoring this post, but I wondered what your archive process looks like. Right now we pretty much store entire projects to our server which can be quite large. Disk space is pretty cheap, but I&#039;m always looking for a better way to work.&lt;br&gt;&lt;br&gt;Steve</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>I don&#39;t know if you are still monitoring this post, but I wondered what your archive process looks like. Right now we pretty much store entire projects to our server which can be quite large. Disk space is pretty cheap, but I&#39;m always looking for a better way to work.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ANDYLEWIS</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-4/#comment-62</link>
		<dc:creator>ANDYLEWIS</dc:creator>
		<pubDate>Sun, 31 May 2009 06:07:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-62</guid>
		<description>I wonder if it&#039;s possible to finish the edit then put the programme back on the SXS card. then the camera can play out SDI or composite to any format vtr? Is this a possibility?</description>
		<content:encoded><![CDATA[<p>I wonder if it&#39;s possible to finish the edit then put the programme back on the SXS card. then the camera can play out SDI or composite to any format vtr? Is this a possibility?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: suitetake</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-4/#comment-43</link>
		<dc:creator>suitetake</dc:creator>
		<pubDate>Thu, 09 Apr 2009 03:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-43</guid>
		<description>That works great when you capture your footage directly into ProRes. But when you shoot tapeless often your only option is to transcode all of your footage after the fact to ProRes. This is not a fast process, and at least in my world it&#039;s never an option budget or time wise. In a perfect world you would just capture straight to ProRes - it is the great universal codec inside of FCP - but that&#039;s just not the reality for many people, myself included. &lt;br&gt;&lt;br&gt;And my experience with letting FCP size HD images into a SD timeline has been pretty darn good. I&#039;m pretty picky about image quality and signal path, and I have not been disappointed yet. So that&#039;s all I can go on. In fact, just recently we had some SD anamorphic footage that was scaled up to 720p inside the timeline, and I was shocked how good it looked. &lt;br&gt;&lt;br&gt;We did a lot of testing before proceeding with this workflow, and it works for us and our needs. But everybody needs to do their own test and make that decision for themselves.</description>
		<content:encoded><![CDATA[<p>That works great when you capture your footage directly into ProRes. But when you shoot tapeless often your only option is to transcode all of your footage after the fact to ProRes. This is not a fast process, and at least in my world it&#39;s never an option budget or time wise. In a perfect world you would just capture straight to ProRes &#8211; it is the great universal codec inside of FCP &#8211; but that&#39;s just not the reality for many people, myself included. </p>
<p>And my experience with letting FCP size HD images into a SD timeline has been pretty darn good. I&#39;m pretty picky about image quality and signal path, and I have not been disappointed yet. So that&#39;s all I can go on. In fact, just recently we had some SD anamorphic footage that was scaled up to 720p inside the timeline, and I was shocked how good it looked. </p>
<p>We did a lot of testing before proceeding with this workflow, and it works for us and our needs. But everybody needs to do their own test and make that decision for themselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moocow</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-3/#comment-42</link>
		<dc:creator>moocow</dc:creator>
		<pubDate>Wed, 08 Apr 2009 23:39:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-42</guid>
		<description>Really?  You are letting FCP do a downconversion for you??  FCP is awful at conversions.  Edit native in ProRes (That&#039;s a big reason this codec was created, to work with &quot;HD&quot; in realtime) and downconvert with whatever means you have upon output. (NOT FCP)&lt;br&gt;My 2 Cents,&lt;br&gt;Joey</description>
		<content:encoded><![CDATA[<p>Really?  You are letting FCP do a downconversion for you??  FCP is awful at conversions.  Edit native in ProRes (That&#39;s a big reason this codec was created, to work with &#8220;HD&#8221; in realtime) and downconvert with whatever means you have upon output. (NOT FCP)<br />My 2 Cents,<br />Joey</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jbroder</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-3/#comment-41</link>
		<dc:creator>Jbroder</dc:creator>
		<pubDate>Wed, 08 Apr 2009 18:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-41</guid>
		<description>I recently found your site since I just finished shooting on EX-1 for the first time.  Thank you for your articles and constant feedback.&lt;br&gt;&lt;br&gt;My question is probably a &quot;duh&quot; question but here it goes.&lt;br&gt;&lt;br&gt;I was able to use the &quot;Log and Transfer&quot; to import all my footage into the FCP project file.  Now my question is when you start a new project what settings do you use?  I know it varies for each type of project.&lt;br&gt;&lt;br&gt;We shot Sony XDCAM 1080 30p&lt;br&gt;&lt;br&gt;Under easy setup I found and am trying -- FORMAT: Sony XDCAM HD - USE: XDCAM EX 1080p30 VBR -  RATE: 29.97&lt;br&gt;&lt;br&gt;Is this the correct setup or do you recommend a different one or way?&lt;br&gt;&lt;br&gt;Our final output will be to dvd for the client.  Which obv. wants the highest quality they can get.  (Should I follow your previous post/comment as my answer?)&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;&lt;br&gt;Josh</description>
		<content:encoded><![CDATA[<p>I recently found your site since I just finished shooting on EX-1 for the first time.  Thank you for your articles and constant feedback.</p>
<p>My question is probably a &#8220;duh&#8221; question but here it goes.</p>
<p>I was able to use the &#8220;Log and Transfer&#8221; to import all my footage into the FCP project file.  Now my question is when you start a new project what settings do you use?  I know it varies for each type of project.</p>
<p>We shot Sony XDCAM 1080 30p</p>
<p>Under easy setup I found and am trying &#8212; FORMAT: Sony XDCAM HD &#8211; USE: XDCAM EX 1080p30 VBR &#8211;  RATE: 29.97</p>
<p>Is this the correct setup or do you recommend a different one or way?</p>
<p>Our final output will be to dvd for the client.  Which obv. wants the highest quality they can get.  (Should I follow your previous post/comment as my answer?)</p>
<p>Thanks,</p>
<p>Josh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: suitetake</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-3/#comment-38</link>
		<dc:creator>suitetake</dc:creator>
		<pubDate>Tue, 31 Mar 2009 12:40:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-38</guid>
		<description>If you know that you&#039;re going to SD already, here is how I would handle it (and how I have in the past). &lt;br&gt;&lt;br&gt;Everything we shoot is HD now, regardless of final output. So there are several times when we just need SD on the output. What we normally do now is create a NTSD (or PAL) SD sequence, set it to 16x9 anamorphic (so we can retain the wide screen aspect ratio) and make sure the sequence codec is ProRes (non-HQ in this case). Now, as we edit our HD footage into the SD timeline it is automatically scaled to fit. We can edit fast, most things will play back in real time (although I have to admit we have pretty new Mac Pros and fiber raids) and if we ever need to do any scaling up of images there is all the room in the world to blow things up and have them look great. When we&#039;re ready for output, we render everything and export a self-contained QT movie that&#039;s already in the SD format. &lt;br&gt;&lt;br&gt;There are a few other benefits to going this route. If you have any graphics to create and render, you only need to do them in the SD format. DVD compression goes much faster since you&#039;re dealing with SD files and your SD image will look awesome. We&#039;ve had great experience with this workflow. &lt;br&gt;&lt;br&gt;As to your multi-cam question, I have to say I can only tell you what I would try myself. I have not actually had this problem yet though. Given everything you&#039;ve said, knowing I&#039;m not only going to SD but I&#039;m also in need of doing multi-cam with a client in session, I would almost certainly have transcoded my footage to ProRes and worked in ProRes instead of native. Again, I say that without having actually done it myself, but that would be my first thought. &lt;br&gt;&lt;br&gt;If somebody else has a better (maybe even first hand) experience, please feel free to chime in here.</description>
		<content:encoded><![CDATA[<p>If you know that you&#39;re going to SD already, here is how I would handle it (and how I have in the past). </p>
<p>Everything we shoot is HD now, regardless of final output. So there are several times when we just need SD on the output. What we normally do now is create a NTSD (or PAL) SD sequence, set it to 16&#215;9 anamorphic (so we can retain the wide screen aspect ratio) and make sure the sequence codec is ProRes (non-HQ in this case). Now, as we edit our HD footage into the SD timeline it is automatically scaled to fit. We can edit fast, most things will play back in real time (although I have to admit we have pretty new Mac Pros and fiber raids) and if we ever need to do any scaling up of images there is all the room in the world to blow things up and have them look great. When we&#39;re ready for output, we render everything and export a self-contained QT movie that&#39;s already in the SD format. </p>
<p>There are a few other benefits to going this route. If you have any graphics to create and render, you only need to do them in the SD format. DVD compression goes much faster since you&#39;re dealing with SD files and your SD image will look awesome. We&#39;ve had great experience with this workflow. </p>
<p>As to your multi-cam question, I have to say I can only tell you what I would try myself. I have not actually had this problem yet though. Given everything you&#39;ve said, knowing I&#39;m not only going to SD but I&#39;m also in need of doing multi-cam with a client in session, I would almost certainly have transcoded my footage to ProRes and worked in ProRes instead of native. Again, I say that without having actually done it myself, but that would be my first thought. </p>
<p>If somebody else has a better (maybe even first hand) experience, please feel free to chime in here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LittleVision</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-3/#comment-37</link>
		<dc:creator>LittleVision</dc:creator>
		<pubDate>Tue, 31 Mar 2009 10:28:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-37</guid>
		<description>Thank you Tom,&lt;br&gt;&lt;br&gt; &lt;br&gt;&lt;br&gt;Actually, I do intend to go to SD but only after the edit as there is one&lt;br&gt;back camera with which we were deliberately conservatively wide and I hope&lt;br&gt;to be able to punch in a little on the scale at certain times in the show to&lt;br&gt;mask out unwanted things at the edge of frame and bring up the size of the&lt;br&gt;action. Nothing huge but I had supposed that there would be plenty of&lt;br&gt;latitude for this given the ratio of pixels HD:SD-wise. If I converted to SD&lt;br&gt;first and then did this scaling afterwards I know this would not work. So I&lt;br&gt;am wondering id there an intermediate solution (ProRes, Apple Intermediate&lt;br&gt;Codec etc.) which would make my workflow easier.&lt;br&gt;&lt;br&gt; &lt;br&gt;&lt;br&gt;An interesting thing I have noticed is that when I put my multiclip down on&lt;br&gt;the native sequence (and this happens whether or not I set the render&lt;br&gt;settings to same as sequence codec or ProRes), turn off my external video&lt;br&gt;and set my RT to Unlimited and Playback to Dynamic or Low, I get a green bar&lt;br&gt;across the top of the sequence. This allows me to edit away in multiclip&lt;br&gt;once I set the Playhead Sync to Open. However, if for any reason I render a&lt;br&gt;part of the sequence or, as happened, I go away for a while and come back to&lt;br&gt;find that auto-render has rendered the whole thing, I then have a purple bar&lt;br&gt;above the sequence but playback in multiclip no longer works, no matter how&lt;br&gt;I mess with my settings afterwards. It took me a long time to figure out why&lt;br&gt;it was no longer working  nothing in the manual hinted at this. I had to&lt;br&gt;make a new sequence and copy and paste the entire sequence into it to regain&lt;br&gt;my green bar and allow myself to continue editing in multiclip mode. Now I&lt;br&gt;have auto-render off. Its troublesome because soon I will have a client on&lt;br&gt;my shoulder who will need to see the thing playing in multiclip in order for&lt;br&gt;us to make fine adjustments, yet wherever I do punch in scale-wise on a&lt;br&gt;camera, I have to render in order for the picture not to be horrible. Should&lt;br&gt;I media manage the whole thing into a different project with a different&lt;br&gt;codec?&lt;br&gt;&lt;br&gt; &lt;br&gt;&lt;br&gt;Thanks again,&lt;br&gt;&lt;br&gt; &lt;br&gt;&lt;br&gt;Éamon &lt;br&gt;&lt;br&gt;  &lt;br&gt;&lt;br&gt;LittleVision</description>
		<content:encoded><![CDATA[<p>Thank you Tom,</p>
<p>Actually, I do intend to go to SD but only after the edit as there is one<br />back camera with which we were deliberately conservatively wide and I hope<br />to be able to punch in a little on the scale at certain times in the show to<br />mask out unwanted things at the edge of frame and bring up the size of the<br />action. Nothing huge but I had supposed that there would be plenty of<br />latitude for this given the ratio of pixels HD:SD-wise. If I converted to SD<br />first and then did this scaling afterwards I know this would not work. So I<br />am wondering id there an intermediate solution (ProRes, Apple Intermediate<br />Codec etc.) which would make my workflow easier.</p>
<p>An interesting thing I have noticed is that when I put my multiclip down on<br />the native sequence (and this happens whether or not I set the render<br />settings to same as sequence codec or ProRes), turn off my external video<br />and set my RT to Unlimited and Playback to Dynamic or Low, I get a green bar<br />across the top of the sequence. This allows me to edit away in multiclip<br />once I set the Playhead Sync to Open. However, if for any reason I render a<br />part of the sequence or, as happened, I go away for a while and come back to<br />find that auto-render has rendered the whole thing, I then have a purple bar<br />above the sequence but playback in multiclip no longer works, no matter how<br />I mess with my settings afterwards. It took me a long time to figure out why<br />it was no longer working  nothing in the manual hinted at this. I had to<br />make a new sequence and copy and paste the entire sequence into it to regain<br />my green bar and allow myself to continue editing in multiclip mode. Now I<br />have auto-render off. Its troublesome because soon I will have a client on<br />my shoulder who will need to see the thing playing in multiclip in order for<br />us to make fine adjustments, yet wherever I do punch in scale-wise on a<br />camera, I have to render in order for the picture not to be horrible. Should<br />I media manage the whole thing into a different project with a different<br />codec?</p>
<p>Thanks again,</p>
<p>Éamon </p>
<p>LittleVision</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: suitetake</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-3/#comment-36</link>
		<dc:creator>suitetake</dc:creator>
		<pubDate>Tue, 31 Mar 2009 01:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-36</guid>
		<description>I never even thought about staying native for a multi-clip project, but yes I can see how that would really tax the machine. It’s doing a lot of decompressing of multiple streams on the fly. Even a new Mac Pro would be a bit challenged. If you know you’re going to be going the multi-clip route, doing a conversion to anther format might be a good idea. And this would be a good time to ask yourself if you NEED to have your final output in HD. If not, transcode to SD and really help your cause. &lt;br&gt;&lt;br&gt;I think your DVD problem might be that you’re doing the encoding inside of DVDSP. While they say it uses compressor in the background, I’ve always found I have much better results using the “best” settings inside of compressor. Then, bring the already compressed elements into DVDSP and burn your DVD. I would be shocked if you didn&#039;t see a huge difference. &lt;br&gt;&lt;br&gt;Hope this helps. Tom</description>
		<content:encoded><![CDATA[<p>I never even thought about staying native for a multi-clip project, but yes I can see how that would really tax the machine. It’s doing a lot of decompressing of multiple streams on the fly. Even a new Mac Pro would be a bit challenged. If you know you’re going to be going the multi-clip route, doing a conversion to anther format might be a good idea. And this would be a good time to ask yourself if you NEED to have your final output in HD. If not, transcode to SD and really help your cause. </p>
<p>I think your DVD problem might be that you’re doing the encoding inside of DVDSP. While they say it uses compressor in the background, I’ve always found I have much better results using the “best” settings inside of compressor. Then, bring the already compressed elements into DVDSP and burn your DVD. I would be shocked if you didn&#39;t see a huge difference. </p>
<p>Hope this helps. Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LittleVision</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-2/#comment-35</link>
		<dc:creator>LittleVision</dc:creator>
		<pubDate>Fri, 27 Mar 2009 21:09:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-35</guid>
		<description>I have read this article and dialogue with interest as I have just shot a dance show with three EX-1&#039;s (my first time using this format) and am about to start editing in multicam. I had read this article before shooting and figured I&#039;d stick with the native sequence settings in FCP. However, I hadn&#039;t factored in the extra load editing in multiclip mode adds. I have just started experimenting using the native codec in the sequence settings and dropping in a multiclip. It seems very processor heavy and I had to reduce playback quality to low for it to play back without dropping frames. I could probably get used to that until the edit is finished and I have to start colour correction and so on but is there a better workflow for multicam editing with XDCAM footage?&lt;br&gt;Also, my client asked me to &quot;run off&quot; a DVD of the show from the back camera so I dropped that onto a separate sequence - again set to native codec - and exported a non-self-contained movie using &quot;Export Quicktime&quot; with current settings and imported this to DVD Studio Pro, encoded and burned a DVD. I was disappointed that whenever there was any reveal or zoom, however subtle, the horizontal lines in the picture would become watery and stay watery until the zoom/reveal ended. Otherwise the pic quality was okay. So my next question is, what is the best route to an SD DVD from an XDCAM timeline?&lt;br&gt;&lt;br&gt;Thanks in advance for advice,&lt;br&gt;&lt;br&gt;Éamon</description>
		<content:encoded><![CDATA[<p>I have read this article and dialogue with interest as I have just shot a dance show with three EX-1&#39;s (my first time using this format) and am about to start editing in multicam. I had read this article before shooting and figured I&#39;d stick with the native sequence settings in FCP. However, I hadn&#39;t factored in the extra load editing in multiclip mode adds. I have just started experimenting using the native codec in the sequence settings and dropping in a multiclip. It seems very processor heavy and I had to reduce playback quality to low for it to play back without dropping frames. I could probably get used to that until the edit is finished and I have to start colour correction and so on but is there a better workflow for multicam editing with XDCAM footage?<br />Also, my client asked me to &#8220;run off&#8221; a DVD of the show from the back camera so I dropped that onto a separate sequence &#8211; again set to native codec &#8211; and exported a non-self-contained movie using &#8220;Export Quicktime&#8221; with current settings and imported this to DVD Studio Pro, encoded and burned a DVD. I was disappointed that whenever there was any reveal or zoom, however subtle, the horizontal lines in the picture would become watery and stay watery until the zoom/reveal ended. Otherwise the pic quality was okay. So my next question is, what is the best route to an SD DVD from an XDCAM timeline?</p>
<p>Thanks in advance for advice,</p>
<p>Éamon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: suitetake</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-2/#comment-33</link>
		<dc:creator>suitetake</dc:creator>
		<pubDate>Mon, 23 Mar 2009 23:03:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-33</guid>
		<description>That is usually how we handle it as well, and the results have been very good. &lt;br&gt;&lt;br&gt;I&#039;ve recently started looking into using Episode Pro as a replacement for compressor, because I don&#039;t think the quality from compressor is always the best it can be. Programs like BitVice do a much better job when it comes to MPEG-2, but that program is more of a one-trick-pony. &lt;br&gt;&lt;br&gt;Enjoy the camera. The more we use it, the more we love it. For the money it&#039;s hard to beat.</description>
		<content:encoded><![CDATA[<p>That is usually how we handle it as well, and the results have been very good. </p>
<p>I&#39;ve recently started looking into using Episode Pro as a replacement for compressor, because I don&#39;t think the quality from compressor is always the best it can be. Programs like BitVice do a much better job when it comes to MPEG-2, but that program is more of a one-trick-pony. </p>
<p>Enjoy the camera. The more we use it, the more we love it. For the money it&#39;s hard to beat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: visualantes</title>
		<link>http://www.suitetake.com/2009/02/20/sony-ex-1ex-3-and-final-cut-pro-whats-your-workflow/comment-page-2/#comment-32</link>
		<dc:creator>visualantes</dc:creator>
		<pubDate>Mon, 23 Mar 2009 14:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.suitetake.com/?p=528#comment-32</guid>
		<description>Thanks for all your advice. I bought the EX-3 last week and very happy.  It looks great.  I also found that most of what I need to do is fine in the &#039;staying native&#039; set up.  Most of my final product is delivered on DVD.  New question:  I usually export to Compressor and use the preset Best Quality 90 min.  than burn a dvd from DVD Studio Pro.  IS this the best way to preserve my image quality or can you suggest something better?  Thanks.</description>
		<content:encoded><![CDATA[<p>Thanks for all your advice. I bought the EX-3 last week and very happy.  It looks great.  I also found that most of what I need to do is fine in the &#39;staying native&#39; set up.  Most of my final product is delivered on DVD.  New question:  I usually export to Compressor and use the preset Best Quality 90 min.  than burn a dvd from DVD Studio Pro.  IS this the best way to preserve my image quality or can you suggest something better?  Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

