<?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: Adobe Creative Suite 5 Video Apps</title>
	<atom:link href="http://www.hd4pc.com/techblog/2010/06/02/adobe-cs5-video-apps/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hd4pc.com/techblog/2010/06/02/adobe-cs5-video-apps/</link>
	<description>Evolving Media Post Production Workflows in Light of Advancing Computer Technology</description>
	<lastBuildDate>Wed, 20 Apr 2011 00:16:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: McCarthyTech</title>
		<link>http://www.hd4pc.com/techblog/2010/06/02/adobe-cs5-video-apps/comment-page-1/#comment-85</link>
		<dc:creator>McCarthyTech</dc:creator>
		<pubDate>Tue, 09 Nov 2010 18:22:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.hd4pc.com/techblog/?p=96#comment-85</guid>
		<description>I don&#039;t understand what you are looking for.  422 isn&#039;t a codec, it is more like a colorspace or compression setting.  Are you looking for ProRes422 or Cineform422, or MPEG422 or smething else.  If you are using the trial, the MPEG encoder is not included, so that will limit your workflow options.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t understand what you are looking for.  422 isn&#8217;t a codec, it is more like a colorspace or compression setting.  Are you looking for ProRes422 or Cineform422, or MPEG422 or smething else.  If you are using the trial, the MPEG encoder is not included, so that will limit your workflow options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.hd4pc.com/techblog/2010/06/02/adobe-cs5-video-apps/comment-page-1/#comment-84</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 09 Nov 2010 17:08:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.hd4pc.com/techblog/?p=96#comment-84</guid>
		<description>We&#039;re running a trial version of Premier and don&#039;t see the option of the 422 codec for export.  Is this a feature lacking in the trial, or are we missing a settings box somewhere?</description>
		<content:encoded><![CDATA[<p>We&#8217;re running a trial version of Premier and don&#8217;t see the option of the 422 codec for export.  Is this a feature lacking in the trial, or are we missing a settings box somewhere?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: McCarthyTech</title>
		<link>http://www.hd4pc.com/techblog/2010/06/02/adobe-cs5-video-apps/comment-page-1/#comment-83</link>
		<dc:creator>McCarthyTech</dc:creator>
		<pubDate>Mon, 08 Nov 2010 21:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.hd4pc.com/techblog/?p=96#comment-83</guid>
		<description>Not that I am aware of.  FCP only supports DSLRs because QT had an existing H264 decoder.  They have not deliberately written software specifically for DSLR files.  This is what leads to the colorspace shift and the decode artifacts.  I have never heard confirmed reports of consistent duplicate frames, but it doesn&#039;t surprise me.  That is why I pushed so hard for Adobe to get away from QT decoding of DSLR files in CS5.  There may not be a solution to your problem in FCP without batch converting all of your footage in CS5 before processing in FCP, which I highly recommend if possible.</description>
		<content:encoded><![CDATA[<p>Not that I am aware of.  FCP only supports DSLRs because QT had an existing H264 decoder.  They have not deliberately written software specifically for DSLR files.  This is what leads to the colorspace shift and the decode artifacts.  I have never heard confirmed reports of consistent duplicate frames, but it doesn&#8217;t surprise me.  That is why I pushed so hard for Adobe to get away from QT decoding of DSLR files in CS5.  There may not be a solution to your problem in FCP without batch converting all of your footage in CS5 before processing in FCP, which I highly recommend if possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.hd4pc.com/techblog/2010/06/02/adobe-cs5-video-apps/comment-page-1/#comment-82</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Mon, 08 Nov 2010 20:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.hd4pc.com/techblog/?p=96#comment-82</guid>
		<description>Upon close inspection of our footage in the FCP timeline, we found, in some of our panning clips, that there is a regular pattern of duplicated frames.  We have one of those same clips loaded in Premier, and all of the individual frames appear.  No dupes; no jittery playback.  Is there some obscure sequence setting that I&#039;m missing in FCP that causes these duplicates?</description>
		<content:encoded><![CDATA[<p>Upon close inspection of our footage in the FCP timeline, we found, in some of our panning clips, that there is a regular pattern of duplicated frames.  We have one of those same clips loaded in Premier, and all of the individual frames appear.  No dupes; no jittery playback.  Is there some obscure sequence setting that I&#8217;m missing in FCP that causes these duplicates?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: McCarthyTech</title>
		<link>http://www.hd4pc.com/techblog/2010/06/02/adobe-cs5-video-apps/comment-page-1/#comment-80</link>
		<dc:creator>McCarthyTech</dc:creator>
		<pubDate>Thu, 04 Nov 2010 21:12:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.hd4pc.com/techblog/?p=96#comment-80</guid>
		<description>Using Adobe CS5 should bypass Quicktime completely on both Mac and PC.  Adobe calls their own MPEG4 H264 importer to decode the file, and Quicktime is not involved.  Then any files you export from CS5 will have the proper colorspace &quot;burned in,&quot; and since in my case that is DPXs for color correction, Quicktime is not involved at any point.  If you batch convert all of your source footage to a different format like ProRes through that process, you will have both proper colorspace, and smoother playback on most systems, at the expense of conversion time and disk space.</description>
		<content:encoded><![CDATA[<p>Using Adobe CS5 should bypass Quicktime completely on both Mac and PC.  Adobe calls their own MPEG4 H264 importer to decode the file, and Quicktime is not involved.  Then any files you export from CS5 will have the proper colorspace &#8220;burned in,&#8221; and since in my case that is DPXs for color correction, Quicktime is not involved at any point.  If you batch convert all of your source footage to a different format like ProRes through that process, you will have both proper colorspace, and smoother playback on most systems, at the expense of conversion time and disk space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.hd4pc.com/techblog/2010/06/02/adobe-cs5-video-apps/comment-page-1/#comment-79</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 04 Nov 2010 18:59:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.hd4pc.com/techblog/?p=96#comment-79</guid>
		<description>Yes, we noticed the color degradation right away.  I&#039;m intrigued by the Premier workflow in native H264.  I can&#039;t help but think that there must be info loss during the conform to ProRes422; like converting a still from RGB to CMYK, and then back again.

Looks like the idea is to bypass Quicktime as much as possible as well, but it appears that for the final output of a completed piece you will have to use Quicktime.

I&#039;ll research the decoder suggestion too. I&#039;m outputting final pieces with the Quicktime Conversion in FCP.  I wonder if Compressor would be better, although, fundamentally they do the same thing.

Thanks for your help Mike,

s</description>
		<content:encoded><![CDATA[<p>Yes, we noticed the color degradation right away.  I&#8217;m intrigued by the Premier workflow in native H264.  I can&#8217;t help but think that there must be info loss during the conform to ProRes422; like converting a still from RGB to CMYK, and then back again.</p>
<p>Looks like the idea is to bypass Quicktime as much as possible as well, but it appears that for the final output of a completed piece you will have to use Quicktime.</p>
<p>I&#8217;ll research the decoder suggestion too. I&#8217;m outputting final pieces with the Quicktime Conversion in FCP.  I wonder if Compressor would be better, although, fundamentally they do the same thing.</p>
<p>Thanks for your help Mike,</p>
<p>s</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: McCarthyTech</title>
		<link>http://www.hd4pc.com/techblog/2010/06/02/adobe-cs5-video-apps/comment-page-1/#comment-78</link>
		<dc:creator>McCarthyTech</dc:creator>
		<pubDate>Thu, 04 Nov 2010 17:58:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.hd4pc.com/techblog/?p=96#comment-78</guid>
		<description>Based on what you are saying, it sounds like Quicktime player is dropping frames on playback.  Installing a more efficient H264 decoder like CoreAVC solves that problems on Windows systems, but I am not sure how to deal with it on a Mac.  Obviously getting a more powerful system would help, but there should be a simpler way to solve the problem.  Clearly your system is physically capable of decoding them smoothly if they work well in FCP, the issue is a software one, but I am unfamiliar with how to manipulate codecs and default decoders in OSX.  Keep in mind that Quicktime decodes Canon DSLR files in an incorrect colorspace anyway, displaying them much flatter than they were actually recorded.</description>
		<content:encoded><![CDATA[<p>Based on what you are saying, it sounds like Quicktime player is dropping frames on playback.  Installing a more efficient H264 decoder like CoreAVC solves that problems on Windows systems, but I am not sure how to deal with it on a Mac.  Obviously getting a more powerful system would help, but there should be a simpler way to solve the problem.  Clearly your system is physically capable of decoding them smoothly if they work well in FCP, the issue is a software one, but I am unfamiliar with how to manipulate codecs and default decoders in OSX.  Keep in mind that Quicktime decodes Canon DSLR files in an incorrect colorspace anyway, displaying them much flatter than they were actually recorded.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.hd4pc.com/techblog/2010/06/02/adobe-cs5-video-apps/comment-page-1/#comment-77</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 04 Nov 2010 16:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.hd4pc.com/techblog/?p=96#comment-77</guid>
		<description>Mike,

Our on-going problem is that some of the HDSLR footage we shoot looks &quot;jittery&quot; played back in Quicktime but not in the FCP timeline or even RealPlayer.  This is only evident in panning clips and not locked-down camera shots, and the severity and frequency of the jumpiness is not identical in each playback. 

Any ideas?</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>Our on-going problem is that some of the HDSLR footage we shoot looks &#8220;jittery&#8221; played back in Quicktime but not in the FCP timeline or even RealPlayer.  This is only evident in panning clips and not locked-down camera shots, and the severity and frequency of the jumpiness is not identical in each playback. </p>
<p>Any ideas?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

