<?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: Multicam HDSLR with Timecode</title>
	<atom:link href="http://www.onerivermedia.com/blog/?feed=rss2&#038;p=244" rel="self" type="application/rss+xml" />
	<link>http://www.onerivermedia.com/blog/?p=244</link>
	<description>Life, love, and the pursuit of pixels</description>
	<lastBuildDate>Wed, 16 May 2012 17:22:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Marco Solorio</title>
		<link>http://www.onerivermedia.com/blog/?p=244#comment-906</link>
		<dc:creator>Marco Solorio</dc:creator>
		<pubDate>Wed, 31 Aug 2011 01:12:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.onerivermedia.com/blog/?p=244#comment-906</guid>
		<description>Thanks for the post. Yes, we&#039;re well aware of the differences between 23.976/24 FPS and 29.97/30 FPS, as we&#039;ve been using both frame-rate formats long before HD came around. Although the frame-rate option for our TC generator says 24, it does lock in online mode at 23.976. Go figure. Your mention of feeding the LTC signal into the HDSLR camera was in the last section of our blog post, in case you missed it. We described how to make it work for both FCP and Avid, and with what hardware. ;-)</description>
		<content:encoded><![CDATA[<p>Thanks for the post. Yes, we&#8217;re well aware of the differences between 23.976/24 FPS and 29.97/30 FPS, as we&#8217;ve been using both frame-rate formats long before HD came around. Although the frame-rate option for our TC generator says 24, it does lock in online mode at 23.976. Go figure. Your mention of feeding the LTC signal into the HDSLR camera was in the last section of our blog post, in case you missed it. We described how to make it work for both FCP and Avid, and with what hardware. <img src='http://www.onerivermedia.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S M</title>
		<link>http://www.onerivermedia.com/blog/?p=244#comment-897</link>
		<dc:creator>S M</dc:creator>
		<pubDate>Tue, 30 Aug 2011 03:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.onerivermedia.com/blog/?p=244#comment-897</guid>
		<description>There is a big difference between what is marked as 24 f.p.s. and 23.97 f.p.s. True 24 is a film timecode option. For all intents and purpose 23.97 didn&#039;t exist before HD video and probably did not exist when your TC gen box was made, hence the reason for your drift. 29.97 is also very different from true 30 and the former was a result of color video. The best way that I have found to TC sync an HDSLR is to feed the LTC code straight into the camera&#039;s input. Avid can read that TC and auto sync your audio.</description>
		<content:encoded><![CDATA[<p>There is a big difference between what is marked as 24 f.p.s. and 23.97 f.p.s. True 24 is a film timecode option. For all intents and purpose 23.97 didn&#8217;t exist before HD video and probably did not exist when your TC gen box was made, hence the reason for your drift. 29.97 is also very different from true 30 and the former was a result of color video. The best way that I have found to TC sync an HDSLR is to feed the LTC code straight into the camera&#8217;s input. Avid can read that TC and auto sync your audio.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

