<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>sonsey.com &#187; 23.976</title>
	<atom:link href="http://sonsey.com/tag/23-976/feed/" rel="self" type="application/rss+xml" />
	<link>http://sonsey.com</link>
	<description>Composer/Sound Designer/Engineer/Gadabout</description>
	<lastBuildDate>Thu, 29 Jul 2010 02:36:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Final Cut Pro Audio Tip#1 -23.976 OMF&#8217;s</title>
		<link>http://sonsey.com/2009/06/17/final-cut-pro-audio-tip1-23-976-omfs/</link>
		<comments>http://sonsey.com/2009/06/17/final-cut-pro-audio-tip1-23-976-omfs/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 18:27:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Sound Advice]]></category>
		<category><![CDATA[23.976]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[FCP]]></category>
		<category><![CDATA[OMF]]></category>

		<guid isPermaLink="false">http://sonsey.com/?p=109</guid>
		<description><![CDATA[A known bug in Final Cut Pro is that OMF&#8217;s of 23.976fps (or 23.98 as it&#8217;s sometimes called) sequences, report as 24fps sequences when loading into ProTools or other Audio DAW&#8217;s.



23.976 OMF Opened in ProTools


This is simply a misreporting of the frame rate by Final Cut Pro. The session IS indeed at 23.976, and changing [...]]]></description>
			<content:encoded><![CDATA[<p>A known bug in Final Cut Pro is that OMF&#8217;s of 23.976fps (or 23.98 as it&#8217;s sometimes called) sequences, report as 24fps sequences when loading into ProTools or other Audio DAW&#8217;s.</p>
<div class="mceTemp mceIEcenter">
<dl id="attachment_138" class="wp-caption aligncenter" style="width: 274px;">
<dt class="wp-caption-dt"><a style="text-decoration: none;" href="http://sonsey.com/wp-content/uploads/2009/06/OPEN_OMF.jpg"><img class="size-medium wp-image-138 " title="OPEN_OMF" src="http://sonsey.com/wp-content/uploads/2009/06/OPEN_OMF-264x300.jpg" alt="23.976 OMF Opened in PT" width="264" height="300" /></a></dt>
<h2>23.976 OMF Opened in ProTools</h2>
</dl>
</div>
<p style="text-align: left;">This is simply a misreporting of the frame rate by Final Cut Pro. The session IS indeed at 23.976, and changing the timeline to 23.976 will fix them problem.</p>
<div class="mceTemp mceIEcenter">
<dl id="attachment_139" class="wp-caption aligncenter" style="width: 310px;">
<dt class="wp-caption-dt"><a href="http://sonsey.com/wp-content/uploads/2009/06/OFF_GRID.jpg"><img class="size-medium wp-image-139 " title="OFF_GRID" src="http://sonsey.com/wp-content/uploads/2009/06/OFF_GRID-300x240.jpg" alt="Notice the Audio isn't on the frame line" width="300" height="240" /></a></dt>
<h2>Notice the Audio is off the Frame line</h2>
</dl>
</div>
<p>As always when changing any sync session, sync should be checked. This is easiest when a &#8220;two-pop&#8221; (a SINGLE frame of bars and tone, exactly 2 seconds before picture start) is included with the OMF.</p>
]]></content:encoded>
			<wfw:commentRss>http://sonsey.com/2009/06/17/final-cut-pro-audio-tip1-23-976-omfs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
