From: "Byron Nash" Received: from mail-wm0-f42.google.com ([74.125.82.42] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 6328859 for AE-List@media-motion.tv; Mon, 02 Oct 2017 16:47:33 +0200 Received: by mail-wm0-f42.google.com with SMTP id i82so8943064wmd.3 for ; Mon, 02 Oct 2017 07:49:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=OCz63aWoGr5T4yASspsEFKWuAwamI2DyjluZ4TqT7d4=; b=CpFomoXRoC/Te+jmCvs9iS2HgX4a5T6AlbZSvCyMMLHbAUlZfYaESOhGlzvp6FSmi1 RFy3zsxwcEQLBSXljdki7apVnpeIE84pN+aAmzVJ4GhkN1rkvgVcgQF6/bSQGXrYLvOr YyT7goGk/31KkjuQQhnLCpgHYR+ITW3lwKvF4hknVf8N6buDKeN52HRz37k2B1HUpCf1 YCjZLeiVwDU6RshK/E8kQuQoGqjdP80M1dd5OHMKNOCzsVAx2B3cD8RM5KS98x4rKp/+ PfbC+Sbj+i2yic3dHZFliqUnSHDqMHWfiUocBsUQSmwMeKn33ni8Wz5TRqjIp9VoPV1O JkiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=OCz63aWoGr5T4yASspsEFKWuAwamI2DyjluZ4TqT7d4=; b=qJDIvgIsKuBvolR/PGJ6t9vIrBLbR2yRHGvGq6NxJfG90rgG1MnILwp2nqJjnT3Nu/ OUeGEStK1dC3GdhhHtb/nW1Ta9VfjQYmlanN5NDDfV6LtkmKKFX5ro5toUO0cneZWb1y SplLHCSeGhM0j2LH5so2H8KGF8eDLEPN2lW44uYMK0tkj6z8SKDjN6BtrAoNiaim8oE7 pXWoZL658qiEx7m7XNKDJtyjBySIVaDGyJLxBrQJJ4hD0Bl6mLVMGuD7uI86RH4kYSNl qWlr5zojIarhfZswN2B3JeoGlaSmZkQ6Wrw5zrnzHSyYaj28LigBqRGI5tzA65/7lO5K xgcQ== X-Gm-Message-State: AHPjjUgDlPScczz2LAzQaYJGZb7xdyINuNEeAlPrasAeVcg/FVCVy0Ju z1WxwfNbNrPprf7jUJT2cHPdw+VNjYTpQca0sI8= X-Google-Smtp-Source: AOwi7QC2MVNIyNLWcO8CA6vxnlbXAZBCLd6SNj5orN2k4SjYAxqlMkE1PiQN4q4ADzHhV7A3QrE6DPqoKzojpu6MEYo= X-Received: by 10.80.171.8 with SMTP id s8mr20659056edc.222.1506955759492; Mon, 02 Oct 2017 07:49:19 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 02 Oct 2017 14:49:08 +0000 Message-ID: Subject: Re: [AE] 3:2 pulldown, frame blending, and camera tracking To: After Effects Mail List Content-Type: multipart/alternative; boundary="94eb2c0eecdcbca4b1055a917a00" --94eb2c0eecdcbca4b1055a917a00 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Yes, we air interlaced. I think what's messing this up is the need to output in HD from a SD source plus the time stretch. Camera tracker doesn't work on stretched footage, and when I collapse the precomp it screws up the camera. I need the text clean, not scaled from SD. On Sat, Sep 30, 2017 at 12:55 PM Jim Curtis wrote= : > Do you broadcast interlaced? > > Once I=E2=80=99ve converted my 29.97 interlaced to 23.976, I render it ou= t at that > frame rate and leave it there. I can reintroduce the pulldown and fields > later if necessary, but it=E2=80=99s rarely necessary. One of my spot de= livery > services demanded 59.94 for a while; then they relaxed it and started > taking 23.976. > > This is pretty basic, so I suppose you know that if you have interlaced > footage, it=E2=80=99s best practice to put it in a comp that=E2=80=99s do= uble the frame > rate - 59.94 so that you are tracking or roto-ing the fields separately a= s > frames. You can recombine the fields later in output. > > > > > > On Sep 29, 2017, at 3:58 PM, Byron Nash wrote: > > We get a lot of older SD footage here that we up-res to HD for our networ= k > broadcast. Some shot need camera tracking, roto, and vfx. I have a shot > that is confounding me and wanted to see what steps some of you would tak= e > differently. > > Here's my normal procedure for dealing with footage shot on 24 and coming > to us at 29.97. > > 1. remove 3:2 pulldown and interpret fields correctly > 2. put footage in a 23.976 comp > 3. enable any speed changes and enable pixel motion frame blending > 4. perform roto and tracking > 5. render to 29.97 with 3:2 pulldown and appropriate fields > > The goal is to work on the footage in it's original cadence. We often get > shots that have been scaled or stretched in time.This greatly exacerbates > the issue. This brings me to my current problem. I'm trying to camera tra= ck > a shot that is SD and has time stretch. I want the tracked in graphic to = be > overlayed in a HD comp. However, the camera tracker doesn't want any > scaling done to the shot first. I know this is an order of operations > problem. Just having trouble getting the pieces lined up. > > Thanks for any input. > > Byron > > > --94eb2c0eecdcbca4b1055a917a00 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes, we air interlaced. I think what's messing this up= is the need to output in HD from a SD source plus the time stretch. Camera= tracker doesn't work on stretched footage, and when I collapse the pre= comp it screws up the camera. I need the text clean, not scaled from SD.
On Sat, Sep 30, 2017 at = 12:55 PM Jim Curtis <AE-List@= media-motion.tv> wrote:
Do you broadcast interlaced?

Once I=E2=80=99ve converted my 29.97 interlaced to 23.976, I ren= der it out at that frame rate and leave it there.=C2=A0 I can reintroduce t= he pulldown and fields later if necessary, but it=E2=80=99s rarely necessar= y.=C2=A0 One of my spot delivery services demanded 59.94 for a while; then = they relaxed it and started taking 23.976.

This is prett= y basic, so I suppose you know that if you have interlaced footage, it=E2= =80=99s best practice to put it in a comp that=E2=80=99s double the frame r= ate - 59.94 so that you are tracking or roto-ing the fields separately as f= rames.=C2=A0 You can recombine the fields later in output.



=

On Sep 29, 2017, at = 3:58 PM, Byron Nash <AE-List@media-motion.tv> wrote:

We get a lo= t of older SD footage here that we up-res to HD for our network broadcast. = Some shot need camera tracking, roto, and vfx. I have a shot that is confou= nding me and wanted to see what steps some of you would take differently.= =C2=A0

Here's my normal procedure for dealing with f= ootage shot on 24 and coming to us at 29.97.
  1. remove 3:2 p= ulldown and interpret fields correctly
  2. put footage in a 23.976 comp=
  3. enable any speed changes and enable pixel motion frame blending
  4. perform roto and tracking
  5. render to 29.97 with 3:2 pulldown a= nd appropriate fields
The goal is to work on the footage in i= t's original cadence. We often get shots that have been scaled or stret= ched in time.This greatly exacerbates the issue. This brings me to my curre= nt problem. I'm trying to camera track a shot that is SD and has time s= tretch. I want the tracked in graphic to be overlayed in a HD comp. However= , the camera tracker doesn't want any scaling done to the shot first. I= know this is an order of operations problem. Just having trouble getting t= he pieces lined up.

Thanks for any input.=C2= =A0

Byron

--94eb2c0eecdcbca4b1055a917a00--