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 4755394 for AE-List@media-motion.tv; Sat, 23 Jun 2012 18:25:09 +0200 Received: from static24-89-101-87.r.rev.accesscomm.ca ([24.89.101.87] helo=[192.168.1.24]) by host6.canaca.com with esmtpa (Exim 4.69) (envelope-from ) id 1SiTBv-0006hl-Ly for AE-List@media-motion.tv; Sat, 23 Jun 2012 12:28:07 -0400 Subject: Re: [AE] frame rate weirdness References: From: Jack Tunnicliffe Content-Type: multipart/alternative; boundary=Apple-Mail-89CDB6A6-B7D7-4A88-A897-BC4431BDB5BA X-Mailer: iPad Mail (9B206) In-Reply-To: Message-Id: <420BC267-EC81-4229-8753-7733AF2FEFC8@javapost.ca> Date: Sat, 23 Jun 2012 10:28:07 -0600 To: After Effects Mail List Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) 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-89CDB6A6-B7D7-4A88-A897-BC4431BDB5BA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii True enough, Warren. I do quite a few demos in the course of a year for the l= ocal university, media college as well as a couple of high schools. One scho= ol fills a bus and travels 250 miles to attend a one hour demo each year.=20= Most students are very engaged and fascinated but invariably there are one o= r two falling asleep. I find it hard to believe they could be this way as we= put on a very engaging dog and pony show of them, but these people are prob= ably not attending a film and video class because it is their first love or p= assion. Often we find very experienced editors making mistakes with frame rates and p= ulldown. Some admit this techie stuff just eludes them and they look to us f= or help. The most prevalent issue we see is 29.97 footage being dragged into= 23.98 projects then that footage is exported or rendered out and frames are= thrown away. We have to try to get back to source or actually attempt to fi= x with products like frame restorer. I had posted a shot a couple of months ago, but worth repeating where a movi= e used a GoPro camera at 29.97 and dropped the footage into a 23.98 timeline= . Then the footage was exported at 23.98 for a vizfx person to remove the sh= adow caused by the helicopter. The source footage went missing. We were doin= g a DCP and the editor at our shop alerted me to the shot. I called the prod= ucer who said, we were told this couldn't be fixed by the biggest post facil= ity in Toronto. I told him we could fix it. Took me 90 minutes with Frame Re= storer, a little warp stabilizer as well as color correcting the guard rail b= ack to green from being blown out to white by the GoPro. Check out the befor= e and after here. Needless to say the producer was on top of the world when h= e saw this fix to his movie. http://web.me.com/java008/Moopoint/Helicopter_After_Frame_Restorer.html Jack Tunnicliffe Java Post Production On Jun 23, 2012, at 2:45 AM, Warren Heaton at UCLA Extension wrote: > Whenever this is the lecture topic, students tend to glaze over or go on Fa= cebook. >=20 >=20 >=20 >=20 >=20 > Sent from my iPad >=20 > On Jun 22, 2012, at 3:46 PM, Jack Tunnicliffe wrote: >=20 >> Interesting, but I can tell you we see this every day. A we are a post fa= cility, we get footage from editors from all over the place. Very few of the= m 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 enou= gh to teach them the ins and outs? We just end up fixing the problem and sen= ding 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 t= ime. Just force 29.97 in the AE Interpret Footage (and mocha project) dialog= s. >>>=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 w= as tracking them for screen replacement - my mocha tracks looked spot on, an= d then when I used those track in AE - every track looked liked it was playi= ng catch up, I tried multiple times to track and try cc power pin vs corner p= in 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 trac= k 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-89CDB6A6-B7D7-4A88-A897-BC4431BDB5BA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
True enough, Warren. I do q= uite a few demos in the course of a year for the local university, media col= lege as well as a couple of high schools. One school fills a bus and travels= 250 miles to attend a one hour demo each year. 

Most students are very engaged and fascinated but invariably there are on= e or two falling asleep. I find it hard to believe they could be this way as= we put on a very engaging dog and pony show of them, but these people are p= robably not attending a film and video class because it is their first love o= r passion.

Often we find very experienced editors m= aking mistakes with frame rates and pulldown. Some admit this techie stuff j= ust eludes them and they look to us for help. The most prevalent issue we se= e is 29.97 footage being dragged into 23.98 projects then that footage is ex= ported or rendered out and frames are thrown away. We have to try to get bac= k to source or actually attempt to fix with products like frame restorer.

I had posted a shot a couple of months ago, but worth= repeating where a movie used a GoPro camera at 29.97 and dropped the footag= e into a 23.98 timeline. Then the footage was exported at 23.98 for a vizfx p= erson to remove the shadow caused by the helicopter. The source footage went= missing. We were doing a DCP and the editor at our shop alerted me to the s= hot. I called the producer who said, we were told this couldn't be fixed by t= he biggest post facility in Toronto. I told him we could fix it. Took me 90 m= inutes with Frame Restorer, a little warp stabilizer as well as color correc= ting the guard rail back to green from being blown out to white by the GoPro= . Check out the before and after here. Needless to say the producer was on t= op of the world when he saw this fix to his movie.


Jack Tunnicliffe
Java Post Producti= on

On Jun 23, 2012, at 2:45 AM, Warren Heaton at UCLA Ex= tension <wheaton@ucla.edu> wro= te:

Whenever thi= s is the lecture topic, students tend to glaze over or go on Facebook.
=





Sent from my iPad<= /div>

On Jun 22, 2012, at 3:46 PM, Jack Tunnicliffe <jack@javapost.ca> wrote:

Interesting, but I can tell you we see th= is 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 ra= tes, pulldown, interlacing, etc. It's like editors never go to school for th= is, or does the school know enough to teach them the ins and outs? We just e= nd up fixing the problem and sending them a bill so there is an upside to kn= owing how to fix these issues. 

J= ack 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 Avi= d footage in particular all the time. Just force 29.97 in the AE Interpret Fo= otage (and mocha project) dialogs.

still pining for unive= rsal 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 correcte= d and when we got them back I was tracking them for screen replacement - my m= ocha tracks looked spot on, and then when I used those track in AE - every t= rack looked liked it was playing catch up, I tried multiple times to track a= nd 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 re= interpreted to 29.97 every track was spot on. I going to have to check with t= he post house that did the CC - I wouldn't even begin to know how they screw= ed that up.

timt


= --Apple-Mail-89CDB6A6-B7D7-4A88-A897-BC4431BDB5BA--