Return-Path: Received: from eu1sys200aog105.obsmtp.com ([207.126.144.119] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with SMTP id 4754877 for AE-List@media-motion.tv; Fri, 22 Jun 2012 20:40:06 +0200 Received: from mail-yx0-f174.google.com ([209.85.213.174]) (using TLSv1) by eu1sys200aob105.postini.com ([207.126.147.11]) with SMTP ID DSNKT+S8ugOvdBm2kCIRkWD2at8ZhnKIq59z@postini.com; Fri, 22 Jun 2012 18:43:07 UTC Received: by mail-yx0-f174.google.com with SMTP id l2so1804616yen.19 for ; Fri, 22 Jun 2012 11:43:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version :x-gm-message-state; bh=WHMOqgKvWLUhGaHzs52YQdpQuiXwPo0RcQuY8ogNTXc=; b=SWPd+Bwv/cuDTpLR1psA9ZvZeDRni+u3Xgm0Ga7JuJBg+HGkahKkRTHYYd6Rikx2s7 78k6ETOeW97746lTL4NuoqbHHnTX+OYNgW9tXLo+RU6Fms00MGFq4FfQMEUna2Do7OfL msrXUpwuzqiUEiL/YLg85UQtz5iB4BLn/gVgDit7EyxTSp6gBZfvE1fYWcVhWqJxGEVr 56mAaJgHcpqQCftE+CJ5F/PYbdq6L6LC9DMMJFF0VQIO4NwGrP4cWzwEgoeDLZtQ2PBi ljhwcxJRh6Kk8Ed/FJqmuDtPq0Hr1eNzyl6hCIETF4wymX5MT75d2tQ8WeM62cRgHDib ZW8A== Received: by 10.60.27.6 with SMTP id p6mr2995754oeg.37.1340390586037; Fri, 22 Jun 2012 11:43:06 -0700 (PDT) Return-Path: Received: from [10.165.189.20] ([166.137.84.123]) by mx.google.com with ESMTPS id hd9sm31102325obc.6.2012.06.22.11.42.59 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 22 Jun 2012 11:43:05 -0700 (PDT) Subject: Re: [AE] frame rate weirdness References: From: Ross Shain Content-Type: multipart/alternative; boundary=Apple-Mail-5594EC50-5255-4846-B504-1E2EFD8A6BFB X-Mailer: iPhone Mail (9B206) In-Reply-To: Message-Id: Date: Fri, 22 Jun 2012 14:42:49 -0400 To: After Effects Mail List Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) X-Gm-Message-State: ALoCoQk1HIKbj17zbkrF7cbZ6PsU/qq6BsBj6EXmcWOIvHOb6dQ6O6BX2e8l7/i1sA6T/lYO2+Im --Apple-Mail-5594EC50-5255-4846-B504-1E2EFD8A6BFB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Whenever tracks look good in mocha, but drift in AE, always double check the= AE/mocha comp settings match FPS and PAR.=20 Also double check the source clips frame rate matches the AE comp (interpret= footage). Sent from my iPhone On Jun 22, 2012, at 2:30 PM, pixelbot@comcast.net wrote: > I believe the post house was working off the QTs from the camera and not a= re-export but I could be wrong. >=20 > tt >=20 > From: "Rob & Jenny" > To: "After Effects Mail List" > Sent: Friday, June 22, 2012 11:27:32 AM > Subject: Re: [AE] frame rate weirdness >=20 > I have had that happen when sending QT to a separate color correction plac= e. 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 f= ootage in question as individual frames. >=20 > -Rob >=20 > 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 star= ting at frame 1 but this can be changed. You can also just slide your keyfra= mes one frame in AE and it should correct. >=20 > Interlaced footage can be an issue for tracking, too. Progressive is alway= s better to hold a good track. >=20 > Jack Tunnicliffe > Java Post Production > www.javapost.ca >=20 >=20 >=20 > On Jun 22, 2012, at 12:06 PM, pixelbot@comcast.net wrote: >=20 > 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 t= hen when I used those track in AE - every track looked liked it was playing c= atch up, I tried multiple times to track and try cc power pin vs corner pin n= othing would fix it, and then I looked at the frame rate in AE it showed tha= t they were 29.9625 not 29.97 - once I reinterpreted to 29.97 every track wa= s spot on. I going to have to check with the post house that did the CC - I w= ouldn't even begin to know how they screwed that up. >=20 > timt >=20 --Apple-Mail-5594EC50-5255-4846-B504-1E2EFD8A6BFB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Whenever tracks look good i= n mocha, but drift in AE, always double check the AE/mocha comp settings mat= ch FPS and PAR. 

Also double check the sou= rce clips frame rate matches the AE comp (interpret footage).



Sent from my iPhone

On Ju= n 22, 2012, at 2:30 PM, pixelbot@com= cast.net wrote:

<= div style=3D"font-family: Arial; font-size: 12pt; color: #000000">I believe t= he post house was working off the QTs from the camera and not a re-export bu= t I could be wrong.

tt

From: <= /b>"Rob & Jenny" <gfxguy74@gmai= l.com>
To: "After Effects Mail List" <AE-List@media-motion.tv>
Sent: Fri= day, June 22, 2012 11:27:32 AM
Subject: Re: [AE] frame rate weirdn= ess

=20 =20 =20 =20 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 sta= rt 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

=20
= --Apple-Mail-5594EC50-5255-4846-B504-1E2EFD8A6BFB--