Return-Path: Received: from host6.canaca.com ([66.49.160.142] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4754844 for AE-List@media-motion.tv; Fri, 22 Jun 2012 20:12:57 +0200 Received: from 207-195-100-23.regn.static.sasknet.sk.ca ([207.195.100.23] helo=[192.168.1.38]) by host6.canaca.com with esmtpa (Exim 4.69) (envelope-from ) id 1Si8Og-0002pg-Hw for AE-List@media-motion.tv; Fri, 22 Jun 2012 14:15:54 -0400 From: Jack Tunnicliffe Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: multipart/alternative; boundary="Apple-Mail=_4F2B966C-5ACC-4463-8F37-7B2F2612060D" Subject: Re: [AE] frame rate weirdness Date: Fri, 22 Jun 2012 12:15:52 -0600 In-Reply-To: To: "After Effects Mail List" References: Message-Id: X-Mailer: Apple Mail (2.1278) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host6.canaca.com X-AntiAbuse: Original Domain - media-motion.tv X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - javapost.ca X-Source: X-Source-Args: X-Source-Dir: --Apple-Mail=_4F2B966C-5ACC-4463-8F37-7B2F2612060D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Make sure your start time is the same. There is a pref in Mocha for = offset to start at frame Zero or frame 1. AE starts at zero and Mocha = numbers starting at frame 1 but this can be changed. You can also just = slide your keyframes one frame in AE and it should correct. Interlaced footage can be an issue for tracking, too. Progressive is = always better to hold a good track. Jack Tunnicliffe Java Post Production www.javapost.ca On Jun 22, 2012, at 12:06 PM, pixelbot@comcast.net wrote: > we sent out some QTs to be color corrected and when we got them back I = was tracking them for screen replacement - my mocha tracks looked spot = on, and then when I used those track in AE - every track looked liked it = was playing catch up, I tried multiple times to track and try cc power = pin vs corner pin nothing would fix it, and then I looked at the frame = rate in AE it showed that they were 29.9625 not 29.97 - once I = reinterpreted to 29.97 every track was spot on. I going to have to check = with the post house that did the CC - I wouldn't even begin to know how = they screwed that up. >=20 > timt --Apple-Mail=_4F2B966C-5ACC-4463-8F37-7B2F2612060D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Make sure your start time is the same. There is a = pref in Mocha for offset to start at frame Zero or frame 1. AE starts at = zero and Mocha numbers starting at frame 1 but this can be changed. You = can also just slide your keyframes one frame in AE and it should = correct.

Interlaced footage can be an issue for = tracking, too. Progressive is always better to hold a good = track.

Jack Tunnicliffe

Java Post Production

www.javapost.ca

On Jun 22, 2012, at 12:06 PM, pixelbot@comcast.net = wrote:

we sent out some QTs to be color corrected and when we got = them back I was tracking them for screen replacement - my mocha tracks = looked spot on, and then when I used those track in AE - every track = looked liked it was playing catch up, I tried multiple times to track = and try cc power pin vs corner pin nothing would fix it, and then I = looked at the frame rate in AE it showed that they were 29.9625 not = 29.97 - once I reinterpreted to 29.97 every track was spot on. I going = to have to check with the post house that did the CC - I wouldn't even = begin to know how they screwed that = up.

timt

= --Apple-Mail=_4F2B966C-5ACC-4463-8F37-7B2F2612060D--