<?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: Timecode Mismatch</title>
	<atom:link href="http://ariasfilms.com/blog/2009/06/20/timecode-mismatch/feed/" rel="self" type="application/rss+xml" />
	<link>http://ariasfilms.com/blog/2009/06/20/timecode-mismatch/</link>
	<description>Hollywood native goes &#34;Hollywood&#34;</description>
	<lastBuildDate>Thu, 04 Aug 2011 07:49:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Shane Ross</title>
		<link>http://ariasfilms.com/blog/2009/06/20/timecode-mismatch/comment-page-1/#comment-1979</link>
		<dc:creator>Shane Ross</dc:creator>
		<pubDate>Mon, 22 Jun 2009 17:24:04 +0000</pubDate>
		<guid isPermaLink="false">http://ariasfilms.com/blog/?p=1058#comment-1979</guid>
		<description>Karen is right I believe.  I haven&#039;t had to deal with second system audio in FCP yet, but I have with Avid.  Same thing with an Avid...dailies on Digibeta at 29.97, sound on DAT at 23.98 to match the film rate.

All you need to do is synch to the 00 frame.  That will be the same on both, no matter what.</description>
		<content:encoded><![CDATA[<p>Karen is right I believe.  I haven&#8217;t had to deal with second system audio in FCP yet, but I have with Avid.  Same thing with an Avid&#8230;dailies on Digibeta at 29.97, sound on DAT at 23.98 to match the film rate.</p>
<p>All you need to do is synch to the 00 frame.  That will be the same on both, no matter what.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen</title>
		<link>http://ariasfilms.com/blog/2009/06/20/timecode-mismatch/comment-page-1/#comment-1977</link>
		<dc:creator>Karen</dc:creator>
		<pubDate>Sat, 20 Jun 2009 22:42:42 +0000</pubDate>
		<guid isPermaLink="false">http://ariasfilms.com/blog/?p=1058#comment-1977</guid>
		<description>Any way that you can set up to sync to a 00 frame?  

My (feeble) understanding is that audio files don&#039;t have a frame rate until you bring them into FCP, so you would need to bring them in with your sequence preset at 23.98.  A second is still a second... until they are in a sequence - when a frame is a frame is a frame, to paraphrase Gertrude Stein.

I used to set up Cinema Tools as if I were syncing audio at 29.97 to my 23.98 clips, just so that I could easily check the TC burns on film, and they would always match at 00.

But then nothing is true until tested.  I&#039;ll be curious to hear what happens.  I&#039;m sure a way will be found...</description>
		<content:encoded><![CDATA[<p>Any way that you can set up to sync to a 00 frame?  </p>
<p>My (feeble) understanding is that audio files don&#8217;t have a frame rate until you bring them into FCP, so you would need to bring them in with your sequence preset at 23.98.  A second is still a second&#8230; until they are in a sequence &#8211; when a frame is a frame is a frame, to paraphrase Gertrude Stein.</p>
<p>I used to set up Cinema Tools as if I were syncing audio at 29.97 to my 23.98 clips, just so that I could easily check the TC burns on film, and they would always match at 00.</p>
<p>But then nothing is true until tested.  I&#8217;ll be curious to hear what happens.  I&#8217;m sure a way will be found&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Crutsinger</title>
		<link>http://ariasfilms.com/blog/2009/06/20/timecode-mismatch/comment-page-1/#comment-1976</link>
		<dc:creator>Sam Crutsinger</dc:creator>
		<pubDate>Sat, 20 Jun 2009 21:54:35 +0000</pubDate>
		<guid isPermaLink="false">http://ariasfilms.com/blog/?p=1058#comment-1976</guid>
		<description>OK, I really need to read before I post. Several typos in there, but you get my drift. =)</description>
		<content:encoded><![CDATA[<p>OK, I really need to read before I post. Several typos in there, but you get my drift. =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Crutsinger</title>
		<link>http://ariasfilms.com/blog/2009/06/20/timecode-mismatch/comment-page-1/#comment-1975</link>
		<dc:creator>Sam Crutsinger</dc:creator>
		<pubDate>Sat, 20 Jun 2009 21:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://ariasfilms.com/blog/?p=1058#comment-1975</guid>
		<description>Yeah, you time code voodoo is an important thing to make sure you have all lined up and tested all the way through the process before day one preferably. The HVX200 records at 29.97. You do the conversion on import and that discards the extra frames, but the &quot;source file&quot; is still that 29.97 file with the extra frames. If you needed to go back to the original source and look at a certain frame, you&#039;d be in a 29.97 world, not a 24fps world. 

Usually, I end up just going ahead and keeping in the 29.97 realm if things get wacky like this. Some cameras, like the Red One, will let you actually lay down 24fps, like the Red, but you have to consider the lowest common denominator on this stuff and use what all the gear will commonly allow if you want a smooth ride.

That said, you might try using a 29.97 time for syncing. I believe FCP will throw in the extra frames if you&#039;re dropping 24 footage on there. Sync up a clip, select the audio and video and group them together. Pull that into a bin and see if it&#039;s a 24 clip or a 29.97 clip at that point. If it&#039;s 24, then there you go. If it&#039;s 29.97, then consider editing at 29.97. 

I usually just do a bunch of trial and error till I find something that works in these situations. Just remember that the person watching won&#039;t have a clue about the mathematical dilemma you&#039;re in. All they know is pictures and sound and story. If the picture and sound are in sync and there&#039;s no annoying jittering or other SNAFUs going on, then they won&#039;t care how you got there.</description>
		<content:encoded><![CDATA[<p>Yeah, you time code voodoo is an important thing to make sure you have all lined up and tested all the way through the process before day one preferably. The HVX200 records at 29.97. You do the conversion on import and that discards the extra frames, but the &#8220;source file&#8221; is still that 29.97 file with the extra frames. If you needed to go back to the original source and look at a certain frame, you&#8217;d be in a 29.97 world, not a 24fps world. </p>
<p>Usually, I end up just going ahead and keeping in the 29.97 realm if things get wacky like this. Some cameras, like the Red One, will let you actually lay down 24fps, like the Red, but you have to consider the lowest common denominator on this stuff and use what all the gear will commonly allow if you want a smooth ride.</p>
<p>That said, you might try using a 29.97 time for syncing. I believe FCP will throw in the extra frames if you&#8217;re dropping 24 footage on there. Sync up a clip, select the audio and video and group them together. Pull that into a bin and see if it&#8217;s a 24 clip or a 29.97 clip at that point. If it&#8217;s 24, then there you go. If it&#8217;s 29.97, then consider editing at 29.97. </p>
<p>I usually just do a bunch of trial and error till I find something that works in these situations. Just remember that the person watching won&#8217;t have a clue about the mathematical dilemma you&#8217;re in. All they know is pictures and sound and story. If the picture and sound are in sync and there&#8217;s no annoying jittering or other SNAFUs going on, then they won&#8217;t care how you got there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

