Return-Path: Received: from mout.perfora.net ([74.208.4.195] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4755079 for AE-List@media-motion.tv; Sat, 23 Jun 2012 03:29:42 +0200 Received: from mbp-17.westell.com (50-55-11-251.waus.wi.frontiernet.net [50.55.11.251]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MUHso-1SIV9Q2XrO-00R14Y; Fri, 22 Jun 2012 21:32:42 -0400 From: Steve Oakley Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: multipart/alternative; boundary="Apple-Mail=_AA094F2C-13C5-4FC5-A8FB-E7353F6B82F0" Subject: Re: [AE] frame rate weirdness Date: Fri, 22 Jun 2012 20:32:35 -0500 In-Reply-To: To: "After Effects Mail List" References: Message-Id: <0C0417D6-B37E-4BA0-A525-9B2C78AD0287@practicali.com> X-Mailer: Apple Mail (2.1278) X-Provags-ID: V02:K0:vueEpyedqyEa/Hff/P3hzDzt9KEQUvtDQFUfgMFI6t7 jKdA/OckPOfJIOqw8lUcXcCajyUDKz1FYYHn3K8NO6MFMyScEU tcLdVW+7FYEsk2yqn7GjmOmTKT+VVmLmQCGkQ9EMLvFcmXOVJ/ LeeDVbgthIOrAwhWPqEJ0fQOV8jbyHUXe9vgXdTMonFtMKSPr2 7B/f90BiAJ94YR4iD9kRaG+ummUVFNbRpCZCas+UeAM2BPuzOb iYVykV1x3zsVPpID75qLUpG03duIwrc7mpeshHq2wMX1RbiVW+ UpVB1Y3WKuToCisiaAQ93A1khSGA5W747nDwoUePnSX/4uYUrx QZOApmXWctyiLYc261K1Pq0XhZRe6T7Q9bgv0+xKTM+BMTunwy lK700UY0h7OzQ== --Apple-Mail=_AA094F2C-13C5-4FC5-A8FB-E7353F6B82F0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii like Jack sez : other people's stupidity or uneducation can be = profitable :) so I don't worry. I just fix their problems and collect = checks. Of course there was this time an "editor" sent an email to her = bosses and everyone in the dept about how FCP 3.0 or 4.o was a POS = because it couldn't keep 30.000 video in sync with audio.she of course = fixed FCP's wrong 29.97 frame rate and changed it to 30.000 everywhere.. = we all know video runs at 30.000, especially NTSC DV captured via FW.... = oh the reply all email was sweet ;) S On Jun 22, 2012, at 5:46 PM, Jack Tunnicliffe wrote: > Interesting, but I can tell you we see this every day. A we are a post = facility, we get footage from editors from all over the place. Very few = of them seem to understand anything about frame rates, pulldown, = interlacing, etc. It's like editors never go to school for this, or does = the school know enough to teach them the ins and outs? We just end up = fixing the problem and sending them a bill so there is an upside to = knowing how to fix these issues.=20 >=20 > Jack Tunnicliffe > Java Post Production > www.javapost.ca >=20 >=20 >=20 > On Jun 22, 2012, at 4:33 PM, Chris Meyer wrote: >=20 >> We used to find we had to re-conform Avid footage in particular all = the time. Just force 29.97 in the AE Interpret Footage (and mocha = project) dialogs. >>=20 >> still pining for universal 30,000/1001 support - >> Chris >>=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 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 >>=20 >=20 --Apple-Mail=_AA094F2C-13C5-4FC5-A8FB-E7353F6B82F0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii like = Jack sez : other people's stupidity or uneducation can be profitable :) = so I don't worry. I just fix their problems and collect checks. Of = course there was this time an "editor" sent an email to her bosses and = everyone in the dept about how FCP 3.0 or 4.o was a POS because it = couldn't keep 30.000 video in sync with audio.she of course fixed FCP's = wrong 29.97 frame rate and changed it to 30.000 everywhere.. we all know = video runs at 30.000, especially NTSC DV captured via FW.... oh the = reply all email was sweet = ;)

S


On Jun 22, = 2012, at 5:46 PM, Jack Tunnicliffe wrote:

Interesting, but I can tell you = we see this every day. A we are a post facility, we get footage from = editors from all over the place. Very few of them seem to understand = anything about frame rates, pulldown, interlacing, etc. It's like = editors never go to school for this, or does the school know enough to = teach them the ins and outs? We just end up fixing the problem and = sending them a bill so there is an upside to knowing how to fix these = issues. 

Jack Tunnicliffe
Java Post Production
www.javapost.ca



On Jun 22, 2012, at 4:33 PM, Chris Meyer wrote:

We = used to find we had to re-conform Avid footage in particular all the = time. Just force 29.97 in the AE Interpret Footage (and mocha project) = dialogs.

still pining for universal 30,000/1001 = support -
Chris


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


<= br>= --Apple-Mail=_AA094F2C-13C5-4FC5-A8FB-E7353F6B82F0--