Return-Path: Received: from mail-pb0-f41.google.com ([209.85.160.41] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4754852 for AE-List@media-motion.tv; Fri, 22 Jun 2012 20:24:34 +0200 Received: by pbbrp2 with SMTP id rp2so3669232pbb.28 for ; Fri, 22 Jun 2012 11:27:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=/1c9aK95VvWIU6Kb9SwT01F5DdqeM7QyAx3t8jfkN6c=; b=bUEuPuFrTuATlkQwo6aS8auyfSvaBu15hCy+07BHDgp73U5PSvBOeggK/4Bt8aQc7D DqVT21Ndr1GalEz5hjHrMViNQ39mrKNOn1Byy2BQA6qFWdTjXxXATH9YM4y/MjgNQbGC q0lWAUSwFes7dGBxAmcO13ZYbKVf7YlKxj47QHWc0W1PYP56v5eGAh23Tr/w2UgpkmJl wNUrJ1n62Bi9v0EQ7WmukgZk3RZ0xAjRA2vrhaKea7R22M7M1jUUoHzscuJpTLLYRjP0 F2g3niYQLFwqHPQ/Eww/f7wHwFzpoWLBd5EcwOtVY8T8202RCYz02wZwxEl6fmRfGbP3 OF3g== Received: by 10.68.228.102 with SMTP id sh6mr12165389pbc.134.1340389652044; Fri, 22 Jun 2012 11:27:32 -0700 (PDT) Return-Path: Received: from [192.168.10.24] (c-98-246-188-32.hsd1.or.comcast.net. [98.246.188.32]) by mx.google.com with ESMTPS id nh8sm39622574pbc.60.2012.06.22.11.27.30 (version=SSLv3 cipher=OTHER); Fri, 22 Jun 2012 11:27:31 -0700 (PDT) Message-ID: <4FE4B914.5010009@gmail.com> Date: Fri, 22 Jun 2012 11:27:32 -0700 From: Rob & Jenny User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: After Effects Mail List Subject: Re: [AE] frame rate weirdness References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------000108050609020607040801" This is a multi-part message in MIME format. --------------000108050609020607040801 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I have had that happen when sending QT to a separate color correction place. It turned out if the Avid made any kind of time warping on the footage it would muck up the output's FPS as well. Unfortunately the fix turned out to be (at that time, I hope it's better now) to re-export the color corrected footage in question as individual frames. -Rob On 6/22/2012 11:15 AM, Jack Tunnicliffe wrote: > 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 > --------------000108050609020607040801 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I have had that happen when sending QT to a separate color correction place. It turned out if the Avid made any kind of time warping on the footage it would muck up the output's FPS as well. Unfortunately the fix turned out to be (at that time, I hope it's better now) to re-export the color corrected footage in question as individual frames.

-Rob

On 6/22/2012 11:15 AM, Jack Tunnicliffe wrote:

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

--------------000108050609020607040801--